Qt Creator and other tools

Agreed that some screen elements can look small on a 4K monitor, but since you're spending all of your workdays in Qt Creator, eventually you'll learn all the keyboard shortcuts and perhaps introduce some of your own (at least I have).

By then you'll permanently hide the menu with Ctrl+Alt+M and don't mind small-sized elements on the screen because they're fixed/static and you know them very well by heart anyway. My own C++ code, of course, that needs to visible and some days I'll increase the font size :-)

@Elerence-Hooke

Not 100% sure for Qt DesignStudio but also with QtCreator most UI elements are only available through code as just a few are selectable from QtCreator's Widget toolbox. Menus like QMenu is not one of them.

@Renu hi,

QtConcurrent already running tasks in different threads, why do you need to create a new separate one ?

Try disabling the code completion for Qt Creator, something like clang or clangd. You will have to hunt through all the settings/options, I cannot recall where it is (and am not running it now). You want to get the stage where Creator does not make any suggestions/comments on your code, or at least is not using the default clang to do that. Does that make the problem go away? Or, for example, if you have Creator running but no project/files at all open/loaded inside it, does it still happen?

It is not sufficient to enable modules for the compiler. Your build system (CMake in this case) needs to now about modules as well to compute the right dependencies. You have to tell CMake which files are defining modules (maybe have a look here: https://cryos.net/2024/01/c-modules-and-cmake/). Otherwise your build might fail (it also might just work right most of the time if the dependencies are accidentally compiled in the right order). If I'm not mistaken modules with CMake so far only work with the ninja generator.

The reason why the build system needs to know about that is because if the compiler is looking for a module and it hasn't been compiled yet, there is no way for the compiler to tell the build system to just build the necessary module. So, the build system has to make sure that all modules have been built (in the right order) before regular compilation starts. (It would be certainly nice if the compiler could just compile the required module as well and then continue. But this is not how it works.)

Thank you for opening a bug report: https://bugreports.qt.io/browse/QTCREATORBUG-32293

Thank you so much for pointing me at these settings!
Disabling the QML debugging had no effect BUT unchecking "Run in terminal" solved the problem!
RunInTerminal.png

This might help.

Come to find out I was removing a label that didn't have any visible text when moving items around the UI. Once I added it back and/or removed it from the .cpp files, the UI compiled fine.

@kkmspb you're welcome!

That's likely related to the old forum which rendered double $ as single hence using a space was mandatory in the answer to show that two were required.

@shokarta
perf is only available on Linux, not Windows. E.g. https://stackoverflow.com/questions/34641644/is-there-a-windows-equivalent-of-the-linux-command-perf-stat. I don't think MinGW offers a perf. You would have to search around for your own equivalent, and change command line. Basically you might want to try to do it externally from Creator.

Linux perf I think would not tell you anything/much about what's going on in JS scripts. Don't know about Windows, MSVC has a profiler, don't know if you can use it best outside VS.

https://forum.qt.io/topic/129737/qtcreator-5-performance-analysis-on-a-windows-10-platform
https://training.kdab.com/portfolio/debugging-and-profiling-qt-applications-on-windows/
https://wiki.qt.io/Profiling_and_Memory_Checking_Tools
https://stackoverflow.com/a/34689067/489865

For latecomers, you could keep track of this issue here: https://bugreports.qt.io/browse/QTCREATORBUG-32283

@dano said in Qt VS Tools not (fully) working with MSVC 2022 & Qt 6.8.0:

but now the Qt VS Tools (version 3.3.1 (rev.1)) seem to have stopped working.

Do you mean this bug? https://bugreports.qt.io/browse/QTVSADDINBUG-1284

If not, please elaborate -- What exactly has stopped working?

+1. View is greyed out. Also having a weird problem of this version hogging focus.

Arch Linux Latest w/ Sway (Wayland)

Thank you for creating https://bugreports.qt.io/browse/QTCREATORBUG-32220!

I've figured it out: the trick is to use the menu item "Build for run configuration..." and assign that the Command+B keystroke.

@jimbrownqtuser said in Default project fails:

The solution was to change the desktop kit so the C++ compiler was GCC instead of CLANG.

Indeed! I can only say that my 24.04 installation (with Qt6) did this already, I never had a problem.
It's obviously not helpful that it creates a project yet then cannot handle it.

Hi,

It's likely the code model that is at play.
You need to do some more spelunking to determine what exactly are the hot paths.

@cristian-adam said in CMake Tool is unconfigured. CMake generator will be ignored.:

Try to register a manual CMake tool and set that as default.

Sometimes this helps.