Path: utzoo!attcan!uunet!ginosko!bbn!usc!bloom-beacon!H.GP.CS.CMU.EDU!eddie.caplan
From: eddie.caplan@H.GP.CS.CMU.EDU
Newsgroups: comp.windows.x
Subject: Re: event-driven X11
Message-ID: <14071.614881708@H.GP.CS.CMU.EDU>
Date: 26 Jun 89 16:28:28 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 14


In article <2701@bucsb.UUCP> boreas@bucsb.bu.edu (Michael A. Justice) writes:
    >Assuming you're running UNIX, why not fork your process, and let one of
    >the two processes do the XNextEvent-loop while the other does your other
    >stuff?  You could then have the XNextEvent-loop's process generate
    >interrupts to tell the "main" process about any events it needs to hear
    >about.  Shared memory or pipes or some such scheme for the processes to
    >keep each other informed. . . .

this is precisely what i do now.  but, i would have preferred to have had this
functionality inside the X protocol.

by the way, Jim Fulton's suggestion of setting a SIGIO on ConnectionNumber(dpy)
is not a bad idea.  i might switch to it.