[Bug 42631] Mouse input cause camera drift in multiple games: Unity-engine games, Fallout4, etc

wine-bugs at winehq.org wine-bugs at winehq.org
Mon Jun 12 12:14:19 CDT 2017


https://bugs.winehq.org/show_bug.cgi?id=42631

--- Comment #24 from Eric Culp <eculperic at gmail.com> ---
After some more testing, the above patch appears to introduce the opposite bug
sometimes (drifting to the top left). However, just clicking the mouse no
longer causes any movement.

Someone more familiar to the code would have an easier time fixing this issue.
There are many layers of indirection and almost no comments, so it's difficult
for a newcomer to discover why the code exists, why it does what it does, and
where its data comes from (doubly so if you aren't very familiar with windows
apis like me).

In particular about this code, if the input MSLLHOOKSTRUCT has a point included
in it (hook->pt), why does it call GetCursor to get another point? Why aren't
they trivially equal? If it needs to return relative movements, can't it
subtract from m_state->lX and m_state->lY?

-- 
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