[PATCH] user32: Implement GetMouseMovePointsEx().

[Arkadiusz Hiler]

On Mon, Sep 14, 2020 at 09:19:17AM -0500, Marvin wrote:
> Hi,
> 
> While running your changed tests, I think I found new failures.
> Being a bot and all I'm not very good at pattern recognition, so I might be
> wrong, but could you please double-check?
> 
> Full results can be found at:
> https://testbot.winehq.org/JobDetails.pl?Key=78681
> 
> Your paranoid android.
> 
> 
> === w10pro64_zh_CN (32 bit report) ===
> 
> user32:
> input.c:2188: Test failed: Spurious WM_INPUT messages
> 
> === w10pro64_he (64 bit report) ===
> 
> user32:
> input.c:1368: Test failed: Wrong new pos: (103,103)
> input.c:1292: Test failed: GetCursorPos: (100,98)
> 
> === w10pro64_ja (64 bit report) ===
> 
> user32:
> input.c:1302: Test failed: Wrong set pos: (99,100)
> input.c:1322: Test failed: GetCursorPos: (99,100)
> 
> === debiant (32 bit report) ===
> 
> user32:
> monitor: Timeout
> 
> === debiant (32 bit Chinese:China report) ===
> 
> user32:
> monitor: Timeout
> 
> === debiant (32 bit WoW report) ===
> 
> user32:
> monitor: Timeout
> 
> === debiant (64 bit WoW report) ===
> 
> user32:
> monitor: Timeout

Doesn't look like it's caused by anything in this patch. User32 input
tests seem to be rather volatile. I've seen some faliures happening here
and there randomly both on Windows and under Wine, even without any of
my changes. But I hven't seen anything like this.

I've also been running that patch through testbot (+/- some cosmetic
changes), and no complaints there:

https://testbot.winehq.org/JobDetails.pl?Key=78677
https://testbot.winehq.org/JobDetails.pl?Key=78689

-- 
Cheers,
Arek