[PATCH v2 4/5] user32/tests: Fix existing winevents in test_mdi_messages() message sequences.

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

Your paranoid android.


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

user32:
msg.c:12811: Test failed: msg.message = 30 instead of WM_TIMER
msg.c:12814: Test failed: msg.message = 275 instead of WM_USER + 1
msg.c:12816: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:12826: Test failed: msg.message = 1025 instead of WM_TIMER
msg.c:12828: Test failed: msg.message = 275 instead of WM_USER
msg.c:12830: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:12839: Test failed: msg.message = 1024 instead of WM_TIMER
msg.c:12841: Test failed: expected PeekMessage to return FALSE, got 1

=== w7u_adm (32 bit report) ===

user32:
msg.c:14294: Test failed: CreateDialogParam_3: 14: the msg 0x001c was expected, but got msg 0x0083 instead

=== w10pro64_zh_CN (64 bit report) ===

user32:
msg.c:12701: Test failed: message time not advanced: eee4 eee4
msg.c:12702: Test failed: coords not changed: (101 101) (101 101)
msg.c:12719: Test failed: message time not advanced: eee4 eee4
msg.c:12720: Test failed: coords not changed: (101 101) (101 101)