General and Desktop

For me it was because when I switched to a 6.8 kit, the "deployment configuration" quietly got set to "Automatic Application Manager Deploy Configuration". As far as I know, I have no need for Application Manager (and evidently, like you, don't even have it installed). I also don't know why it happened for this project and not another, but perhaps because this one is a QtQuick application? I just changed the configuration back to "Deploy Configuration" (which has No Deploy Steps) and all is well. You can find these settings by clicking on "Projects" in the left hand button pane in the Qt Creator window. [image: e47f7762-eb4c-434e-b793-8405a5fbc3d6.png]

Thank you, @JKSH. That's great there's a facility in cmake for this on some platforms.

@cristian-adam Thanks for the attempt for a workaround. I'm using 'init-repository' ; so not sure how to implement that trick + code.qt.io links are hard coded in QT src files, thus I've poor expectations :( Thanks !

Sorry took me a while to get back to this. I found the error and it turns out I did not use consistent uniform bindings between my vertex and fragment shader, you know, one of those ID-10-T errors :). Interestingly, OpenGL didn't seem to care and worked fine regardless. Anyways, the volume rendering is now working on all backends.

@SimonSchroeder said in Dark color scheme on Windows best practises: 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. I would say it's more than a few people who will be getting the Extended Security Updates for the next 11 months, and, after that, there still remain long term supported Enterprise versions of Windows 10, with support through January 2027 and 2032. There are definitely going to be lots of people trying to find ways to not make unnecessary e-waste out of their otherwise still functioning hardware.

@Axel-Spoerl I can try later after rewriting some of the code to compile on Qt 6.

Thanks, for comments

Excellent! I will start to try what you sent me! Thank you all!

@rmccampbell Good question, worrying, and I don't know the answer. The only thread I could come across confirms it is not thread-safe but I'm not sure it answers your question or the implications. However it is worth reading through: Is it safe to use QClipboard in a background thread

Hello again, it took a while to fix this behave. Just to let you know I added the command to the dialog on calling setEditorData setFocusProxy(ui->editLine ); hope this helps also someone of you.

@Dadde As @Christian-Ehrlicher says. To be clear, you cannot influence how the JSON output is written (nor how it is read) in the JSON producers/consumers I know. They only may allow you to influence the irrelevant spacing/indentation/newlines output format, like enum QJsonDocument::JsonFormat.

@John-Van said in After using toStdString, the string exhibited abnormal behavior.: @Christian-Ehrlicher Yes, this issue only occurs in debug mode, but it uses debug libraries. Is this a bug in version 5.15? @Christian-Ehrlicher is suggesting you are mixing debug and release libraries. Check your compile/link commands carefully, particularly how you are compiling your code versus which libraries you are using/how they were compiled. We have often found that people are inadvertently e.g. compiling for debug but linking with release libraries or vice versa, which is not allowed and leads to unexpected behaviour. Also if you have a Windows problem please state what compiler you are using --- MSVC or MinGW, we cannot guess. You now have responses indicating it works correctly with each of them.

@Bonnie Apparently it only works for 6.10 for me. Followed the same procedure for each version.

Hi, I guess all the problems comes from Trixe? I think I need to go back to Bookwarm. Regards, Mucip:)

Hi, Which version of lupdate/linguist are you using ? On which Linux distribution ? Did you check the logs of linguist to see if there's anything there ?

@jronald said in Hard to find some docs for QtGraphs in C++: For the code above, I can't find the keys (like seriesList, axisX, axisY) Those look like properties from GraphsView: https://doc.qt.io/qt-6/qml-qtgraphs-graphsview.html

There is no race condition but you use QGraphicsDropShadowEffect for a child widget with a radius of 10 so this widget is responsible for drawing everything of it's size + 10 pixel which overlaps with your progressbar. I don't understand why you use QGraphicsDropShadowEffect with this large radius at all. What do you want to achieve for a plain QWidget not in a QGraphicsScene?

It seems to work if you add CONFIG-=entrypoint without any spaces(!) in "Additional project settings": [image: ec983e64-6a58-4f20-90a1-4f51aea64176.png]