[PATCH 2/2] user32: Prevent a recursive loop with the activation messages.

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

Your paranoid android.


=== w8 (32 bit report) ===

user32:
msg.c:15351: Test failed: unexpected message 31f
msg.c:15352: Test failed: bad wparam 1
msg.c:15358: Test failed: unicode WM_CHAR: 0: the msg sequence is not complete: expected 0102 - actual 0000

=== debian11 (32 bit French report) ===

user32:
msg.c:17136: Test failed: 0: WaitForSingleObject failed
msg.c:17136: Test failed: 1: WaitForSingleObject failed
msg.c:17136: Test failed: 2: WaitForSingleObject failed
msg.c:17136: Test failed: 3: WaitForSingleObject failed
msg.c:17136: Test failed: 4: WaitForSingleObject failed
msg.c:17136: Test failed: 5: WaitForSingleObject failed
msg.c:17136: Test failed: 6: WaitForSingleObject failed
msg.c:17136: Test failed: 7: WaitForSingleObject failed
msg: Timeout

=== debian11 (32 bit Japanese:Japan report) ===

user32:
msg.c:17136: Test failed: 0: WaitForSingleObject failed
msg.c:17136: Test failed: 1: WaitForSingleObject failed
msg.c:17136: Test failed: 2: WaitForSingleObject failed
msg.c:17136: Test failed: 3: WaitForSingleObject failed
msg.c:17136: Test failed: 4: WaitForSingleObject failed
msg.c:17136: Test failed: 5: WaitForSingleObject failed
msg.c:17136: Test failed: 6: WaitForSingleObject failed
msg.c:17136: Test failed: 7: WaitForSingleObject failed
msg: Timeout