Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!mcsun!sunic!tut!santra!hemuli.tik.vtt.fi!tml
From: tml@hemuli.tik.vtt.fi (Tor Lillqvist)
Newsgroups: comp.windows.x
Subject: Re: X & signals
Keywords: xwindows signals
Message-ID: <4561@hemuli.tik.vtt.fi>
Date: 27 Feb 90 06:48:38 GMT
References: <1154@sdrc.UUCP> <132200@sun.Eng.Sun.COM> <4663@crltrx.crl.dec.com> <132219@sun.Eng.Sun.COM> <4666@crltrx.crl.dec.com> <4559@hemuli.tik.vtt.fi> <4956@helios.ee.lbl.gov>
Organization: Technical Research Centre of Finland, Laboratory for Information Processing (VTT/TIK)
Lines: 15

In article <4956@helios.ee.lbl.gov> envbvs@epb2.lbl.gov (Brian V. Smith) writes:
>In article <4559@hemuli.tik.vtt.fi> I write:
>> An example that is't bad to use signals in X programs is xfig-2.0.  At

>xfig has used setitimer() to blink the cursor since at least version 1.4.3.

Sorry, I didn't mean to point the finger at xfig _2.0_, I had to rip
the blinking out of xfig 1.4, too.

>If someone has a better way to do it, I would appreciate the input.

Don't do it?
-- 
Tor Lillqvist,
working, but not speaking, for the Technical Research Centre of Finland