Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!ISI.COM!tsang
From: tsang@ISI.COM (Kam C. Tsang)
Newsgroups: comp.windows.x.motif
Subject: XmUpdateDisplay - the little engine that couldn't?
Message-ID: <9106180246.AA07832@phecda>
Date: 18 Jun 91 02:46:43 GMT
References: <MONTNARO.91Jun17153835@spyder.crd.ge.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 28

> In my application I popup an XmMessageDialog widget before launching into a
> long operation. I've experimented with calling XmUpdateDisplay one or more
> times before the operation, in an attempt to force the message to display
> properly. My experiments have been unsuccessful thusfar.

Try this:

void ProcessAllExposeEvents()
{ // somehow you have to get to your own appContext
   // see pp 312, 6.10, "X Window System Toolkit"
   //                   by Paul Asente and Ralph Swick
   while (XtAppPending(appContext) & XtIMXEvent) {
      XEvent event;
      XtAppPeekEvent(appContext, &event);
      if ((event.type == Expose) || (event.type == MapNotify))
	 XtAppProcessEvent(appContext, XtIMXEvent);
      else
	 break;
   }
}

-kam
     ----------------------------+-----------------------------
                      Kam Tsang  |  User Interface Group
           (408) 980-1590 x 275  |  Integrated Systems, Inc.
           (408) 980-0400 [Fax]  |  3620 Jay Street
                  tsang@isi.com  |  Santa Clara, CA  94054
     ----------------------------+-----------------------------