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: <8902211642.AA26009@LYRE.MIT.EDU>
Date: 21 Feb 89 16:42:36 GMT
References: <2041@srava.sra.JUNET>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 20


     Date:  17 Feb 89 04:57:24 GMT
     From:  kddlab!icot32!nttlab!gama!etlcom!titcca!sragwa!srava!erik@uunet.uu.
    net  (Erik M. van der Poel)

     Using XtAppNextEvent() it is possible to fetch an X event, examine it,
     and decide what to do with it.
     ...
     Unless I am "missing something", there does not seem to be a way of
     doing the same thing with alternate input and timer events.

There is; since alternate inputs and timers are not "events", the
machinery is slightly different, but you can accomplish the same
effect.  XtAppPending() will tell you whether or not an alternate
input is ready or a timer is about to fire. XtAppProcessEvent()
will allow you to tell Xt which of the three queues to process
(inputs, events, and/or timers).  If you have multiple alternate
input sources, you'll have to determine your own mechanism to
assign priority between them, though; Xt will only treat them
as a group.