%ents; ]> George N. Ugnacious

gnu@kde.org

1999 2000 George N. Ugnacious &FDLNotice; 03/04/1999 1.01.00 &activemirrorcontrol; is an application specially designed to do nothing you would ever want. KDE kdeutils ActiveMirrorControl nothing nothing else &activemirrorcontrol; is a program that lets you do absolutely nothing. Please report any problems or feature requests to the KDE mailing lists. Here's a screenshot of &activemirrorcontrol; Screenshot It slices! It dices! and it comes with a free toaster! The Squiggle Tool Squiggle is used to draw squiggly lines all over the &activemirrorcontrol; main window. It's not a bug, it's a feature! Ctrln File New Creates a new document Ctrls File Save Saves the document Ctrlq File Quit Quits &activemirrorcontrol; Programming &activemirrorcontrol; plugins is a joy to behold. Just read through the next 66 pages of API's to learn how! XtUnmanageChildren Xt - Geometry Management XtUnmanageChildren remove a list of children from a parent widget's managed list. widgetsremoving XtUnmanageChildren 4 March 1996 void XtUnmanageChildren(children, num_children) WidgetList children; Cardinal num_children; 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. 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. 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 XtUnmanageChildren() is more efficient, however, because it only calls the parent's change_managed() method once. 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. The WidgetList type is simply an array of widgets: typedef Widget *WidgetList; &reporting.bugs; &updating.documentation; My Mouse doesn't work. How do I quit &activemirrorcontrol;? You silly goose! Check out the Commands Section for the answer. Why can't I twiddle my documents? You can only twiddle your documents if you have the foobar.lib installed. &activemirrorcontrol; Program copyright 1997 John Q. Hacker jqh@kde.org Contributors: Konqui the KDE Dragon konqui@kde.org Tux the Linux Penguin tux@linux.org Documentation copyright 1999 George N. Ugnacious gnu@kde.org Translations done by: Babel D. Fish babelfish@kde.org (Sanskrit) &underFDL; &underGPL; &underBSDLicense; &underArtisticLicense; &underX11License; &activemirrorcontrol; is part of the KDE project http://www.kde.org. &activemirrorcontrol; can be found in the kdeutils package on ftp://ftp.kde.org/pub/kde/, the main ftp site of the KDE project. In order to successfully use &activemirrorcontrol;, you need KDE 1.1. Foobar.lib is required in order to support the advanced &activemirrorcontrol; features. &activemirrorcontrol; uses about 5 megs of memory to run, but this may vary depending on your platform and configuration. All required libraries as well as &activemirrorcontrol; itself can be found on The &activemirrorcontrol; home page. You can find a list of changes at http://apps.kde.org/activemirrorcontrol. In order to compile and install KApp on your system, type the following in the base directory of the Icon Editor distribution: % ./configure % make % make install Since KApp uses autoconf and automake you should have not trouble compiling it. Should you run into problems please report them to the KDE mailing lists. Don't forget to tell your system to start the dtd dicer-toaster daemon first, or KApp won't work ! &documentation.index;