Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
XtPopup vs. XtManageChild
13 views
Skip to first unread message
Sergey V. Nedzelsky
Dec 2, 1999, 3:00:00 AM12/2/99
to
The following fragment of code is very typical:
// Creating a popup dialog
Widget dialog = XmCreateMessageDialog( parent, "Dialog", 0, 0 ); //
parent is initialized earlier in the code
XtManageChild( dialog );
XtPopup( XtParent( dialog ), XtGrabNone );
Why do we need the XtPopup call? XtManageChild maps the dialog, anyway.
In fact, if one comments the last line out, behavior does not change (at
least, visibly). I surfed the Net, but no one seems to care about it.
Thank you in advance,
Sergei
ken...@nojunk.rahul.net
Dec 2, 1999, 3:00:00 AM12/2/99
to
In article <3846945B...@sabre.com>,
Sergey V. Nedzelsky <sergey_n...@sabre.com> wrote:
>The following fragment of code is very typical:
>
>// Creating a popup dialog
>Widget dialog = XmCreateMessageDialog( parent, "Dialog", 0, 0 ); //
>parent is initialized earlier in the code
>XtManageChild( dialog );
>XtPopup( XtParent( dialog ), XtGrabNone );
>
>Why do we need the XtPopup call?
Sergey V. Nedzelsky <sergey_n...@sabre.com> wrote:
>The following fragment of code is very typical:
>
>// Creating a popup dialog
>Widget dialog = XmCreateMessageDialog( parent, "Dialog", 0, 0 ); //
>parent is initialized earlier in the code
>XtManageChild( dialog );
>XtPopup( XtParent( dialog ), XtGrabNone );
>
>Why do we need the XtPopup call?
You do not need XtPopup with Motif dialogs. Motif takes care of that for you.
--
Ken Lee, http://www.rahul.net/kenton/
0 new messages