Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!pa.dec.com!wsl.dec.com!klee
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: Event Loops
Message-ID: <1991Apr12.151934@wsl.dec.com>
Date: 12 Apr 91 22:19:34 GMT
References: <MALBERT.91Apr12135341@jeeves.shearson.com>
Sender: news@pa.dec.com (News)
Reply-To: klee@wsl.dec.com
Distribution: na
Organization: DEC Western Software Laboratory
Lines: 23

In article <MALBERT.91Apr12135341@jeeves.shearson.com>, malbert@jeeves.shearson.com (Marc Albert) writes:
|> I have an application that has multiple top level windows.  The event
|> loop looks something like this:
|> 	for (;;) {
|> 		if (XtAppPending(WindowOne))
|> 			XtDispatch();
|> 		if (XtAppPending(WindowTwo))
|> 			XtDispatch();
|> 	}
|> 
|> This method works fine. 

Are you sure this works?  XtAppPending takes an application context,
not a window, as its argument.  The application context can contain any
number of displays, with each display containing any number of
top-level windows.


-- 
Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@wsl.dec.com
uucp: uunet!decwrl!klee