http://bugs.winehq.org/show_bug.cgi?id=33436
--- Comment #1 from Felix Hädicke felixhaedicke@web.de 2013-04-21 14:10:47 CDT --- Created attachment 44244 --> http://bugs.winehq.org/attachment.cgi?id=44244 First workaround patch (using mouse event correction values)
I did some research and found this first (admittedly inelegant) workaround.
The problem seems to be that the desktop->cursor.x / desktop->cursor.y values get changed in a way that relative raw input mouse events can not be properly calculated. This is caused by frequent SetCursorPos() calls. This patch introduces correction values used for the raw input events.
But this workaround does not always give back full movement freedom. Sometimes (probably because absolute instead of relative mouse move events are used almost all the time) there is a movement restriction on the left, right, top and bottom.