Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!lll-winken!elroy.jpl.nasa.gov!ames!sgi!shinobu!odin!sgi.com!karlton
From: karlton@sgi.com (Phil Karlton)
Newsgroups: comp.windows.x
Subject: Re: `Working dialogs' in Motif
Keywords: Motif, dialogs, synchronous window display
Message-ID: <4775@odin.SGI.COM>
Date: 1 Mar 90 20:37:27 GMT
References: <47834@wlbr.IMSD.CONTEL.COM> <1990Feb28.164742.1177@Citicorp.COM>
Sender: news@odin.SGI.COM
Reply-To: karlton@sgi.com
Organization: Silicon Graphics, WorkGroup Products Division
Lines: 15

In article <47834@wlbr.IMSD.CONTEL.COM>, greg@tweedledum.imsd.contel.com
(Greg Christy) writes:
>  *   This routine will wait (i.e., block) until an Expose event occurs
>  *   in the widget specified in the argument, process the event with
>  *   XtNextEvent() and then synchronize the server to flush out any
>  *   requests made during the execution of XtNextEvent().  This has the
>  *   effect of waiting for a widget to "appear".

There is a danger in this scheme. If the window for the widget is
completely obscurred, then this will end up wedging the application
until the window is uncovered. Unless you have some guarantee that the
window will be on top, waiting for a Map event would be a better idea.

PK
--