General and Desktop

@jeremy_k Wow, Awesome ! Thanks for your answer and massive props to @VRonin !

Thanks @RokeJulianLockhart, but I have (hopefully!) just released the latest version of my Qt application (using Qt 5.12 because I wanted to keep on using QtWebKit, among other things) and I am now using new (more modern, IMO) technologies. I did enjoy my Qt journey though, although not some of the decisions the Qt people made these past few years.

Hi, An additional suggestion: adopt the new connect style using function address rather than the macro based version. You will have compile time error rather than run-time warnings printed in case of an error.

Thanks a lot for the quick follow-up! I'll provide this info in the KDE bug. Hopefully, we'll get that fixed soon …

@PVS71 Either embed the native window as Qt Widget in a container as shown by @jsulm in the linked documentation page OR you can simply create a QImage from cv::Mat and show the image data directly through Qt using a QLabel for example. What is the reason for you to want the OCV Image output window?

@thierryhenry14 said in How can I programmatically translate a QTranslator-translated string back to english?: Now my problem is that the backend expects the configuration settings to be sent in english. So for example, if there's a config combobox with the choices ["Red", "Blue"], the spanish-translated app would show ["Rojo", "Azul"], but if the user selects the 2nd choice and presses OK, I need to send "choice=Blue" over the network. With the proviso that I have not used QTranslator/tr("..."). This specific case is easy. Every library has a way of setting a combobox/dropdown item to have a display string but also a "value", which (if absent) will default to the display string, but can be set separately. For QComboBox the value is a QVariant and can be set in a variety of ways including addItem(const QString &text, const QVariant &userData = QVariant()) and QComboBox::setItemData(int index, const QVariant &value, int role = Qt::UserRole) and retrieved via QVariant QComboBox::itemData(int index, int role = Qt::UserRole) const, or you can do same via the QAbstractItemModel *QComboBox::model() const. Since you know you always need the English word from a Spanish choice you should store the original English word as the value while allowing the translation for the text. This is what @SGaist was referring to in his reply above.

That's surprising, both should show recursive behaviour. Because you modify the nodes wich would trigger a copy of the vector element. ~ Actually std::vector has no implizit sharing, it does the copy directly. Probably the reason why you see different behaviour.

Hi Yuri, I'm one of the posters you mentioned above. Sadly the solution I eventually went with was to use quickjs as our javascript engine which gives much more control over the java script environment and allowed me to create/control the plumbing around using c++ types within the javascript environment. Sorry i dont have any other help for you.

@ChrisW67 Thanks

@jsulm based on the link, I think this was an answer to an old question.

Because of you use not flag (set/unset) but value (like '-n 123'), you should also set valueName... So your code should be QCommandLineOption NumOption(QStringList() << "n" << "num", "help text", "num"); I ask Qt company to make warning message more user-friendly here.

@nicker-player The hyphen character (-) is often where word breaking occurs in English. On the other hand the underscore character (_) is treated a s part of a "word" and is not where wrapping gets chosen to occur. If QTextOption::WrapAnywhere does not work try WrapAtWordBoundaryOrAnywhere just in case that works better. I don't know what to suggest if none of these work.

@nicker-player You either have a query still active when you attempt to close the database, or perhaps you have kept a QSqlDatabase instance in existence and then are exiting your program. Check https://doc.qt.io/qt-6/qsqldatabase.html#details Warning: It is highly recommended that you do not keep a copy of the QSqlDatabase around as a member of a class, as this will prevent the instance from being correctly cleaned up on shutdown. If you need to access an existing QSqlDatabase, it should be accessed with database(). If you chose to have a QSqlDatabase member variable, this needs to be deleted before the QCoreApplication instance is deleted, otherwise it may lead to undefined behavior.

Feel free to log a bug after searching to see if one already exists.

@WolfgangGriech hi, From memory, the suggestion to have a plug-in and separate library is to keep the dependencies down to a minimum because otherwise you would pull the designer library into your application.

Hi @SGaist, Yeah that was a typo. And yes, after moving to v6.8.1, it seems that the problem is gone. Thank you.

That is what I thought. Thanks for the confirmation.

Okay thank you. I am now working on Ubuntu 22.04.5 LTS I believe I may have only one problem to solve now. How to influence imageformats path looking for imageformat libraries in the source path. All the other plugins are fixed by QT_QPA_PLATFORM_PLUGIN_PATH=/opt/.../core-64-poky-linux/usr/lib/plugins/platforms qt.core.plugin.factoryloader: checking directory path "/home/.../projects/.../src/ui/imageformats" ...