General and Desktop

@SGaist 6.9.1 + vs2022

QtWebEngine in Qt6 does not render changes to CSS radio-buttons and checkboxes when the change happens with a mouse click. The change from True->False or False->True happens in radio-buttons, but it is not drawn/rendered on the QtWebEngineView. Similarly, checked->unchecked and unchecked->checked happens with mouse clicks on checkboxes, but the change is not shown on the QtWebEngineView. I thought it might be possible to capture the state change and redraw the QtWebEngineView so that the change shows. But there is no way to capture state changes in CSS radio-buttons and checkboxes. In Qt5/QtWebKit the state changes are shown right out of the box without any problems. It is a bug in Qt6/QtWebEngine.

@Jammin44fm said in Problem running application on Linux. Ubuntu 22.04 LTS + Wayland platform.: Does this mean I will need to distribute a different version of the libQt6WaylandClient for each version of Qt that i'm using? To make it simple - yes. The ABI promises Qt makes are for applications making use of published APIs. They do not extend to different modules of the framework itself - you should never mix say QtGui 6.8.1 with QtCore 6.8.0; same for QPA plugins (as they make use of private API). Basically, when bundling Qt for distribution - you must copy ALL modules and plugins that the application uses, and not allow any to be used from the containing system. QtWaylandClient included in that - though it needs to be usually manually included as tools scanning dynamic library dependencies often can't see it. What is the status of the linuxdeploy-plugin-qt? it doesn't look like it's part of the official Qt package? It is not official. It works, I use it. As for status, I believe it is actively maintained, although as with pretty much all AppImage tooling it is done by one guy in a basement. Deploying Wayland plugins with linuxdeploy-qt has to be done with care. It works for me by including waylandcompositor in the EXTRA_QT_MODULES environment variable.

@Navadvipa-Chandra-das said in Not compilated Qt from sources: failed because the system could not detect libzstd.dll ... Although the instructions for installing Qt do not mention the zlib library as required for installation! That's strange; I never needed libzstd or zlib to build Qt on Windows. Zstandard and zlib are optional components. If you don't have them, your config.summary file should contain something like this: Support enabled for: Using pkg-config ....................... no Using vcpkg ............................ no udev ................................... no OpenSSL ................................ yes Qt directly linked to OpenSSL ........ no OpenSSL 1.1 ............................ no OpenSSL 3.0 ............................ yes Using system zlib ...................... no Zstandard support ...................... no Thread support ......................... yes

Typo: python3-pyside6 in the last message instead of pyside5, I'm not sure if it's actually broken, even with a simple app (import and print the plugin search paths) I see error on Python initialization.

@schrute What I found to be effective, is to leave it as a bordered window, and just intercept the WM_NCCALCSIZE message, so that it does nothing. This basically gives you a bordered window, where you stop windows from drawing the borders. This way, when you implement your own title bar, aero snap will still work.

@Kent-Dorfman I don't think so, because in the same implementation I use the <=> operator with a member variable that is of type int. Additionally, there is no problem with the usage of std::strong_ordering and the project uses other C++20 features. The compiler complaints only about those Qt types using <=>.

I will not look at qml but maybe it's a good starting point for others who want to debug this.

I found these Natvis visualizers to be working fine with Visual Studio Code, if that helps you: https://github.com/narnaud/natvis4qt/tree/main/natvis QJson value visualizers are only included in the qt6.natvis file.

Hi, Some things to check: which version of VTK did you install ? Meaning, is it the one for Visual Studio ? did you try with their latest version which is the 9.5 series ? as silly as it may sound, are you sure that this version has Qt support enabled ?

I fixed this issue. It was a Qt 6.9.0 bug, but Qt 6.9.1 has the fix

@jawadulhassan Hi Thank you for the hint, the setModal(true) and setWindowModality(Qt::ApplicationModal) has no effect. the activateWindow() where do you mean I should locate it? If I see it right, the opening of the editor is done in the QAbstractItemView. Do you have a sample which fixes this issue?

Did you already check the bug report system to see if other people reported similar issues ?

The solution is qt6-help-devel

Thank you, I'll have a look at its code to mimic its behavior.

Hi SGaist, Thank you :) I am using Qt 5.15.2 I have attached a small example that contains three classes: A mainwindow, a testwidget and a box. The testwidget and box are both subclasses of QLabel. The mainwindow contains the testwidget, the testwidget captures mouse events which move the box to follow the mouse. Even when the mouse is not moving, the box flickers continually. Oh, I tried to upload the file, but received the message that "I do not have enough privileges for this action" It can be downloaded here: https://www.dropbox.com/scl/fi/o493be8f997ti29p037rc/QtCursorExample.zip?rlkey=ck18a9zqzb2r9q3vb7ig2zqoj&st=gjlg1mpx&dl=0 Thanks, fallen

Hi and welcome to devnet, Shouldn't you set the radius on the drop-down as well ? See the QComboBox example in the stylesheet documentation.

@SamiV123 said in Why is my QT application not working ?: "Qt 4.8.4 was released in 2012. The compiler was apparently 2008. That order of time ago is significant." Ok, did it break? Got rusty and turned into dust? :) You’re turning this into a Reddit-level back-and-forth :) Qt4 is a decade past its time — unless you’re stuck with legacy requirements, you should be using Qt5 or Qt6.

I was able to follow these instructions to package my app for initially Qt5 and now Qt6. See this blog post for details: https://nils.schimmelmann.us/2025-08-15-deploying-a-qt-app-to-the-microsoft-store-with-cpack-and-makeappx/