Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!apctrc!zjmw36
From: zjmw36@trc.amoco.com (Joe M. Wade)
Newsgroups: comp.windows.x.motif
Subject: Re: Warning Dialog
Keywords: Warning Dialog Hour Glass
Message-ID: <2484@apctrc.UUCP>
Date: 26 Dec 90 20:23:01 GMT
References: <421@nec-gw.nec.com>
Sender: news@trc.amoco.com
Reply-To: zjmw36@trc.amoco.com (Joe M. Wade)
Distribution: usa
Organization: Amoco Production Company
Lines: 33
Originator: zjmw36@gpss36


In article <421@nec-gw.nec.com>, achan@sparkle.nec.com (Amy Chan) writes:
|> >>
|> >>How can I ensure that a warning dialog widget disappears IMMEDIATELY after
|> >>clicking on (any of the buttons) OK or CANCEL OR HELP?
|> >>I tried putting XtDestroyWidget(w) as the  1st statement of the callback,
|> >>but It does not do the trick!
|> >>The dialog box seems to disappear only after the callback associated with any
|> >>of these buttons terminates!!
|> >>
|> 
|> Set the XmNautoUnmanage resource of your warning dialog widget to True.
|> 
No, the problem is that the callbacks get called before the dialog widget 
gets the unmanage from the motif code. I did just the opposite of your 
advice and set the XmNautoUnmanage resource to False. I then set up my
own callback which does the XtUnmanageChild. That callback gets called
before my other callback which is going to bring up the dialog again.
That was good enough for my snafu. Hopefully it will also work for the
original poster.

Happy Holidays !!

-- 
*  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *
*  Joe M. Wade (jwade@trc.amoco.com)         (918) 660-4387    *
*  Amoco Research Center * 4502 E. 41st St. * Tulsa, OK  74102 *
*  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *
-- 
*  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *
*  Joe M. Wade (jwade@trc.amoco.com)         (918) 660-4387    *
*  Amoco Research Center * 4502 E. 41st St. * Tulsa, OK  74102 *
*  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *