[Bug 48322] World of Warcraft Classic: Mouse movement can block keydown events from registering

[WineHQ Bugzilla]

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

--- Comment #12 from Luca Boccassi <luca.boccassi at gmail.com> ---
(In reply to Sveinar Søpler from comment #11)
> (In reply to Luca Boccassi from comment #10)
> > (In reply to Sveinar Søpler from comment #9)
> > > (In reply to Luca Boccassi from comment #8)
> > > > 
> > > > Yes, that fixes it, just tried in 5.0~rc5, thanks for the tip. But this was
> > > > not necessary until 4.19, so it still sounds like a regression to me.
> > > 
> > > Well, yeah, i think it is somewhat of a regression with the "RawInput"
> > > patchset in staging.
> > > 
> > > I cannot verify this with WoW without staging tho, but if i have the time i
> > > could perhaps ditch that particular patchset and see what happens.
> > 
> > Did you manage to find time to try this?
> > 
> > Thanks!
> 
> No, sorry. It is multiple patchsets in staging dealing with rawinput and i
> quite frankly cba to troubleshoot this.
> 
> This is with "staging", and it is considered experimental to begin with, and
> even if i could find what exact patch causes this i kinda doubt anything
> would be done with it unless i provide a fix for it myself... and that i
> have no idea of doing.
> 
> If someone know exactly what minimal patchsets is needed to run WoW (without
> me having to sift through a few hundred patches and doing a recompile each
> time) it would be nice for comparison tho :)
> 
> PS. I have no huge issues ticking the "grab mouse" option tho, as i think
> that works fine most of the time, other than slightly annoying to alt-tab
> vs. just moving mouse to my 2nd monitor when browsing and stuff like that.

Is there a process to track regression introduced by patches in staging? Could
this bug at least be marked as "confirmed" given there are multiple independent
reports?

I have a multi-monitor setup so it is a bit annoying - but not annoying enough
to start setting up the build&run environment and bisect, not yet at least :-)

-- 
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.