http://bugs.winehq.org/show_bug.cgi?id=31702
--- Comment #35 from voidcastr cephryx@gmx.net 2012-09-24 08:49:19 CDT --- (In reply to comment #33)
Created attachment 41812 [details] patch
Right, so the ClipCursor(NULL) when the mouse button is released disables clipping, and then it stays disabled because ClipCursor() is called so often. Does the attached patch make it any better?
Seems like we got it: Apparently the patch solves the actual issue for all common cases. Tough I only played a couple of minutes so far, but I don't suppose it will somehow stop working.
Nevertheless, the bug can still be triggered in an unusual scenario (I only came across this by chance): 1. start up the application 2. switch to another workspace, away from the application 3. switch back to the workspace the application runs in 4. trying to turn the camera within 1000 ms from the point in time (2.) was triggered causes the bug 5. it recovers for any subsequent attempts so the cam an once more be turned normally
This is not remotely critical, but it might hint to some other misc bug. The hardcoded "1000" is still around and either this threshold or the underlying issue might eventually become a problem for some practical scenario/application (though I cannot figure out one right now).