Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph R Swick)
Newsgroups: comp.windows.x
Subject: Re: querying event sources in Xt
Message-ID: <8902221847.AA27029@LYRE.MIT.EDU>
Date: 22 Feb 89 18:47:53 GMT
References: <2043@srava.sra.JUNET>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 15

>  So, I want the
> application to stop processing while that window is up. But alternate
> input is processed by XtAppNextEvent(), which in the case of my program
> led to an avalanche of message windows.

So why can't you use XtAppProcessEvent(ctx, XtIMXEvent) to block,
ignoring everything, until the next XEvent comes along?
Or, if you're _really_ trying to get your hands on that event
before Xt dispatches it then just call XNextEvent directly.

> Enough griping. Apart from this, Xt is OK, thanks to all involved.

no problem; I'm just trying to figure out whether we really did
leave out something that you need or whether we just didn't document
something else well enough.