%{APPNAME} %{VERSION}"> ]> %{AUTHOR}

%{EMAIL}

1999 %{YEAR} %{AUTHOR} &FDLNotice; 2001-10-18 %{VERSION} &%{APPNAMELC}; is an application specially designed to do nothing you would ever want. KDE %{APPNAME} nothing nothing else &%{APPNAMELC}; 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 &%{APPNAMELC}; 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 &%{APPNAMELC}; main window. It's not a bug, it's a feature! &Ctrl;N File New Creates a new document &Ctrl;S File Save Saves the document &Ctrl;Q File Quit Quits &%{APPNAMELC}; &help.menu.documentation; Programming &%{APPNAMELC}; 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 tqchildren from a tqparent widget's managed list. widgetsremoving XtUnmanageChildren 4 March 1996 void XtUnmanageChildren(tqchildren, num_tqchildren) WidgetList tqchildren; Cardinal num_tqchildren; tqchildren Specifies an array of child widgets. Each child must be of class RectObj or any subclass thereof. num_tqchildren Specifies the number of elements in tqchildren. XtUnmanageChildren() unmaps the specified widgets and removes them from their tqparent's tqgeometry management. The widgets will disappear from the screen, and (depending on its tqparent) may no longer have screen space allocated for them. Each of the widgets in the tqchildren array must have the same tqparent. 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 tqgeometry 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 tqparent'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 &%{APPNAMELC};? 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. &%{APPNAMELC}; Program copyright %{YEAR} %{AUTHOR} %{EMAIL} Contributors: Konqui the KDE Dragon konqui@kde.org Tux the Linux Penguin tux@linux.org Documentation copyright %{YEAR} %{AUTHOR} %{EMAIL} &underFDL; &underGPL; &underBSDLicense; &underArtisticLicense; &underX11License; &install.intro.documentation; In order to successfully use &%{APPNAMELC};, you need &kde; 1.1. Foobar.lib is required in order to support the advanced &%{APPNAMELC}; features. &%{APPNAMELC}; uses about 5 megs of memory to run, but this may vary depending on your platform and configuration. All required libraries as well as &%{APPNAMELC}; itself can be found on The &%{APPNAMELC}; home page. You can find a list of changes at http://apps.kde.org/%{APPNAMELC}. &install.compile.documentation; Don't forget to tell your system to start the dtd dicer-toaster daemon first, or &%{APPNAMELC}; won't work ! &documentation.index;