General and Desktop

I don't remember what is the error message displayed in that case but all I notice is that you define a target name but next define properties for another target name. either you rename your project to appuntitled, or you rename it untitled everywhere else. But mixing "untitled" in project definition with "appuntitled" everywhere else won't work for sure. Best practice is to use ${PROJECT_NAME} variable : project (somename blablabla) qt_add_executable (${PROJECT_NAME} yourfiles) qt_add_qml_module (${PROJECT_NAME} URI your.project.uri RESOURCE_PREFIX someprefix VERSION 1.0 QML_FILES YourQmlFiles.qml ) it's more reliable template than QtCreator's defaults.

as far as I know, the official Qt Installer doesn't provide Mqtt for open source edition as prebuilt module. So unless you use commercial edition, you have to build the whole Qt from sources to have Mqtt available.

Thanks for the feedback ! Looks like a nice tool you are building :-)

@Christian-Ehrlicher, thanks for the explanation. That is totally fine; I was just wondering if I could create a style similar to it, since most of my desktop is made up of Qt widgets and programs, but a single add-line and sub-line will still do, of course. Thank you both nonetheless.

Correction, my mistake found by @JonB: Allocated on the stack, not on the heap!

Hi and welcome! Just by reading your problem description: The bug is in your code. In the last case, the user clicks on the All-checkbox. You intercept the click and set the current text to "None" I guess. When that's done, the checkbox processes the click as well and interprets as a selection of the item "All". That sets the current text back to "All". If you add connect(ui->comboBox, &QComboBox::currentTextChanged, this, [](const QString &str){ qDebug() << "Text changed to:" << str; }); somewhere e.g. in the c'tor of MainWindow, I bet you will see, that the current text is set to "None" before it bounces back to "All". Narrowed it down in the example. Nope. Way too complicated. See here.

Nothing is compatible Did you mean 'Nothing is incompatible' ?

Sorry, I forgot to update: This was a version I installed using the online installer. I switched to Qt 6.9.1 and it seems resolved now.

@jsulm After testing, the QService is unable to open other process programs

@cristian-adam said in Qt Creator for University classrooms: You can install Qt Creator without the need of a Qt account via Chocolatey as: I have never actually thought of that. I personally have chosen to use Scoop as a package manager (https://scoop.sh). They provide Qt Creator, but not Qt directly. However, they have aqtinstall (that you have already mentioned) as an option. I have never heard of aqtinstall before. But, it seems a good way to actually install Qt without an account. Lastly, I've checked Microsoft's own package manger WinGet: Haven't found Qt there, not even Qt Creator (but somehow Qt Designer?). And they also have aqtinstall.

I am sorry to say, but you haven’t responded to @SGaist: please provide a minimal compilable reproducer. I am also sorry to say that I do not understand anything in your reply. If you use translating software, that may be the reason. The code you posted is neither formatted correctly, nor enough to compile. Also Qt 5.14 has been EOL for a long time.

Hi, Can you check with a more recent version of Qt ? If memory serves well, there have been multiple fixes for high dpi.

@DavidFaure that was a sneaky one !

Thanks - I think something changed, either between Ubuntu 24 and 25, or Qt 6.8.0 and 6.9.1, as another machine with older versions does not show the issue. Still I guess it's cosmetic as you say, although I tend to be a bit pedantic about getting rid of unnecessary warnings/messages.

@StudentScripter Not as an immediate priority, but we are planning to implement something like dock widgets also in Quick Controls.

@GregB Install gcc 10, add that compiler in QtCreator and then create a new Kit where you select that compiler

@mirro Please post code as text, not pictures. In your code you're not waiting after calling exec() and you did not add any error handling as @JonB suggested. And did you check Windows logs as it was also suggested? You should use startDetached instead of execute if you're not waiting for the process to finish. command variable should be a QStringList, not QString.

Hi and welcome to devnet, This Wiki article might be worth a look. Hope it helps

@SimonSchroeder said in Where are the .ui files?: I am so vocal about it because I was taught to use pointers and new everywhere when I started with C++. Turns out that this was the source of most bugs. So, using stack variables almost everywhere (except for Qt's objects with parents assigned) helps to prevent a lot of bugs. (There are other reasons to use pointers related to OOP and polymorphism, but even then there are fewer cases than I was taught initially.) True. This correlates also with my experience. @Pl45m4 said in Where are the .ui files?: Have seen beginners creating everything, Qt and non-Qt related stuff, on the heap regardless... that could need some optimization :) Could be "bad" teachers, wrong guides or courses... or just the wrong assumptions that it needs to be done this way. People have heard "C++ is hard", "C++ is complicated", "Lots of bad black memory/pointer magic you can do"... which is kinda accurate... so they take the sledgehammer to crack a nut :D And maybe they get "inpired" by other OOP languages like Java, where you don't have to manage your memory yourself and new'ing something does not come with any drawback, therefore it's most used.