[Bug 48462] "Listen to RawKey* events in the desktop thread" patch makes keyboard unreliable in EverQuest

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48462

--- Comment #10 from Dominique Martinet <dvufhr.nznqarjf at noclue.notk.org> ---
Created attachment 66255
  --> https://bugs.winehq.org/attachment.cgi?id=66255
EQ log with WINEDEBUG=+event

> It may also depend on some window manager features, I don't know how widespread EWMH implementation is, and these patch depend on _NET_ACTIVE_WINDOW property updates.

Right, using wmii here might be something very different.

So to finish my recap, on top of full staging 5.0-rc5 I do not notice any
difference with your three last patches either:
 - EQ without virtual desktop behaves exactly the same
 - with virtual desktop and EQ, there is a difference between the commit I was
testing and staging, but no difference with your extra three patches.
Basically, directly losing focus used to stop input until I changed workspace
and came back (unmap/map), which then took input again even if not focused.
On staging, directly losing focus no longer stops input at all. I'll try to
translate all of these actions to winedebug messages, didn't know about these
it might be better than xev for you...
 - still cannot reproduce the "bad" input with virtual destkop and notepad, so
might be game-dependant for the other bz

Either way, the last three patches do not make a difference for my problem
here, be it on top of the "Listen to RawKey* events" commit or all staging
patches as of 5.0-rc5


> WINEDEBUG=+event and grep "X11DRV_PropertyNotify" could be used.

Tested EQ, no virtual desktop, on top of all staging patches + your 3 latest
patches.
I've attached a full log (with WINEDEBUG=+event), no grep, added timestamps,
and the following schedule ± a couple of seconds:
10s: EQ mostly ready, anything before that can be ignored (window starting, a
few keypresses to get into an input field)
15s: 3 key presses: these work as expected, game is focused.
20s: focus out
25s: 3 key presses: these don't appear in window.
30s: change workspace out
35s: 3 key presses: still don't appear
40s: change workspace in
45s: 3 key presses: these are taken by game but x11 window isn't focused
50s: change workspace out again
55s: 3 key presses: these do appear (can notice when going back in)
60s: change workspace back in and ^C after confirming there are 9 characters in
field as "expected" with bug

so if anything the problem is around the 40s mark, the X11DRV_Expose perhaps?

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.