NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/comp/windows/x/intrinsi/688

Text File | 1992-12-27 | 1.1 KB | 32 lines

Newsgroups: comp.windows.x.intrinsics
Path: sparky!uunet!think.com!enterpoop.mit.edu!bloom-picayune.mit.edu!news
From: [e-mail]
Subject: X-fiendly sleep?
Message-ID: <[e-mail]>
Sender: [e-mail] (News system)
Nntp-Posting-Host: carbonara.mit.edu
Organization: Massachvsetts Institvte of Technology
Date: Sun, 27 Dec 1992 05:53:53 GMT
Lines: 20

I'm wondering if there exists any such thing as an X-friendly sleep,
i.e. sleep that would not grab the server. If I simply put sleep(2) in
a callback, events cannot be handled by the intrinsics during that
sleep, and if the window is exposed, it would not be updated until the
program return from the sleep function call.

What I want is a funtion that when called from a certain location of
the program with an argument of say 2 seconds, does not return from
that location until 2 seconds have passed, but in contrast to
sleep(2), those two seconds should not be spent idle, but in
XtAppMainLoop so that events could be properly handled during that
time.

Any idea if something like this is available. If not, could it be
implemented by timeouts? How?

Thanks.

E.D.