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
Message-ID: <2510@apctrc.UUCP>
Date: 10 Jan 91 14:09:02 GMT
References: <25167.9012181515@orbweb.spider.co.uk> <1991Jan4.143707.1758@siesoft.co.uk>
Sender: news@trc.amoco.com
Reply-To: zjmw36@trc.amoco.com (Joe M. Wade)
Distribution: na
Organization: Amoco Production Company
Lines: 30
Originator: zjmw36@gpss36


In article <1991Jan4.143707.1758@siesoft.co.uk>, huw@siesoft.co.uk (Huw Roberts) writes:
|> 
|> I have the opposite problem - I am using an ErrorDialog to display an error
|> to the user.  The user has the option either to continue regardless or to cancel
|> the operation, but he can also get help (another dialog) to allow him to make
|> the decision.
|> My problem is that when the user selects the help button, the error dialog is
|> removed from the screen so he is unable to then choose one of the other
|> options.  I want to retain the ErrorDialog until the user chooses one of the
|> other options.
|> 
|> (I am using XmCreateErrorDialog followed by XtManageChild to display the
|> widget and am not destroying or unmapping it subsequently)
|> 
|> Thanks,  Huw

Setting XmNautoUnmanage attribute on your dialog should make it stay 
up when your help button is pushed. However, you will have to do 
the XtUnmanage yourself for your other buttons for which you want the 
dialog to go away. You can either add a callback on each button which 
unmanages the dialog or you can add the call at the top of any existing
callbacks that you have.

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