- Qt designer vs qt creator how to#
- Qt designer vs qt creator portable#
- Qt designer vs qt creator software#
- Qt designer vs qt creator windows#
Debugger easily loses control, need to restart.Can't display some variables in Debug mode, ex: static variables, globals.Displaying some variables locks up QC when expanding an object.'assert' crashes instead of displaying an error message.
Qt designer vs qt creator windows#
Looking back I think it would be a lot more difficult doing in Qt Creator taking into account the amount of Windows specific debugging Do you mean that Qt uses the VS debugger? Then why is it so bad? I can't be the only who has noticed that (Qt Creator 4.11.0): I did a large MFC to Qt port, so a similar scenario and it was all done using VS and very custom build system. VS has also great profiling tools built in which is a tremendous advantage in my line of work.įor small personal Qt projects I use Qt Creator just because it has better Qt support in general and I don't need to debug as much, but VS is my IDE of choice if Qt is not the center of the project.Īnother consideration for me is integration with external tools and frameworks, unrelated to Qt, and for those important to me VS is usually the number one target on Windows with very minor, if any, support for other IDEs, including Qt Creator. As said Qt Creator is using an external debugger, but its integration into the IDE is lacking IMO. In my experience VS debugging experience is way above that of Qt Creator too, especially in more advanced scenarios than just looking at couple of variables. Usually because Qt is just a small part of the entire project and only some of the components are using it. That being said, for me - I worked on couple of big projects and it's VS in all of them. There's just too many of us and all you can get here are some personal scenarios of few devs. What do most Windows developers use: Visual Studio or Qt Creator? Otherwise, VS will often recompile some moc and ui files every single said: This is by far the best way for VS to track dependencies in Qt projects. FASTBuild also provides a way to generate a VS project file. These are currently generated from the Qt project files (see my github: ). PS: We are now using FASTBuild for compilation. So, you can have a dual setup or go fully VS. But, you will definitely need VS for debugging on Windows anyways. In summary: I personally find Qt Creator superior in navigating code, especially when switching between platforms. Expanding a class to see its values can take minutes. The main problem is with the display of current values of variables.
Qt designer vs qt creator software#
Our software is quite large and stepping through code takes several seconds for each line of code in Qt Creator. For this I always switch over to VS because it saves me hours. Nevertheless, I have to agree with the others that debugging inside Qt Creator is horrible. From my experience, using qmake directly to create a VS project tracks dependencies better (though not perfect) than using the Qt plugin for VS.
In this setup it is a little bit harder for him to add a file to the project because he can't do it in Visual Studio directly. My colleague, however, uses Visual Studio. I prefer using Qt Creator because I can navigate a lot faster. It is easy to create a VS project file from Qt project files using qmake. In the end it comes down to preferences if you want to use Qt Creator or Visual Studio for development. However, I believe that both Qt and Visual Studio support cmake projects. One way to go is to use Qt's project files and qmake.
Qt designer vs qt creator portable#
If you plan to have a portable application, I suggest that you use a single project file for all platforms.