Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

xtunmanageb(3) [hpux man page]

XtUnmanageChildren()													      XtUnmanageChildren()

Name
  XtUnmanageChildren - remove a list of children from a parent widget's managed list.

Synopsis
  void XtUnmanageChildren(children, num_children)
	 WidgetList children;
	 Cardinal num_children;

Inputs
  children   Specifies an array of child widgets.  Each child must be of class RectObj or any subclass thereof.

  num_children
	     Specifies the number of elements in children.

Description
  XtUnmanageChildren()	unmaps	the  specified	widgets and removes them from their parent's geometry management.  The widgets will disappear
  from the screen, and (depending on its parent) may no longer have screen space allocated for them.

  Each of the widgets in the children array must have the same parent.

  See the "Algorithm" section below for full details of the widget unmanagement procedure.

Usage
  Unmanaging widgets is the usual method for temporarily making them invisible.  They can be re-managed with XtManageChildren().

  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  are	only going to unmanage a single widget, it is more convenient to call XtUnmanageChild().  It is often more convenient to call
  XtUnmanageChild() several times than it is to declare and initialize an array of widgets to pass to XtUnmanageChildren().  Calling XtUnman-
  ageChildren() is more efficient, however, because it only calls the parent's change_managed() method once.

Algorithm
  XtUnmanageChildren() 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, XtUnmanageChildren() performs
     the following:

     -	Ignores the child if it already is unmanaged or is being destroyed.

     -	Otherwise, if the child is realized, it makes it nonvisible by unmapping it.

  o  Calls the change_managed() method of the widgets' parent if the parent is realized.

Structures
  The WidgetList type is simply an array of widgets:

     typedef Widget *WidgetList;

See Also
  XtDestroyWidget(1), XtIsManaged(1), XtManageChild(1), XtManageChildren(1), XtUnmanageChild(1).

Xt - Geometry Management												      XtUnmanageChildren()

Check Out this Related Man Page

XtManageChildren(3Xt)						     MIT X11R4						     XtManageChildren(3Xt)

Name
       XtManageChildren, XtManageChild, XtUnmanageChildren, XtUnmanageChild - manage and unmanage children

Syntax
       typedef Widget *WidgetList;

       void XtManageChildren(children, num_children)
	  WidgetList children;
	  Cardinal num_children;

       void XtManageChild(child)
	  Widget child;

       void XtUnmanageChildren(children, num_children)
	  WidgetList children;
	  Cardinal num_children;

       void XtUnmanageChild(child)
	  Widget child;

Arguments
       child	 Specifies the child.

       children  Specifies a list of child widgets.

       num_children
		 Specifies the number of children.

Description
       The function 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

       o    Returns immediately if the common parent is being destroyed; otherwise, for each unique child on the list, ignores the child if it
	    already is managed or is being destroyed and marks it if not.

       o    If the parent is realized and after all children have been marked, it makes some of the newly managed children viewable:

	    -	 Calls the change_managed routine of the widgets' parent.

	    -	 Calls on each previously unmanaged child that is unrealized.

	    -	 Maps each previously unmanaged child that has map_when_managed

       Managing children is independent of the ordering of children and independent of creating and deleting children.	The layout routine of the
       parent should consider children whose managed field is and should ignore all other children.  Note that some composite widgets, especially
       fixed boxes, call from their insert_child procedure.

       If the parent widget is realized, its change_managed procedure is called to notify it that its set of managed children has changed.  The
       parent can reposition and resize any of its children.  It moves each child as needed by calling which first updates the x and y fields and
       then calls if the widget is realized.

       The function constructs a of length one and calls

       The function 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

       o    Returns immediately if the common parent is being destroyed; otherwise, for each unique child on the list, performs the following:

	    -	 Ignores the child if it already is unmanaged or is being destroyed and marks it if not.

	    -	 If the child is realized, it makes it nonvisible by unmapping it.

       o    Calls the change_managed routine of the widgets' parent after all children have been marked if the parent is realized.

       does not destroy the children widgets.  Removing widgets from a parent's managed set is often a temporary banishment, and, some time later,
       you may manage the children again.

       The function constructs a widget list of length one and calls

See Also
       XtMapWidget(3Xt), XtRealizeWidget(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

															     XtManageChildren(3Xt)
Man Page