Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
Different output in VS2010 than ... everything else
tachoknight last edited by
I'm a complete newbie to QT, having downloaded the SDK on Monday. Working with both QT Creator and the Eclipse plugin, I have created some test applications and I'm just blown away by how cool QT is; once I figured out how to do the signal->slot connections in the designer, I was happily coding away. Awesome stuff!
I apologize if this is an "everybody knows but me" question, but I was wondering why the UI member in a project generated using the VS Plugin is not a pointer, when an identical project created under QT Creator, and the QT Plugin for Eclipse, it is. Not a huge deal, of course, but moving code back and forth from the various projects requires changing the dereference operator. I know I could just change it, but I figured there might be a reason why it was done this way.
Just curious, I already love QT...I'm never going back to MFC. :)
Guest last edited by
I've not used VS Plugin and can't answer you on that but
[quote author="tachoknight" date="1289406730"]I'm never going back to MFC. :)[/quote]
cheers! I know exactly what you mean and welcome to Qt! I'm a convert too and it was bye bye Java for me :)
There are several ways to do UI file integration into C++ classes (as "documented":http://doc.qt.nokia.com/4.7/designer-using-a-ui-file.html#the-direct-approach). VS Plugin and Qt Creator both implement a flavor of "the direct approach". I doubt that there is any more specific reason than personal preferences of the developers that actually did the wizards to set them up.
Having said this and being a Creator guy myself I have to point out that QObjects should be allocated on the heap and thus you should prefer Qt Creator's way of doing things.
Welcome aboard by the way... I fully understand why you do not want to go back to MFC by the way:-)