Qt Creator and other tools

Both open source and commercial versions of Qt support MSVC. VS installer has what is called workloads i.e. .net, desktop C++, UWP, android, azure etc. and I don't remember if that's still the case, but I think C++ was not selected by default. So although you have VS2019 installed you might actually not have C++ compiler installed. Open VS installer and check if you have desktop C++ development workload selected and install that if not. After that the C++ compiler should show up in your Qt Creator compilers tab and you can set up a Qt kit that uses it.

OK this will take some explaining :-) In order to run an application if you only have code, these are the necessary steps: qmake - creates build instructions for the build system (make or nmake) build - this compiles the source code and links it into a binary executable (by calling make). Build artifacts (object files, make files, debug symbols) are generated here and left in place - to speed up future builds (incremental builds) run - this simply instructs the Operating System to execute your application (same thing happens when you double-click an .exe file in file browser) Now, in Qt Creator here is what menu actions do: Build - this will run qmake if necessary, then run make (compile & link the executable) Run qmake - this will only run qmake (generate Makefiles) but it will not proceed with compilation Run - this will run qmake and build if necessary, then run (execute) your application Rebuild - this will clean, then run qmake then build Clean - this will clean up the build artifacts (Makefile, object files, debug symbols, MOC, UIC files etc.) leaving the build directory clean I hope this makes it a bit more clear. If not, please ask more :-)

@JonB Yep, I am a bit confused, there are so many different ways... I just want to know, whats the best one^^

@brighton64 not exactly sure what you mean by "main widget" i say QMainWindow with dock widgets but anyway, you can simply check the source yourself

@thierryhenry14 this problem sounds like QTCREATORBUG-20737 Looks like it should still work if you disable the Clang Code Model if that is an option for you. Regards

If Qt Creator packaged by a distribution does not work it is a problem of that distribution. Write to PSLinuxOS maintainers. Anyway, you can try linking Qt Creator with an installation. Go to Tools -> Options -> Kits -> Qt Versions -> Link with Qt... and browse to your Qt installation location. Alternatively, by far the easiest option - use the official Qt installer to get a full package: newest Qt Creator + any Qt version you like, all working together nicely.

Sounds like a bug. Are you using the newest Qt Creator? That's 6.0.1 at this moment.

Tools -> Options -> Text Editor -> Display -> Highlight Blocks.

Hi and welcome to devnet, Looks like your sources have an issue. I would ré-extract them and start fresh. Also, please use out of source builds so that you can more easily restart if something goes wrong.

@AnneRanch said in How to "select QT load " ?: I start QT creator via Ubuntu desktop icon on what version , not what kit , of QT is being executed. Are you asking about which Qt Creator you want to load, or which kit you want to build with, or which Qt you want your program to use at runtime?

Finally, I managed to fix the problem. Being the Qt Linux dilettante that I am, it took me one week: The Qt Online Installer that I use to install Qt on Arch Linux doesn't install qt6-wayland package and doesn't spread the Qt Wayland plugins to all places where they are needed. That's why Qt Creator 6.0.1 which is build using Qt 6.2.2 is not able to run in native Wayland mode and if QT_QPA_PLATFORM=wayland is defined won't even launch. The same is true for Qt Maintenance Tool. Because of that, both applications run on XWayland which results in blurry font rendering on HiDPI graphics. A manual workaround to enable Qt Creator's 6.0.1 native Wayland mode for example on Arch Linux / Wayland (with KDE Plasma 5.23.4 or Gnome 41 or Sway WM) is: Define QT_QPA_PLATFORM=wayland (for example in /etc/environment) Install qt6-wayland package: Copy directories: /home/user/Qt/6.2.2/gcc_64/plugins/platforms /home/user/Qt/6.2.2/gcc_64/plugins/wayland-decoration-client /home/user/Qt/6.2.2/gcc_64/plugins/wayland-graphics-integration-client /home/user/Qt/6.2.2/gcc_64/plugins/wayland-shell-integration to (overriding existing platforms folder) /home/user/Qt/Tools/QtCreator/lib/Qt/plugins/platforms /home/user/Qt/Tools/QtCreator/lib/Qt/plugins/wayland-decoration-client /home/user/Qt/Tools/QtCreator/lib/Qt/plugins/wayland-graphics-integration-client /home/user/Qt/Tools/QtCreator/lib/Qt/plugins/wayland-shell-integration reboot (to enable QT_QPA_PLATFORM=wayland environment variable) After that, Qt Creator 6.0.1 runs in native Wayland mode with sharp font rendering on HiDPI graphics. I wrote QTBUG-99429 report about it: https://bugreports.qt.io/browse/QTBUG-99429 Edit 15. February 2022: There was a typo in this post. The correct name of the environment variable that forces Wayland is: QT_QPA_PLATFORM=wayland

I am very happy to see someone try to explain this problem, thank you very much Chris Kawa. @Chris-Kawa For this Issue. I used that feature about 3 years ago, maybe 5... I know that "go to slot" button do the same things like that describe, at least before. I agree with your suggestion, using automatic connection signal is not a good way. I will connect action manually in the future. thanks for your adviced. @AhmedBedier I have bad luck for that Issue. But I have good news for you. Currently I am using QtCreator 5.0.3 and designer plugin 5.0.3 on Ubuntu 1804. This problem did not occur on that platform and version I used. Hope this message is useful to you.

SVNR = $$system("svn info --show-item=revision")

@AnneRanch Can anybody help to update this ? Start debugging in QT Creator as normal, stopping near the the code you wish to reverse debug (via a breakpoint etc). Enable the Window->Views->Debugger Log menu option. Cannot find the above The visible (Window) options seems to be only for edit At the bottom of the left pane which appears, type record next to the command prompt. Continue debugging as normal using the QT Creator UI (or the command prompt). When you want to perform a reverse step (rs), reverse next (rn) , reverse continue (rc) etc command, just type it into the command prompt. The UI should reflect the results of these commands as usual.

@Hammerfall said in Qt Creator MSVC2019 Kit Configuration: I also tried install Qt Creator 6.0 RC1 and it can successfully detect msvc2022. However, I don't have the Qt version for msvc2022. So, I think I have to wait for a msvc2022 Qt version. Thanks. I have installed Qt Creator 6.0.1 and MSVC2002 on my PC. With this configuration, I can compile Qt projects with Qt 5.12.x without any trouble. Qt Creator has automatically create the corresponding Kit.