# The &tork; Handbook

Robert Hogan

    robert@roberthogan.net

1999
2006
Robert Hogan
&FDLNotice;
2001-10-18
0.1

&tork; is an application specially designed to do nothing you would ever want.

KDE
tork
nothing
nothing else

## Introduction

&tork; is a program that lets you do absolutely nothing. Please report any problems or feature requests to the &kde; mailing lists.

## Using &tork;

Here's a screenshot of &tork; Screenshot

### More &tork; features

It slices! It dices! and it comes with a free toaster!

The Squiggle Tool Squiggle is used to draw squiggly lines all over the &tork; main window. It's not a bug, it's a feature!

## Command Reference

### The main &tork; window

#### The File Menu

&Ctrl;N File New

  Creates a new document

&Ctrl;S File Save

  Saves the document

&Ctrl;Q File Quit

  Quits &tork;

#### The Help Menu

&help.menu.documentation;

## Developer's Guide to &tork;

Programming &tork; 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.
4 March 1996

    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 `XtUnmanageChildren()` is more efficient, however, because it only calls the parent's `change_managed()` method once.

#### Algorithm

`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.

#### Structures

The WidgetList type is simply an array of widgets:

    typedef Widget *WidgetList;

## Questions and Answers

&reporting.bugs; &updating.documentation;

My Mouse doesn't work. How do I quit &tork;?

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.

## Credits and License

&tork;

Program copyright 2006 Robert Hogan robert@roberthogan.net

Contributors:

- Konqui the KDE Dragon konqui@kde.org

- Tux the Linux Penguin tux@linux.org

Documentation copyright 2006 Robert Hogan robert@roberthogan.net

&underFDL;

&underGPL; &underBSDLicense; &underArtisticLicense; &underX11License;

## Installation

### How to obtain &tork;

&install.intro.documentation;

### Requirements

In order to successfully use &tork;, you need &kde; 1.1. Foobar.lib is required in order to support the advanced &tork; features. &tork; uses about 5 megs of memory to run, but this may vary depending on your platform and configuration.

All required libraries as well as &tork; itself can be found on The &tork; home page.

You can find a list of changes at http://apps.kde.org/tork.

### Compilation and Installation

&install.compile.documentation;

### Configuration

Don't forget to tell your system to start the `dtd` dicer-toaster daemon first, or &tork; won't work !

&documentation.index;