General and Desktop

Sure enough the event filter worked! Thanks.

@Collaxd said in Mouse Pointer and Label Background Coloring in Qt Application with Multiple Labels: void HandLabel::dragEnterEvent(QDragEnterEvent *event) { Q_UNUSED(event); updateColorScheme(); } Oh, miss that drag enter is call for each label ! Even easier that I imagined. Despite the mouse having a 'block' symbol, the colors are working perfectly! You need to call ev->acceptProposedAction(); for that symbol to not appear.

@Teodor-Stefan said in Multiple calls to QCoreApplication::quit(): In Qt6 it seems to post the 'quit' event so that it makes sure the subsequent exit() will run on the main thread. I must've completely missed that.

@Saviz Sorry, I don't know such article. But basically create a settings object and store the settings in it instead of in widgets classes.

@Qt-embedded-developer said in How to manage resources in thread without blocking main GUI thread ?: so other system is using mutex because it has one part where it has to check sensors connection is there or or not What do you mean by "system"? Other application? Other thread? ...?

@aaron4124 So you probably have a working Qt C++ development environment. Python support does not come out of that box. See Qt for Python

As already stated, but to restate...No. You need to address mirroring on the X display level using someting like a screen scraping VNC server, or do what @ankou29666 mentioned and create two separate instances and link them with signals.

@DWJO said in Ui doesn't launch when using openGL widgets.: sometimes when debugging, the Ui doesn't launch Please clarify this. only when debugging? I might expect such behaviour in an otherwise correct program being debugged since openGL is its own command processing pipeline. think of it as "parallel processing". So, breakpoints in your Qt program might not consistently apply to what's going on in the GPU pipeline.

You don't override the value, just a pointer so you don't modify the object deleteLater() was called upon.

In the visual studio, we need to change the .h propeerty, set Item Type = "Qt Meta-Object Compiler (moc)".

@prathap Use another mirror. See here how: https://forum.qt.io/topic/143509/can-not-install-qt-6-4-2

I also tried the JSON for Modern C++ . I thought I wanted BSON, but after looking at all the wasted space in the resultant binary file, I tried CBOR, but too wasted too much space. MessagePack turned out to be nicely compact. I had a minor mysterious error if I created it with an initializer list, and then tried to assign a new datum via a string index, e.g.: j["foo"] = "bar"; It turns out it must be one or the other. It is well-maintained and up to date. I found it easier to use the one big include. I would use an official MessagePack API, but the vanilla C++ one requires Boost++ also, and there are about six other APIs which only use MessagePack output format. This one can use multiple output formats. I might use QJsonObject, but the lack of support for storing binaries as binary was a non-starter; and the much more compact format of MessagePack, without a CPU-expensive re-encoding of binary format was a winner for me. I hope in the future, QJsonObject will support MessagePack and non-reencoded binary fields.

@SGaist said in Shutdown remotly linux by qt app: @Damian7546 Hi, The most simple would be to use QProcess and use ssh to execute the command on the remote node. Which is 100% what I said :) @Damian7546 If you mean you can go into a shell and use ssh to invoke the shutdown command for a remote machine then you can do that from a Qt program via QProcess. If you mean anything else please clarify what you expect to do,.

Then it might be simpler to implement your own history state that can handle that special case.

@JoeCFD I don't understand why in your machine works