General and Desktop

@JonB said in Concept for analyze several XML messages, sometimes incomplete.: What exactly do you mean by this? I send and receive XML messages via socket, which I have to evaluate. There may be 0000 between the messages, other characters that are not necessary for XML. Presumably buffer with 000 The idea is to read <Root> XXXXXX </Root>. It may be that two messages come at once, too fast. How can I solve this? RingBuffer? Do you have a good example of how to solve this?

I think its the defaults command we were looking for !

If anyone comes across this, you can also achieve this by changing X11's WM_CLIENT_MACHINE property of your widget. Gnome will treat this as a different application. You can also see how gnome matches windows to applications here: https://github.com/GNOME/gnome-shell/blob/main/src/shell-window-tracker.c#L388.

@JoeCFD Thanks a lot, your solution works! @Christian-Ehrlicher thank you too! Problem solved.

@vivaat said in Bounding size of QTableView to parent widget: But is it possible to limit such a behavior? Maybe by overriding the mouseMove event.

Thanks for the answers. I figured it out for the cmake build system. For anyone who stumbles across a similar problem. I had to edit three lines in CMakeLists.txt, i.e., essentially add the keyword "Multimedia" to them: find_package(QT NAMES Qt6 Qt5 REQUIRED COMPONENTS Widgets Multimedia) find_package(Qt${QT_VERSION_MAJOR} REQUIRED COMPONENTS Widgets Multimedia) target_link_libraries(Countdown PRIVATE Qt${QT_VERSION_MAJOR}::Widgets Qt${QT_VERSION_MAJOR}::Multimedia) After that compiler and linker do find the corresponding files.

@gbettega said in Combo box (or equivalent) - "one click" behavior: One of the authors also explains how the drop down is immediately hidden after a mouse release event (as in your case), but at the end no conclusive solution exposed to the word. This went off in a tangent that I didn't expect. The intent was move from abstract discussion into a brief code example that cab be tested, and discussed in more concrete terms suggest looking at the implemented item view functionality before overriding lower level mechanisms Yes, the CurrentChanged edit trigger can have unexpected behavior. SelectedClicked is probably easier to work with. That takes one to two clicks (one to select a cell, one to edit the selection) to display the combo box popup, and doesn't appear to have the unintended popup close behavior. Sometimes it fails to create the editor, possibly when interpreting the second click on the newly selected cell as a double click.

Also: A problem on both MacOS and Arch Linux.

Hi and welcome to devnet, Do you expérience the same if you use ffmpeg directly ?

My app is translatable to a single language so far, not 31 as qtdeployer suggests. Anyway no options to skip collecting all available dlls "just in case" to deploy folder are available in documentations.

@Christian-Ehrlicher Thank you. It's fixed.

To be honnest, looking more deeply in Qhash than i'v done before, it appered that it was the perfect tool for a bit later. Once my thing is working and I have fixed my own mess, I'll take a look at improving what mess have been made before me.

@SGaist It is true. I guess few people would like to do that. We have MQTT, but do not use QMqtt module. There are other ways to implement mqtt with Qt.

@garlicbox as already written: the offline installers have not been available for open source users since before 5.15.2. So no.

See also QProcess::startCommand(), which seems to be equivalent to passing the results from splitCommand() into start(). This was introduced in Qt 6.0.

Like previously stated, the only real option you have is to start a separate process from your Qt application. This process loads the DLL and performs the calculations. You can then terminate that process at any time, and the operating system will take care of cleaning up memory, handles, and other resources. The only potential downside is the risk of corrupted files, if the DLL performs file operations. Communication between your main application and the second process can be handled via QSharedMemory, QLocalSocket, or standard input/output piping.

Ah, found this issue right after posting while doing some more thorough review of my overridden methods. Hopefully it helps someone else. For those converting QSqlTableModels to QSqlRelationalTableModels be careful what methods you're calling! In the below code I forgot to update the base function call to QSqlRelationalTableModel so it was still calling QSqlTableModel::insertRowIntoTable(const QSqlRecord &values) which led to these issues. bool PolicyModel::insertRowIntoTable(const QSqlRecord &values) { QSqlRecord rec = values; rec.setGenerated(Policy::DataRole::Id, false); return QSqlRelationalTableModel::insertRowIntoTable(rec); } I had overridden this method because the primary key is an AUTO_INCREMENT field.