xtcreatepob(3) [hpux man page]
XtCreatePopupShell() XtCreatePopupShell() Name XtCreatePopupShell - create a popup shell widget. Synopsis Widget XtCreatePopupShell(name, widget_class, parent, args, num_args) String name; WidgetClass widget_class; Widget parent; ArgList args; Cardinal num_args; Inputs name Specifies the resource name for the created shell widget. widget_class Specifies the widget class pointer for the created shell widget; must be shellClass or any subclass. parent Specifies the parent widget; must be of class Core or any subclass thereof. args Specifies the argument list to override the resource defaults. num_args Specifies the number of arguments in the argument list. Returns A widget of class widget_class created as a popup child of parent. Description XtCreatePopupShell() checks that widget_class is a subclass of Shell, and, if it is, creates a widget of that class. The widget is not stored in the children array (maintained by Composite widgets), but rather in the popup_list array (which all widgets have). The screen resource for this widget is determined by first scanning args for the XtNscreen resource. If it is not found, the resource database associated with the parent's screen is queried. If both queries fail, the parent's screen is used. Once the screen is deter- mined, the resource database associated with that screen is used to retrieve all remaining resources for the widget not specified in args. Usage All shell widgets other than those created by XtAppInitialize() and XtAppCreateShell() must be created with XtCreatePopupShell(). Popup shells can be a child of any widget, not just Composite widgets. Remember that shell widgets can only have a single child, which will gen- erally be the layout widget that arranges whatever grandchildren widgets are to appear in the popup. Creating and realizing a popup shell widget is not enough to make it visible. To make a shell pop up, use XtPopup() or one of the prede- fined callback procedures or menu actions that call this function. To make it popdown, call XtPopdown(). Rather than initializing an ArgList to pass to XtCreatePopupShell(), you can call XtVaCreatePopupShell() which accepts a NULL-terminated variable length argument list of resource names and resource values. See Also XtCallbackExclusive(1), XtMenuPopup(1), XtPopdown(1), XtPopup(1), XtVaCreatePopupShell(1). Xt - Pop Ups XtCreatePopupShell()
Check Out this Related Man Page
XtCreateWidget(3Xt) MIT X11R4 XtCreateWidget(3Xt) Name XtCreateWidget, XtCreateManagedWidget, XtDestroyWidget - create and destroy widgets Syntax Widget XtCreateWidget(name, widget_class, parent, args, num_args) String name; WidgetClass widget_class; Widget parent; ArgList args; Cardinal num_args; Widget XtCreateManagedWidget(name, widget_class, parent, args, num_args) String name; WidgetClass widget_class; Widget parent; ArgList args; Cardinal num_args; void XtDestroyWidget(w) Widget w; Arguments args Specifies the argument list to override the resource defaults. name Specifies the resource name for the created widget, which is used for retrieving resources and, for that reason, should not be the same as any other widget that is a child of same parent. num_args Specifies the number of arguments in the argument list. parent Specifies the parent widget. w Specifies the widget. widget_class Specifies the widget class pointer for the created widget. Description The function performs much of the boilerplate operations of widget creation: o Checks to see if the class_initialize procedure has been called for this class and for all superclasses and, if not, calls those nec- essary in a superclass-to-subclass order. o Allocates memory for the widget instance. o If the parent is a subclass of it allocates memory for the parent's constraints and stores the address of this memory into the con- straints field. o Initializes the core nonresource data fields (for example, parent and visible). o Initializes the resource fields (for example, background_pixel) by using the resource lists specified for this class and all super- classes. o If the parent is a subclass of it initializes the resource fields of the constraints record by using the constraint resource list specified for the parent's class and all superclasses up to o Calls the initialize procedures for the widget by starting at the initialize procedure on down to the widget's initialize procedure. o If the parent is a subclass of it puts the widget into its parent's children list by calling its parent's insert_child procedure. For further information, see Section 3.5. o If the parent is a subclass of it calls the constraint initialize procedures, starting at on down to the parent's constraint initial- ize procedure. Note that you can determine the number of arguments in an argument list by using the macro. For further information, see Section 11.1. The function is a convenience routine that calls and The function provides the only method of destroying a widget, including widgets that need to destroy themselves. It can be called at any time, including from an application callback routine of the widget being destroyed. This requires a two-phase destroy process in order to avoid dangling references to destroyed widgets. In phase one, performs the following: o If the being_destroyed field of the widget is it returns immediately. o Recursively descends the widget tree and sets the being_destroyed field to for the widget and all children. o Adds the widget to a list of widgets (the destroy list) that should be destroyed when it is safe to do so. Entries on the destroy list satisfy the invariant that if w2 occurs after w1 on the destroy list then w2 is not a descendent of w1. (A descendant refers to both normal and pop-up children.) Phase two occurs when all procedures that should execute as a result of the current event have been called (including all procedures regis- tered with the event and translation managers), that is, when the current invocation of is about to return or immediately if not in In phase two, performs the following on each entry in the destroy list: o Calls the destroy callback procedures registered on the widget (and all descendants) in post-order (it calls children callbacks before parent callbacks). o If the widget's parent is a subclass of and if the parent is not being destroyed, it calls on the widget and then calls the widget's parent's delete_child procedure (see Section 3.4). o If the widget's parent is a subclass of it calls the constraint destroy procedure for the parent, then the parent's superclass, until finally it calls the constraint destroy procedure for o Calls the destroy methods for the widget (and all descendants) in post-order. For each such widget, it calls the destroy procedure declared in the widget class, then the destroy procedure declared in its superclass, until finally it calls the destroy procedure declared in the Core class record. o Calls if the widget is realized (that is, has an X window). The server recursively destroys all descendant windows. o Recursively descends the tree and deallocates all pop-up widgets, constraint records, callback lists and, if the widget is a subclass of children. See Also XtAppCreateShell(3Xt), XtCreatePopupShell(3Xt) X Window System Toolkit: The Complete Programmer's Guide and Specification, Paul J. Asente and Ralph Swick X Window System: The Complete Reference, Second Edition, Robert W. Scheifler and James Gettys XtCreateWidget(3Xt)