General and Desktop

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.

I am marking this as solved, since I developed a work-around for what I am doing. Basically, I am using the following characters which are supported by the most common fonts: Description Symbol Unicode valiue Carriage return (CR, 0x0D):     ¬ U+00AC Line feed (LF, 0x0A): ¶ U+0086 Space (SPC, 0x20): · U+0087 Tab (TAB, 0x09): → U+2192 Invalid code point: � U+FFFD Miscellaneous control code: ¤ U+00A4 If Invalid code point or a Miscellaneous control code are detected, the user can hover over the character with the mouse and a tooltip will display the actual Unicode code point as a hexadecimal number. Thanks for all the useful suggestions!

@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

@jsulm said in Change font on QTextCursor before start typing any text: Aren't you changing a copy here? Yes, but as I understand it, there is no other way to get a QTextCursor other than QTextCursor DocumentHandler::textCursor() const { QTextDocument *doc = textDocument(); if (!doc) return QTextCursor(); QTextCursor cursor = QTextCursor(doc); return cursor; }

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