Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
5.14.2
-
None
-
Linux/X11
Description
The initial problem is reported here: https://bugreports.qt.io/browse/AUTOSUITE-709
Basically this report is to clarify, whether QCoreApplication::processEvents should flush Wayland messages. This would be achieved with:
diff --git a/src/compositor/compositor_api/qwaylandcompositor.cpp b/src/compositor/compositor_api/qwaylandcompositor.cpp index e021b742..63002616 100644 --- a/src/compositor/compositor_api/qwaylandcompositor.cpp +++ b/src/compositor/compositor_api/qwaylandcompositor.cpp @@ -218,6 +218,7 @@ void QWaylandCompositorPrivate::init() QAbstractEventDispatcher *dispatcher = QGuiApplicationPrivate::eventDispatcher; QObject::connect(dispatcher, SIGNAL(aboutToBlock()), q, SLOT(processWaylandEvents())); + QObject::connect(dispatcher, SIGNAL(awake()), q, SLOT(processWaylandEvents())); initializeHardwareIntegration(); initializeSeats();
An admittedly contrived example is attached. The question is whether the client should terminate immediately when the compositor sends the window close event. The (glibc) implementation of the event dispatcher processEvents() method only emits awake and not aboutToBlock.
Attachments
Issue Links
- resulted from
-
AUTOSUITE-709 Analyse test case issues
-
- Closed
-