3 ms·
I don't like to have adjust my build systems to run an additional pre-processor over my code when there's no actual requirement for it. I don't want to have to
by PaulDavisThe1st 7y ago
I don't like to have adjust my build systems to run an additional pre-processor over my code when there's no actual requirement for it. I don't want to have to deal with code I did not write appearing in the middle of code I did write.
GTK is written in C. Gtkmm is written in C++. Totally different. Gtkmm's signal/slot system is better than the original one in Qt. I haven't looked at Qt's current system in quite some time.
someButton.signal_clicked().connect (mem_fun (*this, &Handler::method);
Many variations to allow binding, argument hiding, return value hiding and all the usual stuff.
Gtkmm has several display widgets that use a model/view paradigm, and let you define your own model and then map that to the view. If you literally just have a bunch of strings, there's one specifically to handle that situation.
I haven't used Qt myself but have worked in close collaboration with people who use it a lot.
- simion314 7y agoOK, so your problem is that moc is an extra build step. but is this for aesthetic reason or why? From my Qt experience you never see the moc code when you debug your applications. The only way to avoid moc would be to use heavy templates or macros and those also generate code behind your back. I did not heard of GTKmm so I will check it out to find out more, thanks.