Re: [PATCH 3/6] user32: Return WAIT_TIMEOUT in nulldrv_MsgWaitForMultipleObjectsEx.

[Zebediah Figura (she/her)]

On 5/14/21 6:40 AM, Rémi Bernon wrote:
> When there's nothing to wait for.
> Signed-off-by: Rémi Bernon
>
> dlls/user32/driver.c | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/dlls/user32/driver.c b/dlls/user32/driver.c
> index 35e206f5e98..cb9dda6a692 100644
> --- a/dlls/user32/driver.c
> +++ b/dlls/user32/driver.c
> @@ -305,6 +305,7 @@ static void CDECL nulldrv_GetDC( HDC hdc, HWND hwnd, HWND top_win, const RECT *w
>   static DWORD CDECL nulldrv_MsgWaitForMultipleObjectsEx( DWORD count, const HANDLE *handles, DWORD timeout,
>                                                           DWORD mask, DWORD flags )
>   {
> - if (!count && !timeout) return WAIT_TIMEOUT;
>  return WaitForMultipleObjectsEx( count, handles, flags & MWMO_WAITALL,
>                                   timeout, flags & MWMO_ALERTABLE );
> }

Why is this necessary? In fact, won't this give wrong results if there 
is a queued message available?