On Fri May 19 18:13:58 2023 +0000, Alexandre Julliard wrote:
If you are creating a thread to process Wayland events, it shouldn't be necessary to do anything in the other threads, they would simply wake up when getting window messages. Though the preferred solution would be to have normal threads pull out Wayland events in ProcessEvents(), and not use an extra thread at all.
I have updated the branch as suggested to use internal window messages to handle events in particular threads. I am still using a single, separate thread to dispatch events from the (single, per-process) Wayland compositor event queue, since that is libwayland's supported threading/dispatch model.
Please note that I haven't rebased on latest master to keep the MR version diffs sane.
(The winhttp test-linux-32 failure is unrelated to this MR, see https://gitlab.winehq.org/wine/wine/-/merge_requests/2871)