xtunmanagea(3) [hpux man page]
XtUnmanageChild() XtUnmanageChild() Name XtUnmanageChild - remove a widget from its parent's managed list. Synopsis void XtUnmanageChild(w) Widget w; Inputs w Specifies the child widget to be unmanaged; must be of class RectObj or any subclass thereof. Description XtUnmanageChild() unmaps the specified widget and removes it from its parent's geometry management. The widget will disappear from the screen, and (depending on its parent) may no longer have screen space allocated for it. XtUnmanageChild() simply calls XtUnmanageChildren(). See that function for more information about the procedure for unmanaging a widget. Usage Unmanaging a widget is the usual method for temporarily making it invisible. It can be re-managed with XtManageChild(). You can unmap a widget, but leave it under geometry management by calling XtUnmapWidget(). You can destroy a widget's window without destroying the widget by calling XtUnrealizeWidget(). You can destroy a widget completely with XtDestroyWidget(). If you will be unmanaging several sibling widgets, it is more efficient to call XtUnmanageChildren() because this only generates a single call to the parent's change_managed() method. It is often more convenient to simply call XtUnmanageChild() several times, however. See Also XtIsManaged(1), XtManageChild(1), XtManageChildren(1), XtUnmanageChildren(1). Xt - Geometry Management XtUnmanageChild()
Check Out this Related Man Page
XtManageChildren() XtManageChildren() Name XtManageChildren - bring an array of widgets under their parent's geometry management. Synopsis void XtManageChildren(children, num_children) WidgetList children; Cardinal num_children; Inputs children Specifies an array of child widgets. The widgets must all be siblings and must be of class RectObj or any subclass thereof. num_children Specifies the number of children in the array. Description XtManageChildren() brings a list of widgets created with XtCreateWidget() under the geometry management of their parent. All widgets (except shell widgets) must be managed in order to be visible. Managing a widget will generally make it visible, unless its XtNmappedWhenManaged resource is False. The "Algorithm" section below details the procedure followed by XtManageChildren(). Usage To manage a single widget, you can use XtManageChild(). To unmanage widgets, use XtUnmanageChild() and XtUnmanageChildren(). If you are going to manage multiple children of the same managed and realized parent, it is more efficient to place those children widget into an array and call XtManageChildren() just once than it is to manage them individually. The former technique results in only a single call to the parent's change_managed() method. If you are creating widgets before the widget tree has been realized, however, managing them one at a time is fine. Algorithm XtManageChildren() performs the following: o Issues an error if the children do not all have the same parent or if the parent is not a subclass of compositeWidgetClass. o Returns immediately if the common parent is being destroyed; otherwise, for each unique child on the list, XtManageChildren() ignores the child if it already is managed or is being destroyed, and marks it otherwise. o If the parent is realized XtManageChildren() does the following: - Calls the change_managed() method of the widgets' parent. - Calls XtRealizeWidget() on each marked child that is unrealized. - Maps each marked child that has its XtNmappedWhenManaged resource True. The management of children is independent of the creation and ordering of the children. There is no special list of managed children; the layout routine of the parent should loop through the list of all children and simply ignore those that are not managed (see XtIsManaged()). Structures typedef Widget *WidgetList; See Also XtCreateManagedWidget(1), XtIsManaged(1), XtManageChild(1), XtMoveWidget(1), XtRealizeWidget(1), XtSetMappedWhenManaged(1), XtUnman- ageChild(1), XtUnmanageChildren(1). Xt - Widget Lifecycle XtManageChildren()