On Thu Nov 3 19:56:13 2022 +0000, Tim Clem wrote:
I'm afraid that this could possibly cause some stutter?
Yes, I agree that is a potential issue. I considered factoring most of `NtUserSetCursorPos` into a function that does everything but call the driver, and then call that from the sync function.
I'm also not completely sure to understand why this is an
initialization issue only. Absolutely a valid point. I assume the current caching mechanism was for performance reasons, for games that call `GetCursorPos` many times a second.
I believe I looked and it's been there for ages. Originally `GetCursorPos` was calling the graphics drivers all the time, and updated wineserver position too after that.
The input handling has been refactored and I believe it's been left there to avoid changing too much the behavior but I'm not completely convinced it's still useful.