Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!helios.ee.lbl.gov!epb2.lbl.gov!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.windows.x
Subject: Re: X & signals
Keywords: xwindows signals
Message-ID: <4956@helios.ee.lbl.gov>
Date: 26 Feb 90 18:50:03 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>
Sender: usenet@helios.ee.lbl.gov
Reply-To: envbvs@epb2.lbl.gov (Brian V. Smith)
Organization: lbl
Lines: 14
X-Local-Date: 26 Feb 90 10:50:03 PST

In article <4559@hemuli.tik.vtt.fi>, tml@hemuli.tik.vtt.fi (Tor
Lillqvist) writes:
> An example that is't bad to use signals in X programs is xfig-2.0.  At
> least on HP-UX, it dumps core unless you #ifdef out the calls to
> setitimer in blink.c.  (Xfig uses interval timers to make a blinking
> cursor.)

xfig has used setitimer() to blink the cursor since at least version 1.4.3.
If someone has a better way to do it, I would appreciate the input.

_____________________________________
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
I don't speak for LBL, these non-opinions are all mine.