Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!sp29.csrd.uiuc.edu!hammer
From: hammer@sp29.csrd.uiuc.edu (David Hammerslag)
Newsgroups: comp.windows.x
Subject: Re: Synchronous vs Asynchrounous
Message-ID: <1990Feb3.171406.14379@ux1.cso.uiuc.edu>
Date: 3 Feb 90 17:14:06 GMT
References: <9002021641.AA24460@expo.lcs.mit.edu> <1990Feb1.213625.12870@ux1.cso.uiuc.edu>
Sender: news@ux1.cso.uiuc.edu (News)
Reply-To: hammer@uicsrd.csrd.uiuc.edu
Organization: University of Illinois Center for Supercomputing Research and Development
Lines: 27

In article <9002021641.AA24460@expo.lcs.mit.edu>, kit@EXPO.LCS.MIT.EDU
(Chris D. Peterson) writes:
> 
> [ David Hammerslag (hammer@uicsrd.csrd.uiuc.edu) writes: ]
> 
> > I faced a similar problem.  Here is what I did.  (Caveat:  it ain't pretty,
> > but is seems to work). If anybody is willing to share a more reasonable 
> > solution, I would like to see it.
> 
> 
> This is one of the best solutions I have seen to this problem.  In face using
> XtAppAddTimeout() you can even set a global variable to have this loop
time out
> after a few seconds, so that your application doesn't hang if the window
> happens to be covered and doesn't receive an expose event.  
> 
> 
> 						Chris D. Peterson     
> 						MIT X Consortium 

Well, now I have to 'fess up.  The solution I posted was inspired by the way
the same problem was solved in "xman."  No wonder you liked it!

-------------------------------------------------------------------------------
David Hammerslag            | "Woe to those who are wise in their own
hammer@uicsrd.csrd.uiuc.edu |  eyes and clever in their own sight." Isaiah 5:21
-------------------------------------------------------------------------------