🚀 go-pugleaf

In article <1993Jan1.161847.2266@vela.acs.oakland.edu>, sglanger@vela.acs.oakland.edu (LANGER STEVEN C) writes:
|> When using functions like
|> 	dialog = XmCreateMessageDialog(parent, "my_dialog", NULL, 0);
|> 
|> why does the dialog always come up with the title bar
|> 		"my_dialog_popup"
|> 
|> I can override this from an app-defaults file, but I'd like to just do
|> it in the code. I've tried
|> 	XtVaSetValues (dialog, XmNlabelString, "my_dialog", NULL);
|> 
|> and XtVaSetValues (dialog, XmNlabelType, "my_dialog", NULL);
|> 
|> but the title bar always has _popup appended to it.
|> XtCreateManagedWidget does not do this, but is not as conveneient.
|> Any suggestions?

The convenience function XmCreateMessageDialog() creates a DialogShell
(named my_dialog_popup), with a MessageBox child (named my_dialog).
The widget ID of the Message Box is returned to you.

The title you see is is the name of the Dialog Shell unless you set the
dialog shell's title.

	* setting the app-default file provides a title for the Dialog Shell

	* Doing SetValues on the Message box does not.  Doing it on
	  XtParent(dialog) should.

	* Passing an arg list to the XmCreateMessageDialog call would work,
	  because these args are also passed along to the Dialog Shell
	  when it is created.

XtCreateManagedWidget works differently because, unlike the convenience
function, it is not creating a dialog shell behind your back.

I seem to recall that this is all explained in some manual, but I could not
quickly locate it.

--Bob