Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!decwrl!bacchus.pa.dec.com!wsl.dec.com!heiney
From: heiney@wsl.dec.com (Bob Heiney)
Newsgroups: comp.windows.x.motif
Subject: Re: Pushbutton callback problem
Message-ID: <1990Aug15.171547.17370@wrl.dec.com>
Date: 15 Aug 90 17:15:47 GMT
References: <9008150552.AA01009@ucisae.isae.cancol.oz>
Sender: news@wrl.dec.com (News)
Reply-To: heiney@wsl.dec.com (Bob Heiney)
Distribution: inet
Organization: DEC Western Software Lab
Lines: 33

In article <9008150552.AA01009@ucisae.isae.cancol.oz>,
jan@ucisae.isae.cancol.oz.au (Jan Newmarch) writes:
|> 
|> I have a pushbutton within a form within a dialog shell. When I push the
|> button, not only does it call the callback that I have added, but it also
|> exits the whole dialog! I presume it unmanages it but I don't know. The 
|> bulletin board doco says that it defines Btn1Down as Arm() and Btn1Up
|> as Activate() but that doesn't help me much. I want the dialog to stick
|> around until I tell it to go.

|> but that leaves these questions: a) Am I doing this the right way; b) Who
|> is adding these extra callbacks (if that's what is happening), and what
|> do they do; and c) Why the  *?!!?* can't I find it in the Motif doco?

Try looking at the BulletinBoard resource XmNautoUnmanage.

Page 1-187 of the hardcover OSF/MOTIF Programmer's reference says:

XmNautoUnmanage
	Controls whether or not BulletinBoard is automatically unmanaged
	after a button is activated.  If True, BulletinBoard adds a callback
	to button children ... that unmanages the BulletinBoard when a
	button is activated; and, the unmap callbacks are called if the parent
	of the BulletinBoard is a DialogShell.  If False, the BulletinBoard is
	not automatically unmanaged.

The default value is True.

Hope this answers your question.  :-)

Bob Heiney
Graphics Consultant
heiney@dec.com