Jon TURNEY f57100bb36 hw/xwin: Process one Windows message per wakeup, rather than all of them. ... De-queuing Windows messages and X events happens in the same thread of execution. Draining the windows message queue can lead to the X event queue overflowing if lots of those windows messages cause X events (e.g. if a keyboard macro program has just dumped thousands of keypresses into the Windows message queue). See the mailing list thread [1] for more details. Processing one Windows message per wakeup, rather than all of them gives the X server a chance to do stuff as well after each message. [1] http://cygwin.com/ml/cygwin-xfree/2010-01/msg00056.html Signed-off-by: Jon TURNEY <jon.turney@dronecode.org.uk> Reviewed-by: Colin Harrison <colin.harrison@virgin.net>		2013-01-10 15:33:12 +00:00
..
dmx	Merge remote-tracking branch 'yselkowitz/master'	2012-12-19 12:22:03 -08:00
kdrive	Fix formatting of address operators	2012-12-05 18:09:48 -06:00
vfb	vfb: Initialize the GLX extension again.	2012-11-21 11:13:55 +11:00
xfree86	hw/xfree86: Require only one working CRTC to start the server.	2013-01-08 20:24:32 -08:00
xnest	dix: Remove #includes of mibstore.h	2012-09-23 10:31:27 -07:00
xquartz	XQuartz: Don't add the 15bit visual any more	2012-12-18 01:37:27 -08:00
xwin	hw/xwin: Process one Windows message per wakeup, rather than all of them.	2013-01-10 15:33:12 +00:00
Makefile.am	Catch errors in recursive relink targets	2010-03-22 00:45:57 -05:00