Path: utzoo!attcan!uunet!lll-winken!arisia!sgi!daisy!klee
From: klee@daisy.UUCP (Ken Lee)
Newsgroups: comp.windows.x
Subject: XNextEvent vs. select(2)
Message-ID: <2199@daisy.UUCP>
Date: 20 Dec 88 01:26:00 GMT
Reply-To: klee@daisy.UUCP (Ken Lee)
Organization: Daisy Systems Corp., Mountain View, Ca.
Lines: 15
References:

We are building an application that contains 2 (or more) UNIX processes.
Each process is an X client.  We would like to communicate between the
processes with UNIX sockets and wait on these events with select(2).  At
the same time, we would like to wait on X events with XNextEvent().
Unfortunately, the UNIX input stream seems to be incompatible with the X
input stream.  Is there any (preferably portable) way to register the X
event stream with select()?  Alternatively, is there any way to be
notified of UNIX events through XNextEvent()?  Thanks much for your help!

Ken Lee
Daisy Systems Corp., Interactive Graphics Tools Dept.
-- 
uucp:  uunet!daisy!klee		arpanet:  daisy!klee@uunet.uu.net

"DC6 which is being used for [Contra weapons supply] runs out of New Orleans
is probably being used for drug runs into U.S." - Oliver North, August, 1985