General and Desktop

@ankou29666 you don't need to build the whole of Qt if you need to add a single module to an existing Qt installation.

made a try with 6.8.3 on mac, the default template makes project untitled and everywhere else is appuntitled. builds fine, fine. (just complaining that virtual keyboard is not installed, I don't really understand why but doesn't matter). So yeah looks like the name given in project doesn't have to match the name given in qt_add_executable.

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

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.

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.

@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.

@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.

I didn't expect this (but admit that I should have checked it earlier...) Using 6.9.0: When selecting "winrt" as engine it output the format error, but using "sapi" it works. Using "winrt" the Application Output shows "QAudioSink::start: QAudioFormat not supported by QAudioDevice" Still don't know how to fix the problem for winrt, but it's a step forward. Also, the application needs to work for alle engines the end user select in order to support all locales and voices. It would be interesting to know if this only applies to my setup or if anyone else using Windows 11 and Qt 6.9.1 experience the same issue with this code I still can't figure out how to set the format of the default output

Hi @SimonSchroeder Nope. I build the projects in Release mode.

It looks like that doc page was updated. A requirement line encompasses all the Android requirements, and it states that QC can download these for you.

Thanks @Ben-Campbell-Wallis and @JonB for the reply.