Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!exodus!argv
From: argv@turnpike.Eng.Sun.COM (Dan Heller)
Newsgroups: comp.windows.x.motif
Subject: Re: XtAddTimeOut
Message-ID: <2665@exodus.Eng.Sun.COM>
Date: 13 Nov 90 18:46:50 GMT
References: <1990Nov12.152054@lbl.gov>
Sender: news@exodus.Eng.Sun.COM
Organization: O'Reilly && Associates
Lines: 18

In article <1990Nov12.152054@lbl.gov> ctday@lbl.gov (Christopher T. Day) writes:
> Has anybody else out there had trouble with XtAddTimeOut?  I know people for
> whom it works, but I'm not among them.  No errors are reported, just no
> timeout routines are ever called.  It most likely is my setup somewhere.

It's difficult to evaluate and advise you on the problem without
some context.  "It doesn't work" isn't good enough.  The only thing
I can recommend is RTFM (see O'Reilly Volumes 4 or 5).  Until more
information is available, I can't tell what could be the problem.
The only problem that I ever had was where I was using XtAddTimeOut()
rather than XtAppAddTimeout().  This occured once I switched from
XtInitialize() to XtVaAppInitialize().

--
dan
----------------------------------------------------
O'Reilly && Associates   argv@sun.com / argv@ora.com
Opinions expressed reflect those of the author only.