Museum

Home

Lab Overview

Retrotechnology Articles

⇒ Online Manual

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

XtAppCreateShell(3Xt)

XtCreatePopupShell(3Xt)




XtCreateWidget(3Xt) XtCreateWidget(3Xt)
NAME XtCreateWidget, XtCreateManagedWidget, XtDestroyWidget - create and destroy widgets SYNOPSIS 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; DESCRIPTION The XtCreateWidget function performs much of the boilerplate operations of widget creation by doing these operations: Checks to see if the class_initialize procedure has been called for this class and for all superclasses and, if not, calls those necessary in a superclass-to- subclass order. Allocates memory for the widget instance. If the parent is a subclass of constraintWidgetClass, allocates memory for the parent's constraints and stores the address of this memory into the constraints member. Initializes the core nonresource data members (for ex- ample, parent and visible). Initializes the resource members (for example, background_pixel) by using the resource lists specified for this class and all superclasses. If the parent is a subclass of constraintWidgetClass, initializes the resource members of the constraints record by using the constraint resource list specified for the parent's class and all superclasses up to constraintWidgetClass. November, 1990 1



XtCreateWidget(3Xt) XtCreateWidget(3Xt)
Calls the initialize procedures for the widget by starting at the core initialize procedure on down to the widget's initialize procedure. If the parent is a subclass of compositeWidgetClass, puts the widget into its parent's children list by cal- ling its parent's insert_child procedure. For further information, see Section 3.5 in X Toolkit Intrinsics - C Language Interface. If the parent is a subclass of constraintWidgetClass, calls the constraint initialize procedures, starting at constraintWidgetClass on down to the parent's con- straint initialize procedure. Note that you can determine the number of arguments in an argument list by using the XtNumber macro. For further in- formation, see Section 11.1 in X Toolkit Intrinsics - C Language Interface. The XtCreateManagedWidget function convenience routine that calls XtCreateWidget and XtManageChild. The XtDestroyWidget 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 procedure of the widget being des- troyed. This requires a two-phase destroy process in order to avoid dangling references to destroyed widgets. In phase one, XtDestroyWidget performs these operations: If the being_destroyed member of the widget is TRUE, it returns immediately. Recursively descends the widget tree and sets the being_destroyed member to TRUE for the widget and all children. 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 widget 2 occurs after widget 1 on the destroy list, widget 2 is not a descendent of widget 1. (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 registered with the event and translation managers), that is, when the current invocation of XtDispatchEvent is about to return or immediately if not in 2 November, 1990



XtCreateWidget(3Xt) XtCreateWidget(3Xt)
XtDispatchEvent. In phase two, XtDestroyWidget performs these operations on each entry in the destroy list: Calls the destroy callback procedures registered on the widget (and all descendants) in post-order (it calls children callbacks before parent callbacks). If the widget's parent is a subclass of compositeWidgetClass and if the parent is not being destroyed, it calls XtUnmanageChild on the widget and then calls the widget's parent's delete_child procedure (see Section 3.4 in X Toolkit Intrinsics - C Language Interface). If the widget's parent is a subclass of constraintWidgetClass, it calls the constraint destroy procedure for the parent, then the parent's superclass, until finally it calls the constraint destroy procedure for constraintWidgetClass. Calls the destroy methods for the widget (and all des- cendants) in post-order. For each such widget, it calls the destroy procedure declared in the widget class, then the destroy procedure declared in its su- perclass, until finally it calls the destroy procedure declared in the Core class record. Calls XDestroyWindow if the widget is realized (that is, has an X window). The server recursively destroys all descendant windows. Recursively descends the tree and deallocates all pop- up widgets, constraint records, callback lists and, if the widget is a subclass of compositeWidgetClass, chil- dren. Arguments These functions accept the following 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 November, 1990 3



XtCreateWidget(3Xt) XtCreateWidget(3Xt)
list. parent Specifies the parent widget. w Specifies the widget. widget-class Specifies the widget class pointer for the created widget. SEE ALSO XtAppCreateShell(3Xt), XtCreatePopupShell(3Xt)
X Toolkit Intrinsics - C Language Interface
Xlib - C Language Interface 4 November, 1990

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026