On Fri May 19 16:44:23 2023 +0000, Alexandre Julliard wrote:
I would expect that you wouldn't need fancy event filtering. The mouse/keyboard events can go straight to the hardware queue, and the others can be either sent or posted depending on the desired event mask.
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?