Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!decuac!bacchus.pa.dec.com!decwrl!klee
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: Awaiting _non_ X events, was Re : XtAddTimeOut() ....
Message-ID: <1990Aug30.175902.1445@wrl.dec.com>
Date: 30 Aug 90 17:59:02 GMT
References: <9008231943.AA01202@crc.skl.dnd.ca> <141292@sun.Eng.Sun.COM> <4039@husc6.harvard.edu>
Sender: news@wrl.dec.com (News)
Reply-To: klee@wsl.dec.com
Organization: DEC Western Software Laboratory
Lines: 17


In article <4039@husc6.harvard.edu>, moghe@husc4.HARVARD.EDU (moghe m) writes:
|> In the bad-old-days-before-X one would use this select()
|> in the main loop to wait on Keys, Mouse, Timeout or
|> whatever other events on any file descriptors were of
|> interest. But now, if you have an X application which
|> also needs to handle events other than X events, how
|> does one do it? Lets say you want the X application to
|> await on a message on a socket in addition to handling
|> events from the X-server.

Use XtAppAddInput to wait on UNIX-style file descriptors.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@wsl.dec.com
uucp: uunet!decwrl!klee