Qt Creator and other tools

Excellent ! Happy coding !

@Simmania said in "QML module not found" error when importing custom qml module: [cmake] CMake Error at custom_qml/MyButtons/CMakeLists.txt:4 (set_target_properties): [cmake] set_target_properties Can not find target to add properties to: [cmake] MyButtonsLib You've swapped the order of qt_add_library() and set_target_properties(). The order in your previous version was fine; you must define the target library first before you can set its properties. When removing line 4, I get the error message: [cmake] CMake Error at C:/Qt/6.11.2/msvc2022_64/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:1539 (message): [cmake] Metatype generation requires either the use of AUTOMOC or a manual list of [cmake] generated json files So that lines seems needed. You don't need it if you called qt_standard_project_setup() at the start of your project. This automatically enables AUTOMOC on all of your targets (and it also enables other features): https://doc.qt.io/qt-6/qt-standard-project-setup.html#description Note that I'm not sure about target_link_libraries(appstudio PRIVATE Qt6::Quick MyButtonsLib ) Maybe that should be target_link_libraries(appstudio PRIVATE Qt6::Quick MyButtonsLibplugin ) But it seems to make no difference. For STATIC modules, the official examples use *plugin: https://github.com/qt/qtdoc/blob/v6.11.2/examples/demos/mediaplayer/CMakeLists.txt#L31-L33 (Note: In practice, you could probably omit "MyButtonsLibplugin" and rely on qmlimportscanner to automatically find it... but I like to specify the link for clarity)

@Louis100 Hi, Check this post about accessing the bug report system.

@aha_1980 good point ! I did not think of the snapshots.

@JKSH said in Trouble Running Project: Please use a currently-supported version of Qt (the latest release is Qt 6.11.3) and load a different demo. If you give us some details about what kind of functionality do you want to see and what operating system(s) you want to develop for, perhaps we can help you to find a suitable, more up-to-date demo. If you're after an instrument cluster demo, the most recent one I could find for desktop/embedded platforms is https://git.qt.io/public-demos/qtquick3d/-/tree/master/XaxisCluster -- this can run on Qt 5.15, but not on Qt 6. Note: Nowadays, manufacturers are using automotive-specific operating systems and MCUs for creating automotive software (including instrument clusters). So you'd want to look at Qt for Android Automotive, Qt for MCUs (Qt Quick Ultralite), and Qt Safe Renderer. These are commercial-only products, however.

In the locator (the little search box in lower left corner) type t Show Menu Bar and press enter. Once you have menu back in the View menu there's a Modes submenu. In these select either Icons and Text or Icons Only option to show the side bar.

@SimonSchroeder The question is why the change in behaviour: but qc18 is ok, qc20 cannot open the same FILE MACRO Your statements are true, but why does behaviour apparently differ from Creator 18 to 20?

I moved the output folder to a local folder inside the VM. That seems to solve the problem. Only issue now is that when I run a build the Build Settings right beneath "Build directory" say: "The Makefile is for a different project. The build will be overwritten" This is only for the active build. When I change from debug to release, the message disappears in debug and appears in release and vice versa. It won't go away when I specify a full absolute path to somewhere in the local file system. It's bit strange, because Debug and Release builds are compiled into different folders without problem. Nothing is overwritten.

@JKSH Thanks!

Hi, AFAIK, no. The most simple is to update your CMakeFiles.txt and either comment out the lines with the files or delete them.

Thx! Guess it is better to start with plain .cpp and .h file for now.

@Joe-von-Habsburg said in Elided settings limit error: any solution here? due to settings limit So did you check the settings for such a limit?

Thanks for the suggestion, but I had actually tried all that before posting my query. I finally did solve it by checking my path statements. On build I have it configured to put the final .exe in a 'bin' folder and a few project-associated .dlls in a plugins folder in the 'bin'. When I ran the windeployqt.exe to get the latest Qt .dlls for all that, I had the path wrong, so apparently got incorrect .dlls.

I have prodded the wizard some more and found the following: If you take the above config and remove the Debug Configuration it successfully created the project. (Although there's some issues when compiling) Setting the build system to "CMake Project for Qt" always fails with "Object reference not set to an instance of an object." once a linux target is selected The with the project created for WSL Visual Studio complains that this is targetting WSL1 and that the QT Installation path isn't set correctly So yeah I guess I'll have to this very diffently than expected

@HansKottmann said in qDebug() is not working anymore in QT-Creator (Installed from QT-Installer from QT.io, OS: Manjaro Linux: The only thing I've changed is the args QStringList, it looks now exactly like yours, the only difference are the quotation marks at the beginning and the end of the file path string because filenames can have white spaces: I already explained earlier that you are calling errorString() too early. So did @jsulm . And what to do about it. Your Unknown Error currently does not indicate anything has gone wrong. You need to change your code. Your understanding of whitespace as it appears when you type a command into a shell versus how to pass arguments to spawned processes is not right. The arglist should be as a wrote and not have quotes. Or send the whole command line to bash -c.

@Jennise-Hall said in Qt desktop app crashing at startup: @SGaist LOL useful information though. Agreed ! :-)

Download from qt.io/download-qt-installer-oss (not the generic address) and log in with a new/clean Qt account that has not previously been linked to a commercial or trial license.

Hi again, in the meantime our clang experts are working on a solution for using lldb. I'm sure they will do it well. I still have another issue with lldb. But therefore I will start another thread or even create a bug ticket. And for the issue with gdb not showing the object member values (which was my original one) I first will try to find out, whether there is a new gdb version doing it better.