Re: [Development] Module maintainers: QT_NO_CONTEXTLESS_CONNECT in your modules

Hi, > Second, it's also easy to forget that since there's no receiver/context, > the connection is always forced to be *direct*, which complicates things > if multiple threads are involved. I'm not a module maintainer, but I remember fixing a bug in Qt Bluetooth which was caused by exactly this

[Development] Module maintainers: QT_NO_CONTEXTLESS_CONNECT in your modules

Hi, https://codereview.qt-project.org/c/qt/qtbase/+/487560 introduces QT_NO_CONTEXTLESS_CONNECT , a macro that disables the 3-arguments connect -- in other words, it disables the QObject::connect(sender, signal, functor) overload, leaving only 4/5 argument(s) overloads

Re: [Development] QtWayland compositor can't to render a wl_surface to multi outputs, Is this a restrict of QtQuick graphics scene?

Thank you. Currently, my approach is to use a for loop to call QQuickWindow::setRenderTarget to change the rendering target while change the projectionMatrix of QSGRenderer. "because different screens have different surface formats requirements" Is point say a QSurfaceFormat?

Re: [Development] QtWayland compositor can't to render a wl_surface to multi outputs, Is this a restrict of QtQuick graphics scene?

Hi, Each window has an isolated scene graph and RHI instance, which is the reason for this limitation if I understand correctly. Decoupling them is actually quite complicated, because different screens have different surface formats requirements and it might not be possible to render to both