Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!uunet!dev1f.mdcbbs.com!watson
From: watson@dev1f.mdcbbs.com
Newsgroups: comp.windows.x.motif
Subject: Re: Pushbutton callback problem
Message-ID: <1990Aug17.174003.1@dev1f.mdcbbs.com>
Date: 17 Aug 90 17:40:03 GMT
References: <9008151804.AA10891@dvlseq.us.oracle.com>
Distribution: inet
Organization: McDonnell Douglas M&E, Cypress CA
Lines: 35

In article <9008151804.AA10891@dvlseq.us.oracle.com>, cuweiss.US2.oramail@us.oracle.com ("Connie Weiss ", note the U =>) writes:
> In-Reply-To: DVLSEQ:motif-request@alphalpha.com's message of 08-15-90 15:51
> 
> 
> I had the same problem, with a pushbutton in a
> bulletin board dialog.  My workaround was to put
> the pushbutton in a row column widget (even 
> though it was just one button).  It's a mystery
> to my as to why it behaves this way, I'm just
> hoping it's fixed in 1.1.
> 
> Connie Weiss
> (cuweiss@oracle.com)
> 
>

This problems refers to activation of push button children of bulletin board
or form dialogs causing the dialog to be unmanaged.  As mentioned in other
replies, setting the XmNautoUnmanage resource to false for the bulletin
board or form dialog parent will stop this behavior.

XmNautoUnmanage is a resource of XmBulletinBoard and XmForm, but NOT a
resource of XmRowColumn, so making your push button the child of a 
row column circumvents the auto unmanage behavior of the bulletin board
parent, as it should.

Let's hope this isn't "fixed in 1.1", since it seems to be behaving as
expected.


Catie Watson
McDonnell Douglas Manufacturing & Engineering
Cypress, California

(watson@dev1.mdcbbs.com)