http://bugs.winehq.org/show_bug.cgi?id=27604
Harm Geerts harmgeerts@home.nl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |harmgeerts@home.nl
--- Comment #1 from Harm Geerts harmgeerts@home.nl 2011-06-26 20:06:28 CDT --- I experienced the same using wine-1.3.21 and mumble-1.2.3
The mumble development version solved these problems for me (which has xinput2 support). https://github.com/mumble-voip/mumble/commit/ffbeaa25e0290fa0f974e4e1b469700... https://github.com/mumble-voip/mumble/commit/2cd986337d28f5faf86f6d77152adf2...
From the behavior I've seen it's as if mumble is eating the movement events
while the button is pressed and releases them when the button is released.
mumble development only listens to pressed/released events while 1.2.3 appears to listen to all which could explain this.