[PATCH 4/5] user32: Use rawinput device handles to identify devices.

[Marvin]

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

Your paranoid android.


=== w7u_2qxl (32 bit report) ===

user32:
input.c:756: Test failed:  0 (a4/0): 00 from 00 -> 80 unexpected
input.c:756: Test failed:  0 (a4/0): 41 from 01 -> 00 unexpected

=== w7u_el (32 bit report) ===

user32:
input.c:4292: Test failed: SendInput triggered unexpected message 0xc042

=== wvistau64 (64 bit report) ===

user32:
input.c:756: Test failed:  0 (a4/0): 01 from 01 -> 00 unexpected
input.c:756: Test failed:  0 (a4/0): 11 from 01 -> 00 unexpected
input.c:756: Test failed:  0 (a4/0): a2 from 01 -> 00 unexpected

=== w1064 (64 bit report) ===

user32:
input.c:3258: Test failed: expected WM_LBUTTONDOWN message
input.c:3259: Test failed: expected WM_LBUTTONUP message
input.c:3286: Test failed: expected WM_NCHITTEST message
input.c:3287: Test failed: expected WM_RBUTTONDOWN message
input.c:3288: Test failed: expected WM_RBUTTONUP message
input.c:3317: Test failed: expected WM_LBUTTONDOWN message
input.c:3318: Test failed: expected WM_LBUTTONUP message
input.c:3371: Test failed: expected loop with WM_NCHITTEST messages
input.c:3424: Test failed: expected WM_LBUTTONDOWN message
input.c:3425: Test failed: expected WM_LBUTTONUP message
input.c:1322: Test failed: GetCursorPos: (99,100)