https://bugs.winehq.org/show_bug.cgi?id=48462
--- Comment #5 from Dominique Martinet dvufhr.nznqarjf@noclue.notk.org ---
However this is not always reflected on the X11 side, where another window may have the input focus.
And it's not possible to have a better synchro between the windows state and the x11 state ? FWIW, in wayland, you cannot get events for the root window anymore (only the really focused wayland window gets events) -- that looks much saner to me.
virtual desktop as a workaround
That is a good point, I might get better input with that for my other problems too, I'll give it a spin. But I don't think it's enough to just fix virtual desktop, you will probably have many other games behaving the same way I think?
no events processed for a long time
Now while that might be very true for games like EQ (during heavy lag period I can easily have something like 10s delay between what I finished typing and the moment it's done processing), I don't think it was the case when I had problems with what I typed in firefox being sent to the game as well. In the occurrences I had the game was idle in a relatively lag-free safe area so there shouldn't have been even a second of lag there, and text I was typing minutes after switching workspace was still sent.
There might be a problem with how wmii notifies x11 clients of workspace switch (just tested with xev: I see proper FocusIn/FocusOut events if focused and UnmapNotify/MapNotify events even if not focused so it looks proper to me)... But anyway, I still don't find natural that games have to process root window key events. Call me paranoid but I don't particularily trust windows programs I haven't seen the source of, so the less it can see of what I don't type with it explicitely focused the better (think keyloggers or similar)
Thanks,