Qt Creator and other tools

@lacuna Post it here and we’ll have a look!

@Kaluss Actually, maybe you could run clang on your files to get those output somehow, but I don't know.

@Costica said in RS485 with qt version greater or equal with 6: #include QSerialPort they complain that this is not available. Because you did not install the QtSerialPort module.

@Ifeanyi-Chukwu Qt6 is not supplied as 32-bit pre-built binaries. I believe it supports 32-bit only if you download sources and build for yourself.

@dearqt See https://askubuntu.com/questions/4694/how-to-use-a-iso-image-as-a-cd-rom-repository

@JonB "copy" solved the problem of placing the items, but can you explain to me how I can make it work? Like in the case of the 'if' above, here's my code and it also says that it doesn't have the 'clang' and other items. [image: WA4FfT2.gif]

@dpcrd said in Qt Creator : how to invoke uic automatically ?: @JonB : I love your way of "solving" problems 😂 ! Why didn't I ask some AI to do my job ? But wait ! How about my wages, then ? 🤔 I very rarely refer to ChatGPT. I did on this occasion because I did not know the answer and had trouble finding it. Your script always runs uic on every .ui file. If properly integrated into the build process it would only run it where .ui file timestamp newer than generated ui_....py file. However I guess it does not take too long.

In the meantime, I found the solution for me that works here: https://lists.qt-project.org/pipermail/interest/2017-December/028990.html I have the .cxx file in a separate folder called locale which I exclude (along with 3rd-party code) like this in the .pro file: lupdate_only { TR_EXCLUDE += \ ../3rd_party/* \ src/locale/* } At first, this didn't work until I realized that the /* after the folder name is important. Also, my lupdate finishes now in a second or two, as opposed to several minutes before. :)

OK, the solution was indeed to add ENVNAME\Library\bin to PATH... with the right syntax 😉.

Hello @Chris-Kawa, we tried many things and found a solution for our problem. The main problem was the given Includes are ignored. [image: 3b732675-7fdd-4d36-a60e-2c7b8d4df66a.PNG] We set "Override C/C++ Properties" to "Extend" and append all include paths in "Additional Inlucde Directories". [image: dab6d750-aed6-4536-a9da-648204b30a17.PNG] Is that a bug? We got another little problem with the C/C++ Preprocessor Defines. We cant set them because in the project was only one cpp file in our project and this is set to moc. We had to add a dummy.cpp file so you can get the C/C++ tree tab. [image: fd9f5e30-1597-4825-b3e9-5ea09a8e0f3e.PNG] Thanks for your help.

@jsulm I have solved the problem. Thanks a lot

@abdelmaegd said in qt_add_resources error: Is this issue in the macro itself ? No since the macro only invokes cmake and rcc so you should create a cmake bug report but I doubt this will get high priority - even you're correct a qrc file is not meant to be modifed by anything else but the Qt tools.

You need to enable the QmlDesigner plugin in the plugins dialog. https://www.qt.io/blog/qt-creator-6-released mentions this as: The integrated Qt Quick Designer is now disabled by default. Qt Creator will open .ui.qml files in Qt Design Studio. This is a step towards a more integrated workflow between Qt Design Studio and Qt Creator (video). Qt Quick Designer is still there, you can manually enable it again by checking the QmlDesigner plugin in Help > About Plugins.

@JonB when you target class with mouse it outputs extra details, but I want it to be static is there a way?

@jsulm Wow. Thanks. That worked. I guess I was not paying close attention that when I did it before, I right clicked on the container (QDialog) and not the widget (QTabWidget) in the container to get the QTabWidget to expand. So right clicking on the QTabWidget and selecting Lay Out in a Grid expanded the QTextBrowser. Was a long day and I guess my attention span was waning.

See https://bugreports.qt.io/browse/QTBUG-102965 - remove Q_DECLARE_METATYPE(QList<QObject*>) from the header or update to Qt >= 6.3 or use the workaround mentioned in the bug report.

@trangggg Come on, I gave you the link! Did you check it?