ce7a98e95c
After processing several X events, X11DRV_MsgWaitForMultipleObjects always tells us that a new message is available. This is not true for some cases. For instance, when we call DestroyWindow, the X queues DestroyEvent. Then, X11DRV_MsgWaitForMultipleObjects handles the event only; none is posted or sent as hwnd for destroyed window is unavailable. However, the function states "new message is available" by returning count - 1 value. This is an issue for CoWaitForMultipleHandles because it expects a new message in the queue and consumes the message. Signed-off-by: Akihiro Sagawa <sagawa.aki@gmail.com> Signed-off-by: Alexandre Julliard <julliard@winehq.org> |
||
|---|---|---|
| .. | ||
| Makefile.in | ||
| bitblt.c | ||
| brush.c | ||
| clipboard.c | ||
| desktop.c | ||
| event.c | ||
| graphics.c | ||
| ime.c | ||
| init.c | ||
| keyboard.c | ||
| mouse.c | ||
| mwm.h | ||
| opengl.c | ||
| palette.c | ||
| pen.c | ||
| settings.c | ||
| systray.c | ||
| version.rc | ||
| window.c | ||
| winex11.drv.spec | ||
| wintab.c | ||
| x11drv.h | ||
| x11drv_main.c | ||
| xcomposite.h | ||
| xdnd.c | ||
| xim.c | ||
| xinerama.c | ||
| xrandr.c | ||
| xrender.c | ||
| xvidmode.c | ||