Qt Creator and other tools

Thx for explanation what the problem was. That is what I need. Marked topic as solved

Sorry; I would have edited the post but the site does not allow me. The error message I posted was from when I had my custom debugging helpers on. Them being on or not (or even present) has no impact on this failure, but they do change the error message slightly and I didn't want to confuse the issue with that oversight. Here is a version of the error with no involvement from those: <718python theDumper.fetchVariables({"allowinferiorcalls":1,"autoderef":1,"context":"","displaystring >&"python theDumper.fetchVariables({\"allowinferiorcalls\":1,\"autoderef\":1,\"context\":\"\",\"displaystringlimit\":300,\"dyntype\":1,\"expanded\":{\"inspect\":100,\"local\":100,\"local.boxHigh\":100,\"return\":100,\"watch\":100},\"fancy\":0,\"formats\":{},\"nativemixed\":0,\"partialvar\":\"local.boxHigh\",\"passexceptions\":0,\"qobjectnames\":1,\"qtnamespace\":\"\",\"qtversion\":331539,\"resultvarname\":\"\",\"stringcutoff\":10000,\"timestamps\":0,\"token\":718,\"typeformats\":{},\"watchers\":[{\"exp\":\"6d446972656374696f6e\",\"iname\":\"watch.0\"}]})\n" >~"bridgemessage={msg=\"b' COULD NOT ACCESS FIELD: union {...}'\"},\n" >~"bridgemessage={msg=\"b' COULD NOT ACCESS FIELD: union {...}'\"},\n" >~"bridgemessage={msg=\"b' COULD NOT ACCESS FIELD: union {...}'\"},\n" >~"result={token=\"718\",data=[{iname=\"local.boxHigh\",name=\"boxHigh\",address=\"0x555555f48b78\",size=\"12\",numchild=\"1\",sortable=\"1\",children=[],type=\"glm::vec3&\",value=\"\",},{iname=\"watch.0\",wname=\"6D446972656374696F6E\",numchild=\"0\",type=\" \",value=\"<no such value>\",},],typeinfo=[],partial=\"1\",runtime=\"0.012951968994457275\",counts={}}\n" >718^done <Rebuild Watchmodel 92 @ 23:19:10.586 [3141ms] > [GDB] Finished retrieving data.

@Jackie said in Agentic Chat Improvement in ACP plugin: Oh I see, sorry for posting in the wrong place. No worries ! You're not the first nor the last in that case. You came to the right place to get directions :-)

For me (Arch Linux) its this library: unixodbc Installing the library fixed that issue. using this config it loaded: ---@type vim.lsp.Config return { cmd = { 'qmlls6' }, -- may be 'qmlls' for you depending on distro filetypes = { 'qml', 'qmljs' }, root_markers = { '.git' }, }

@Nils-Sjoberg said in Constrain Clang-Tidy and Clazy to just one file: @SGaist With great pleasure, English is not my native language. Done :-)

Hi alex, i took me some time, i had to restructure the project so many components would become static libraries, but i have to say it was for the better. I like how everything became organized. Thanks for the pointers!

@Asperamanca https://codereview.qt-project.org/c/qt-creator/qt-creator/+/754371 fixes the issue. Do try it out when you have the chance! Thanks.

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.