@Christian-Ehrlicher , I added below line in main.cpp but nothing changed in Debian 12. QApplication::setStyle(QStyleFactory::create("Fusion")); MainWindow w; Regards, Mucip:)

Hmmm some digging shows that the lxqt-qtplugin is shipped with the system as: /usr/lib/x86_64-linux-gnu/qt6/plugins/platformthemes/libqtlxqt.so But my install takes the theme plugins from /opt/DeepSkyStacker/plugins/platforms/platformthemes which contains plugins that were copied from /opt/Qt/6.10.0/gcc_64/plugins/platformthemes on my build system which doesn't include the lxqt plugin. As lxqt does ship a suitable plugin, how can this be included as part of the Qt6 distribution for Linux (not the one that comes with the system as I have no control over the level of that!). Looks like the QT distribution should also add a plugins/styles containing at least the Breeze and Kvantum plugins as shown here from the startup of an lxqt aware qt app (the desktop) on the system: Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: qt.core.plugin.factoryloader: checking directory path "/usr/lib/x86_64-linux-gnu/qt6/plugins/styles" ... Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: qt.core.plugin.factoryloader: looking at "breeze6.so" Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: qt.core.plugin.loader: Found metadata in lib /usr/lib/x86_64-linux-gnu/qt6/plugins/styles/breeze6.so, metadata= Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: { Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "IID": "org.qt-project.Qt.QStyleFactoryInterface", Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "MetaData": { Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "Keys": [ Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "Breeze" Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: ] Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: }, Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "archlevel": 1, Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "className": "StylePlugin", Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "debug": false, Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "version": 395776 Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: } Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: qt.core.plugin.factoryloader: Got keys from plugin meta data QList("breeze") Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: qt.core.plugin.factoryloader: looking at "libkvantum.so" Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: qt.core.plugin.loader: Found metadata in lib /usr/lib/x86_64-linux-gnu/qt6/plugins/styles/libkvantum.so, metadata= Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: { Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "IID": "org.qt-project.Qt.QStyleFactoryInterface", Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "MetaData": { Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "Keys": [ Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "kvantum", Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "kvantum-dark" Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: ] Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: }, Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "archlevel": 1, Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "className": "KvantumPlugin", Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "debug": false, Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: "version": 395520 Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: } Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: qt.core.plugin.factoryloader: Got keys from plugin meta data QList("kvantum", "kvantum-dark") Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: qt.core.plugin.factoryloader: checking directory path "/usr/libexec/styles" ... Oct 30 09:10:05 charon org.freedesktop.impl.portal.desktop.lxqt[368070]: xdp-lxqt: Desktop portal registered successfully Thanks, David

I think I figured out what is happening. I did not have a look at build_qtcreator dir (my bad). cmake -G Ninja "-DCMAKE_PREFIX_PATH=../install_qt;../libclang" ../qtcreator cmake --build . --parallel produces a valid app bundle called Qt Creator inside build_qtcreator dir. It references libs from install_qt so it can be run only locally. cmake --install . --prefix ../install_qtcreator produces invalid app bundle in install_qtcreator dir. This app bundle does not work even locally. The script SIGNING_IDENTITY=- ./scripts/build.py --src . --build ../build_qtcreator --qt-path ../install_qt --llvm-path ../libclang --no-sbom --no-dmg --no-zip produces valid, relocatable app bundle with all the dependencies being packed inside. The problem seems to be solved. Thanks everyone.

@Jim-G said in Selection highlight is a thin blue bar at the left of the cell.: So why does setting alternatingRowColors cause the change in highlight? Qt tries to use the OS default widgets first. Alternating row colors is not supported by the OS directly. So, Qt will draw it from scratch and usually tries to mimic the OS look. Seems like it did not get updated, yet.

Compiling Qt yourself for the right compiler version is the right way to go. One simple workaround is to rename the folder of the Qt installation, then uninstall MinGW. Even if it tries to uninstall Qt as well, it will not find the folder. After that you can (and really should) rename the Qt folder back to its original name (some tools have their path baked into the executable).

@SamuraiDestroy Qt widget layouts is a dark art. Everything you do in Designer is saved in (fairly) readable XML in the generated .ui file, nothing else. You can look at that to try to figure what is going on, and if you are really stuck you can paste it here and people can tell you what you need so long as they understand what you are trying to achieve.

@Axel-Spoerl Sorry. It looks like the black rectangle isn't a regression, but rather the implementation of dark mode support. In version 6.8, dark mode wasn't applied automatically. If the system color theme is light, both versions look identical. Qt 6.8.3, Dark theme, scale 100%: [image: 71a73ecd-1d25-45ed-8f99-4f2ec5c51524.png] Qt 6.12.0, Light theme, scale 100%: [image: 8b33cb68-132d-4875-abc8-16958c5d9507.png] Interestingly, even at 100% scale, the scrollbar looks a bit jagged in both versions, even though the scrollbar itself is straight. However, Fusion.ScrollBar looks good. Thank You. [image: 31dff5ec-b1ac-45f7-a7c0-780738a887fd.png] Should I close the topic as resolved?

@SiFox Thank you ! :-)

Is that white background different in other apps ?

@JohnBen said in Can QT Widgets be used directly with C#?: I'm probably going to have to slouch back to Gdk.... Before you do, would you consider giving Qt for Python a chance? It does provide direct bindings, so Widgets are fully supported. As for the Qt Bridge for C#, for now it will remain focused on Qt Quick / QML. But we would like to also offer support for Widgets at some point. This can be achieved by reusing the interop framework of Bridges to expose the necessary API's as C# types. However, we don't yet have a schedule for the development of that feature.

Classic macOS breaking platform consistency again. We ran into the exact same issue after updating our build machines — calling the static QFontDialog::getFont basically turns into a dead end because the native panel now behaves more like an inspector rather than a traditional modal dialog. Setting the QFontDialog::DontUseNativeDialog flag is pretty much the only sane workaround right now if you rely on blocking modal flow with OK/Cancel, even though the Qt-rendered dialog looks noticeably out of place on newer macOS versions.

Thanks a lot @IgKh for your inputs, it gives some light. Looking for CUINamedVectorGlyph crash with macOS 27 I found indeed a lot of reports, and this seems to be a quite well known issue... It seems the problem could come from a locale not using the period as decimal number separator such as... French locale, which is the setup my users have (comma is used as separator). This could also explain why with a US locale the problem doesn't occur. If you have means to retest my little code above with a French locale on a macOS 27.0.1 system it could be useful to verify. Thanks again.

Since the XCB version creates a valid surface while the X11 version returns a null surface, it does sound like the issue could be related to the EGL platform configuration. It would be interesting to see whether the same behavior occurs with a different Nvidia driver version or a minimal Qt example.

Your best bet is opening a sales ticket directly inside account.qt.io while your evaluation is running. That immediately pings a rep in their CRM, so they usually get back to you way faster than waiting on email. Also, if you're dealing with company procurement and need a local fapiao, going through a local software distributor in China is often way less headache than buying directly from Qt HQ. Calling the Shanghai office directly during regular work hours usually works too if you don't mind following up by phone.

@JonB the original QWebView class was indeed part of QtWebKit which was superseded by QtWebEngine. At some point the QtWebView module was introduced to provide a webview using the native backend of the OS. For example, on iOS it's mandatory to use Apple's API if you want to display web content. Android also provides something. On OS without a native webview component, QtWebEngine is used. The goal of the module is to be lighter weight (unless no native component is available so WebEngine...)

@SGaist thank you for your reply, I will try and If I will have a question, I will return :)

@cristian-adam something like that would be great.

Hi, Additional info about the 0 byte component: WebAssembly category node (0 bytes) with multithread and singlethread nodes below it was added between the 6.12 development releases and that causes the MaintenanceTool view to not look right if you had previous development release installed. Run "Update components" before "Add or remove components" to fix the "Add or remove..." view. Fresh installs and upcoming releases will not see this issue.

@Irimitlad said in How to fix missed libicui18n.so.74 when adding qmake to Qt Creator?: libicui18n.so.74 => /usr/local/lib/libicui18n.so.74 (0x00007457a4200000) Why is it looking in /usr/local/lib? Did you install this lib by yourself? Regarding installer being stuck: take a look at https://wiki.qt.io/Online_Installer_4.x#Selecting_a_mirror_for_opensource

I still have the problem of extra padding around the check boxes and the top messages in 6.12.0. I probably can override this manually but I feel I shouldn't have to. changing the setStyle() between windows11, windowsvista, Windows, and Fusion has varying results. The messages at the top sometimes have padding fixed. But the checkboxes never do. Just for reference, here's what it looks on macOS: https://forum.qt.io/topic/165221/pyside6-ui-looks-different-depending-on-which-macos-built-python