Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!hewey.UUCP!ian
From: ian@hewey.UUCP (Ian Hogg)
Newsgroups: comp.windows.x
Subject: Re: again : avoiding event loops
Message-ID: <9006040500.AA06963@shamash.cdc.com>
Date: 4 Jun 90 04:21:39 GMT
References: <2998.26663bc7@esat.kuleuven.ac.be>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 20

> 
> > My approach is to get the file descriptor for the X server (with
> > ConnectionNumber(display)) and catch SIGIO.
> 
> This works fine but there is still one problem : If I catch an interrupt
> when I'm in a X-call, my programm crashes. I worked around this by
> postponing the interrupt handling while I'm doing X-calls. This is however
> elaborate, and I'm wondering if there is not an other way to prevent the
> Xserver from receiving two concurrent X-calls
> Please send any reply by Email
> 

I haven't tried this but what if you opened the display twice.  Use one display
for your normal processing and the other to update the display in your signal
handler.  Anyone know if this is OK?

-- 
===============================================================================
Ian Hogg                                    email:  ian@dms.cdc.com
Control Data Corporation                    phone:  (612)-553-4484