http://bugs.winehq.org/show_bug.cgi?id=31702
--- Comment #25 from voidcastr cephryx@gmx.net 2012-09-23 17:56:36 CDT --- (In reply to comment #23)
This is the problem here. I don't think that any mouse input should be throttled in a way which can negative affect the user. Reducing the time (even just to 10 milliseconds) would be more like a hackish way of solving this problem. I would prefer a clean solution which doesn't even theoretically cause this problem.
Absolutely. But in the case being at hand (GW2), it looks like completely removing the throttling solves the initial problem. Nevertheless, I suppose it's in there for a specific reason, and doing so might break other applications... though I really can't figure out what reason that might be. If and only if the throttling turns out to be obsolete or something, removing it would evidently be a clean solution; but that remains to be proven.
(In reply to comment #24)
(In reply to comment #22) What causes the WM_X11DRV_CLIP_CURSOR? Is it the application changing the cursor clipping rect with ClipCursor()?
I don't know yet -- gonna investigate this tomorrow.