[PATCH v2 1/3] server: Create message queue and thread input in set_key_state.

[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=113488

Your paranoid android.


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

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

=== w10pro64_ja (64 bit report) ===

user32:
input.c:3438: Test failed: expected WM_NCHITTEST message
input.c:3439: Test failed: expected WM_RBUTTONDOWN message
input.c:3440: Test failed: expected WM_RBUTTONUP message
input.c:3468: Test failed: expected WM_NCHITTEST message
input.c:3469: Test failed: expected WM_LBUTTONDOWN message
input.c:3470: Test failed: expected WM_LBUTTONUP message
input.c:3496: Test failed: expected WM_NCHITTEST message
input.c:3523: Test failed: expected loop with WM_NCHITTEST messages
input.c:3576: Test failed: expected WM_LBUTTONDOWN message
input.c:3577: Test failed: expected WM_LBUTTONUP message