https://bugs.winehq.org/show_bug.cgi?id=36873
--- Comment #10 from Ryan S. Northrup northrup@yellowapple.us --- Hi Alistair,
Thanks for the quick turnaround!
At a quick glance I don't think the patch as it exists in the wine-staging repo is going to work; one of our findings in the Proton GitHub thread on this issue (https://github.com/ValveSoftware/Proton/issues/3706) was that the two points returned have to be different from one another for the program to actually recognize it as a mouse movement. That's why I opted to store the coordinates from the previous call in those static variables (so that any mouse movement changes would register an actual change in mouse position).
If there's a policy against static variables in functions, then that's understandable, but if that's the case then we'd need to generate that second position some other way. We previously tried just incrementing the x and y coordinates by 1, which mostly worked except for camera rotation in the game's world map (it would only turn counterclockwise).