Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!asente
From: asente@decwrl.dec.com (Paul Asente)
Newsgroups: comp.windows.x
Subject: Re: querying event sources in Xt
Message-ID: <1122@bacchus.dec.com>
Date: 21 Feb 89 18:33:22 GMT
References: <2041@srava.sra.JUNET>
Organization: DEC Western Software Lab
Lines: 19

In article <2041@srava.sra.JUNET> erik%sra.junet@uunet.uu.net (Erik M. van der Poel) writes:
>Using XtAppNextEvent() it is possible to fetch an X event, examine it,
>and decide what to do with it. Ordinarily one would pass it to
>XtDispatchEvent() but one does not have to; the event can also be
>ignored, for example.
>
>Unless I am "missing something", there does not seem to be a way of
>doing the same thing with alternate input and timer events. It would be
>nice if one could check the source (file descriptor) or XtIntervalId
>before deciding to dispatch the event.

You're certainly free to do whatever processing you want in your input and
timer callback procedures, including doing nothing or queuing up a task
for later processing.

I'm not sure I understand what it is you're trying to accomplish here.

	-paul asente
	    asente@decwrl.dec.com	decwrl!asente