General and Desktop

These are two different styles - a dark one and a light one. So first you should make sure to use the same style.

Did you already check the bug report system ?

You should take a look at the vnc platform plugin implementation. I remember seeing there something related to adjustment.

@Plan-C You should consider posting this here: https://forum.qt.io/category/8/showcase

and add 100$ for each sold device

Doing this in QWidgets looks like a pain in the ass. It would be pretty easy to do in Qt Quick.

Yep the error above was what I saw on the web console. I can get the page to load as HTTPS, and the server side of the websocket (sslechoserver) is not reporting any errors. Hence why I am rather lost. Does not help this is not an area I have much experience in.

The problem is using the EOL Qt 5.15.18. PMF based connections used to silently fail under certain conditions (I know ambiguity was one reason). They have been significantly improved in Qt 6. In Qt 6.11 I get this output right away: B QVariant(int, 1) A QVariant(int, 1) B QVariant(Invalid) A QVariant(Invalid) B QVariant(int, 2) A QVariant(int, 2) virtual C::~C() virtual B::~B() virtual A::~A() If you wanna check which connection fails, you can output the return value of the connect statement e.g. like that: B(const A &a) : a{a} { const auto connection = connect(&a, &A::valueChanged, this, &B::valueChanged); qInfo() << connection; } (The return value is of the type QMetaObject::Connection, but it's debug operator just treats it like a bool.)

@dencla One simple thing from the Designer side: look at the Object Explorer at the right hand side, showing all your widgets in a hierarchical structure. If any widget nodes have a "red no entry" symbol on them that indicates you are missing a layout. To assign layouts in the UI you either right-click on a widget (once it has children) and set its Layout from there or there are actual layout items in the toolbox on the left to drag explicitly. I have never looked into whether they end up doing the same thing!

Right. file(GLOB IMAGES_FILES RELATIVE ${CMAKE_SOURCE_DIR} "src/resources/images/*.svg")

@SGaist Yes, I did see the C++ example however I don't want to go the GL rendering route, as my shell will only have one Wayland surface visible at a time, hence the reason I chose this route. Something interesting worth noting is that if I try to pass a Wayland surface through C++ to ShellSurfaceItem in QML, it draws some sort of border but nothing actually renders inside it. Doing the same entirely in QML works without issues.

Hi @Krish89 and welcome to the Qt Forum, the crash happens in Qt5, which is EOL and no longer maintained. Can you try Qt6 (e.g. 6.8) instead? I am asking because the XCB implementation was improved in Qt6, so there is a chance that this has already been fixed. Cheers Axel

You can use doxygen/doxywizard to generate graphviz dot files: [image: fc587a50-40f0-4c0c-8820-29630b401a3f.png]

@Christian-Ehrlicher said in Why does QTimer::setInterval(0) not work as expected in Qt 6?: @jeremy_k said in Why does QTimer::setInterval(0) not work as expected in Qt 6?: I thought you were going to ask for something hard, like a reference within the implementation. Please look at my link to the source code. I overlooked that. Thanks. QTimer::singleShotImpl() uses a queued connection for the ns == 0 case. https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/kernel/qtimer.cpp#n389 QMetaObject::invokeMethodImpl(const_cast<QObject *>(receiver), slotObj, Qt::QueuedConnection, h.parameterCount(), h.parameters.data(), h.typeNames.data(), h.metaTypes.data());

To add a bit more to @Christian-Ehrlicher 's answer, the operator <() of QVariant had already been obsoleted since Qt5.15 and got removed from Qt6. You can see this from the archived Qt5.15 documentation: https://doc.qt.io/archives/qt-5.15/qvariant-obsolete.html#operator-lt This operator is deprecated as it cannot establish a total order required for most use of this operator, which is the reason you cannot use QVariant as the key of a QMap.

I think, I figured it out. Using this qputenv("QT_LOGGING_RULES", "qt.multimedia.ffmpeg*=false"); in main does not log anything from ffmpeg

I found that in QT version 6.8.3, when using the styleMask of NSWindow, only MainWindow itself would extend to the title bar, while CentralWidget and ToolBar would not extend to the title bar.

Hi and welcome to devnet, Do you see this on all platforms ?