[Bug 33436] Tomb Raider (2013): Game does sometimes not respond to mouse move

wine-bugs at winehq.org wine-bugs at winehq.org
Sun Apr 21 14:10:47 CDT 2013


http://bugs.winehq.org/show_bug.cgi?id=33436

--- Comment #1 from Felix Hädicke <felixhaedicke at 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.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.


More information about the wine-bugs mailing list