Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!WESTHAWK.UUCP!thp
From: thp@WESTHAWK.UUCP
Newsgroups: comp.windows.x
Subject: Re: How to handle non-X events
Message-ID: <8906151021.AA02230@westhawk.uucp>
Date: 15 Jun 89 10:21:49 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 19


You don't say how the independant process communicates. If it
talks via a file (or pipe or socket) the you can just say:

XtAddInput(fdesc, XtInputReadMask, stalk_readln, &fdesc);

where fdesc is the file you are interested in and stalk_readln() is a
function you want invoked when data arrives on fdesc . This has worked
very well for me.

If however you communicate via signals, shared memory, semaphores etc
then it's harder, X betraying it's BSD roots ?

Tim.
+----------------------------------------------------------------------------+
|Tim Panton, Westhawk Ltd.       (Contract X application programmer)         |
|Paper: Westhawk Ltd. 26 Rydal Grove, Helsby, Cheshire, WA6 OET. UK.         |
|Phone: +44 92822574             uucp : ..!mcvax!ukc!cam-cl!westhawk!thp     |
+----------------------------------------------------------------------------+