On Fri May 19 18:08:09 2023 +0000, Alexandros Frantzis wrote:
Thanks, sounds good, I will explore this further. So to ensure I understand the new proposed approach properly: `ProcessEvents` would not perform any actual event dispatching and thus filtering (so the mask would be effectively unused), we would only ensure it wakes up the thread if there have been new Wayland events (and thus messages). All the handling and filtering would be done implicit by the core message handling, based on the details of how we send/post key/mouse/internal messages from the Wayland event handlers. Does this sound about right?
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.