General and Desktop

You're right. But I have to call up the dialog within my measurement class. Even if I change that, it doesn't solve my original problem.

Aside from all the other valid args against embrasing AI, you do understand that since AI is heavily dependent upon cloud info database, while it is free now, the marketing model is always "suck them in with freebies, get them dependent, and then charge them up the wazoo"? And for the record, I've dumped every tool that has an AI assistant in it. They just scream "data-mining!!!!"

@APSH said in Change QMenu Shortcut text color: Is that not supported for customizing QMenu and it's keysequence? no - it's one text

Any news on this issue? It's still broken in Qt6.

I don't know. But how do we or you know whether you are using style windowsxp or windowsvista? Simple common sense: Start by removing the if and testing once with windowsxp or windowsvista unconditionally. Does that make any difference? If yes then it's something to do with style, if not then the style is not at issue.

@Joeblack said in Background Image not display.: What did I missed? The ":" after background-image.

@JacobNovitsky said in Unknown module(s) in QT: webenginewidgets: Cannot obtain the lock for file "/home/j/.cache/qt-unified-linux-online/cache.lock": Resource temporarily unavailable Is Qt Online Installer still running? If so close it and try again. If it does not help delete that file manually.

In fact. I wrote the data in a new std::thread and then post the result to the qt ui main loop. Now I just used the emit way to send the data to the ui loop.

I had no problem at all building and installing QT Creator port on FreeBSD 14.3 using Poudriere.

@l3u_ said in Dark color scheme on Windows best practises: I think the best approach would actually be to leave Windows 10 as-is As of Oktober this year almost nobody should be using Windows 10 anymore (though many will). Official support is ending by then and you'll be vulnerable to attacks. A few people might opt-in to extended support for a couple more months.

@SamiV123 said in Qt Window positioning: Somehow maintaining things is also possible..just look at Win32 API that is stable and one can take an app written 20 years ago and still run it today. I am not sure if fixing a bug, then noticing it breaks certain software and because of that writing a work around to keep the bug when that software is running is a good strategy. You don't get the best API when it's totally bloated. It takes more time to maintain a larger API which means less new features (and fewer bug fixes). Also, I choose C++ as programming language because I need good performance. This also requires good performance of the libraries I'm using. Qt is one of those libraries. I would claim that bloated libraries (with work arounds like in Windows) steal some of your performance (work arounds are not free if you don't need them). Honestly, we are also still using Qt 5. (But we also have one student using Qt 6. It is not too much work to port.) We are a small company which mostly survives not from software sales. We don't have the money (and time) to constantly switch versions. I am not sure I need 20 year-old software running perfectly fine today (probably it wouldn't because we didn't have 4k high-resolution displays back then). However, it would be nice to only have to switch every 10 or 12 years or so. Large software companies might be able to switch every 3 years, but small companies (and hobby projects and small open source projects) might need much longer stretches. So, I agree that we need longer maintenance periods, but I'm not sure if the Windows model is the right one. (Apple's maintenance model is too short for me. They are already fading out Rosetta 2 and my 2015 MacBook Pro has also not been supported for several OS versions for no specific reason.) PS: Windows also occasionally drops support. At some time they have dropped support for 16-bit applications (but that has been probably more than 20 years). I also remember that I couldn't install some software (which would have still run perfectly otherwise) because my hard drive was too large. (Remember back in the day when installers would compute install size and would let you install if there wasn't enough space? Once your hard drive gets larger than they expected you get negative hard drive sizes reported.)

Here we are: https://bugs.kde.org/show_bug.cgi?id=509488

I have selected 6.9.2 , this is available with older versions (but I really don't want to go back)

This code works, however. QSoundEffect no on Kubuntu, works on Windows, but it works on Kubuntu and older versions of Qt. QMediaPlayer *p = new QMediaPlayer(); p->setLoops(2); p->setSource(QUrl::fromLocalFile("/home/tony/Code3/Qt9/MPltest/test.wav")); QAudioOutput *outPut = new QAudioOutput(); p->setAudioOutput(outPut); outPut->setVolume(100); p->play();

can you share the gstreamer link or pkgconfig exe

@APSH What does your question have to do with this 5 years old topic? You should create a new one.

Hi, I still got this issue on Qt 6.8.3. Anyone has found some way to resolve this problem? Thanks! Error setting up serial port /dev/tty.usbmodemCACF62D63C042. open: Operation not permitted