Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!hp-pcd!hpfcso!hpfcmgw!chan
From: chan@hpfcmgw.HP.COM (Chan Benson)
Newsgroups: comp.sys.hp
Subject: Re: Interrupt driven X event loop?
Message-ID: <17780015@hpfcmgw.HP.COM>
Date: 18 Mar 91 21:01:27 GMT
References: <395@esl.ESL.COM>
Organization: HP Fort Collins, CO
Lines: 16

>      Where are x events queued when using Xm and Xt?  Some events 
>      come off the socket, others never make it to the socket but
>      are queued.  Where?

Xlib has an internal event buffer. All events come through the socket,
but a whole chunk of them may get read at once (even though you've
only asked for one). You need to modify your code so that you don't
block until XPending() returns 0, which means that everything has
been read off the internal queue and there's nothing waiting to be
read from the socket.

Hope that helps. If you need more details, let me know.

			-- Chan Benson
			HP Fort Collins