Rename ntqapplication, ntqconfig and ntqmodules files to equivalent tq*

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

1 files changed, 189 insertions, 189 deletions

diff --git a/doc/man/man3/tqapplication.3qt b/doc/man/man3/tqapplication.3qt
index 3761797b7..aa073c581 100644
--- a/doc/man/man3/tqapplication.3qt
+++ b/doc/man/man3/tqapplication.3qt
@@ -1,5 +1,5 @@
 '\" t
-.TH QApplication 3qt "2 February 2007" "Trolltech AS" \" -*- nroff -*-
+.TH TQApplication 3qt "2 February 2007" "Trolltech AS" \" -*- nroff -*-
 .\" Copyright 1992-2007 Trolltech ASA.  All rights reserved.  See the
 .\" license file included in the distribution for a complete license
 .\" statement.
@@ -7,34 +7,34 @@
 .ad l
 .nh
 .SH NAME
-QApplication \- Manages the GUI application's control flow and main settings
+TQApplication \- Manages the GUI application's control flow and main settings
 .SH SYNOPSIS
-\fC#include <ntqapplication.h>\fR
+\fC#include <tqapplication.h>\fR
 .PP
 Inherits TQObject.
 .PP
 .SS "Public Members"
 .in +1c
 .ti -1c
-.BI "\fBQApplication\fR ( int & argc, char ** argv )"
+.BI "\fBTQApplication\fR ( int & argc, char ** argv )"
 .br
 .ti -1c
-.BI "\fBQApplication\fR ( int & argc, char ** argv, bool GUIenabled )"
+.BI "\fBTQApplication\fR ( int & argc, char ** argv, bool GUIenabled )"
 .br
 .ti -1c
 .BI "enum \fBType\fR { Tty, GuiClient, GuiServer }"
 .br
 .ti -1c
-.BI "\fBQApplication\fR ( int & argc, char ** argv, Type type )"
+.BI "\fBTQApplication\fR ( int & argc, char ** argv, Type type )"
 .br
 .ti -1c
-.BI "\fBQApplication\fR ( Display * dpy, HANDLE visual = 0, HANDLE colormap = 0 )"
+.BI "\fBTQApplication\fR ( Display * dpy, HANDLE visual = 0, HANDLE colormap = 0 )"
 .br
 .ti -1c
-.BI "\fBQApplication\fR ( Display * dpy, int argc, char ** argv, HANDLE visual = 0, HANDLE colormap = 0 )"
+.BI "\fBTQApplication\fR ( Display * dpy, int argc, char ** argv, HANDLE visual = 0, HANDLE colormap = 0 )"
 .br
 .ti -1c
-.BI "virtual \fB~QApplication\fR ()"
+.BI "virtual \fB~TQApplication\fR ()"
 .br
 .ti -1c
 .BI "int \fBargc\fR () const"
@@ -404,13 +404,13 @@ Inherits TQObject.
 .br
 .in -1c
 .SH DESCRIPTION
-The QApplication class manages the GUI application's control flow and main settings.
+The TQApplication class manages the GUI application's control flow and main settings.
 .PP
 It contains the main event loop, where all events from the window system and other sources are processed and dispatched. It also handles the application's initialization and finalization, and provides session management. It also handles most system-wide and application-wide settings.
 .PP
-For any GUI application that uses Qt, there is precisely one QApplication object, no matter whether the application has 0, 1, 2 or more windows at any time.
+For any GUI application that uses Qt, there is precisely one TQApplication object, no matter whether the application has 0, 1, 2 or more windows at any time.
 .PP
-The QApplication object is accessible through the global pointer \fCqApp\fR. Its main areas of responsibility are:
+The TQApplication object is accessible through the global pointer \fCqApp\fR. Its main areas of responsibility are:
 .IP
 .TP
 It initializes the application with the user's desktop settings such as palette(), font() and doubleClickInterval(). It keeps track of these properties in case the user changes the desktop globally, for example through some kind of control panel.
@@ -446,9 +446,9 @@ On the X window system, it provides functions to flush and sync the communicatio
 It provides support for sophisticated session management. This makes it possible for applications to terminate gracefully when the user logs out, to cancel a shutdown process if termination isn't possible and even to preserve the entire application's state for a future session. See isSessionRestored(), sessionId() and commitData() and saveState() for details.
 .IP
 .PP
-The Application walk-through example contains a typical complete main() that does the usual things with QApplication.
+The Application walk-through example contains a typical complete main() that does the usual things with TQApplication.
 .PP
-Since the QApplication object does so much initialization, it \fBmust\fR be created before any other objects related to the user interface are created.
+Since the TQApplication object does so much initialization, it \fBmust\fR be created before any other objects related to the user interface are created.
 .PP
 Since it also deals with common command line arguments, it is usually a good idea to create it \fIbefore\fR any interpretation or modification of \fCargv\fR is done in the application itself. (Note also that for X11, setMainWidget() may change the main widget according to the \fC-geometry\fR option. To preserve this functionality, you must set your defaults before setMainWidget() and any overrides after.)
 .PP
@@ -459,36 +459,36 @@ l - l. Groups of functions System settings desktopSettingsAware(), setDesktopSet
 .fi
 </center>
 .PP
-\fINon-GUI programs:\fR While TQt is not optimized or designed for writing non-GUI programs, it's possible to use some of its classes without creating a QApplication. This can be useful if you wish to share code between a non-GUI server and a GUI client.
+\fINon-GUI programs:\fR While TQt is not optimized or designed for writing non-GUI programs, it's possible to use some of its classes without creating a TQApplication. This can be useful if you wish to share code between a non-GUI server and a GUI client.
 .PP
 See also Main Window and Related Classes.
 .SS "Member Type Documentation"
-.SH "QApplication::ColorSpec"
+.SH "TQApplication::ColorSpec"
 .TP
-\fCQApplication::NormalColor\fR - the default color allocation policy
+\fCTQApplication::NormalColor\fR - the default color allocation policy
 .TP
-\fCQApplication::CustomColor\fR - the same as NormalColor for X11; allocates colors to a palette on demand under Windows
+\fCTQApplication::CustomColor\fR - the same as NormalColor for X11; allocates colors to a palette on demand under Windows
 .TP
-\fCQApplication::ManyColor\fR - the right choice for applications that use thousands of colors
+\fCTQApplication::ManyColor\fR - the right choice for applications that use thousands of colors
 .PP
 See setColorSpec() for full details.
-.SH "QApplication::Encoding"
+.SH "TQApplication::Encoding"
 This enum type defines the 8-bit encoding of character string arguments to translate():
 .TP
-\fCQApplication::DefaultCodec\fR - the encoding specified by TQTextCodec::codecForTr() (Latin-1 if none has been set)
+\fCTQApplication::DefaultCodec\fR - the encoding specified by TQTextCodec::codecForTr() (Latin-1 if none has been set)
 .TP
-\fCQApplication::UnicodeUTF8\fR - UTF-8
+\fCTQApplication::UnicodeUTF8\fR - UTF-8
 .PP
 See also TQObject::tr(), TQObject::trUtf8(), and TQString::fromUtf8().
-.SH "QApplication::Type"
+.SH "TQApplication::Type"
 .TP
-\fCQApplication::Tty\fR - a console application
+\fCTQApplication::Tty\fR - a console application
 .TP
-\fCQApplication::GuiClient\fR - a GUI client application
+\fCTQApplication::GuiClient\fR - a GUI client application
 .TP
-\fCQApplication::GuiServer\fR - a GUI server application
+\fCTQApplication::GuiServer\fR - a GUI server application
 .SH MEMBER FUNCTION DOCUMENTATION
-.SH "QApplication::QApplication ( int & argc, char ** argv )"
+.SH "TQApplication::TQApplication ( int & argc, char ** argv )"
 Initializes the window system and constructs an application object with \fIargc\fR command line arguments in \fIargv\fR.
 .PP
 The global \fCqApp\fR pointer refers to this application object. Only one application object should be created.
@@ -541,12 +541,12 @@ The X11 version of TQt also supports some traditional X11 command line options:
 .TP
 -visual \fCTrueColor\fR, forces the application to use a TrueColor visual on an 8-bit display.
 .TP
--ncols \fIcount\fR, limits the number of colors allocated in the color cube on an 8-bit display, if the application is using the QApplication::ManyColor color specification. If \fIcount\fR is 216 then a 6x6x6 color cube is used (i.e. 6 levels of red, 6 of green, and 6 of blue); for other values, a cube approximately proportional to a 2x3x1 cube is used.
+-ncols \fIcount\fR, limits the number of colors allocated in the color cube on an 8-bit display, if the application is using the TQApplication::ManyColor color specification. If \fIcount\fR is 216 then a 6x6x6 color cube is used (i.e. 6 levels of red, 6 of green, and 6 of blue); for other values, a cube approximately proportional to a 2x3x1 cube is used.
 .TP
 -cmap, causes the application to install a private color map on an 8-bit display.
 .PP
 See also argc() and argv().
-.SH "QApplication::QApplication ( int & argc, char ** argv, bool GUIenabled )"
+.SH "TQApplication::TQApplication ( int & argc, char ** argv, bool GUIenabled )"
 Constructs an application object with \fIargc\fR command line arguments in \fIargv\fR. If \fIGUIenabled\fR is TRUE, a GUI application is constructed, otherwise a non-GUI (console) application is created.
 .PP
 Set \fIGUIenabled\fR to FALSE for programs without a graphical user interface that should be able to run without a window system.
@@ -571,7 +571,7 @@ The following example shows how to create an application that uses a graphical i
 .br
 #endif
 .br
-    QApplication app(argc, argv, useGUI);
+    TQApplication app(argc, argv, useGUI);
 .br
 .br
     if ( useGUI ) {
@@ -592,35 +592,35 @@ The following example shows how to create an application that uses a graphical i
 .br
   }
 .fi
-.SH "QApplication::QApplication ( int & argc, char ** argv, Type type )"
+.SH "TQApplication::TQApplication ( int & argc, char ** argv, Type type )"
 Constructs an application object with \fIargc\fR command line arguments in \fIargv\fR.
-.SH "QApplication::QApplication ( Display * dpy, HANDLE visual = 0, HANDLE colormap = 0 )"
+.SH "TQApplication::TQApplication ( Display * dpy, HANDLE visual = 0, HANDLE colormap = 0 )"
 Create an application, given an already open display \fIdpy\fR. If \fIvisual\fR and \fIcolormap\fR are non-zero, the application will use those as the default Visual and Colormap contexts.
 .PP
 \fBWarning:\fR TQt only supports TrueColor visuals at depths higher than 8 bits-per-pixel.
 .PP
 This is available only on X11.
-.SH "QApplication::QApplication ( Display * dpy, int argc, char ** argv, HANDLE visual = 0, HANDLE colormap = 0 )"
+.SH "TQApplication::TQApplication ( Display * dpy, int argc, char ** argv, HANDLE visual = 0, HANDLE colormap = 0 )"
 Create an application, given an already open display \fIdpy\fR and using \fIargc\fR command line arguments in \fIargv\fR. If \fIvisual\fR and \fIcolormap\fR are non-zero, the application will use those as the default Visual and Colormap contexts.
 .PP
 \fBWarning:\fR TQt only supports TrueColor visuals at depths higher than 8 bits-per-pixel.
 .PP
 This is available only on X11.
-.SH "QApplication::~QApplication ()\fC [virtual]\fR"
+.SH "TQApplication::~TQApplication ()\fC [virtual]\fR"
 Cleans up any window system resources that were allocated by this application. Sets the global variable \fCqApp\fR to 0.
-.SH "void QApplication::aboutTQt ()\fC [slot]\fR"
+.SH "void TQApplication::aboutTQt ()\fC [slot]\fR"
 Displays a simple message box about Qt. The message includes the version number of TQt being used by the application.
 .PP
 This is useful for inclusion in the Help menu of an application. See the examples/menu/menu.cpp example.
 .PP
 This function is a convenience slot for TQMessageBox::aboutTQt().
-.SH "void QApplication::aboutToQuit ()\fC [signal]\fR"
+.SH "void TQApplication::aboutToQuit ()\fC [signal]\fR"
 This signal is emitted when the application is about to quit the main event loop, e.g. when the event loop level drops to zero. This may happen either after a call to quit() from inside the application or when the users shuts down the entire desktop session.
 .PP
 The signal is particularly useful if your application has to do some last-second cleanup. Note that no user interaction is possible in this state.
 .PP
 See also quit().
-.SH "TQWidget * QApplication::activeModalWidget ()\fC [static]\fR"
+.SH "TQWidget * TQApplication::activeModalWidget ()\fC [static]\fR"
 Returns the active modal widget.
 .PP
 A modal widget is a special top level widget which is a subclass of TQDialog that specifies the modal parameter of the constructor as TRUE. A modal widget must be closed before the user can continue with other parts of the program.
@@ -628,7 +628,7 @@ A modal widget is a special top level widget which is a subclass of TQDialog tha
 Modal widgets are organized in a stack. This function returns the active modal widget at the top of the stack.
 .PP
 See also activePopupWidget() and topLevelWidgets().
-.SH "TQWidget * QApplication::activePopupWidget ()\fC [static]\fR"
+.SH "TQWidget * TQApplication::activePopupWidget ()\fC [static]\fR"
 Returns the active popup widget.
 .PP
 A popup widget is a special top level widget that sets the WType_Popup widget flag, e.g. the TQPopupMenu widget. When the application opens a popup widget, all events are sent to the popup. Normal widgets and modal widgets cannot be accessed before the popup widget is closed.
@@ -636,19 +636,19 @@ A popup widget is a special top level widget that sets the WType_Popup widget fl
 Only other popup widgets may be opened when a popup widget is shown. The popup widgets are organized in a stack. This function returns the active popup widget at the top of the stack.
 .PP
 See also activeModalWidget() and topLevelWidgets().
-.SH "TQWidget * QApplication::activeWindow () const"
+.SH "TQWidget * TQApplication::activeWindow () const"
 Returns the application top-level window that has the keyboard input focus, or 0 if no application window has the focus. Note that there might be an activeWindow() even if there is no focusWidget(), for example if no widget in that window accepts key events.
 .PP
 See also TQWidget::setFocus(), TQWidget::focus, and focusWidget().
 .PP
 Example: network/mail/smtp.cpp.
-.SH "void QApplication::addLibraryPath ( const TQString & path )\fC [static]\fR"
+.SH "void TQApplication::addLibraryPath ( const TQString & path )\fC [static]\fR"
 Append \fIpath\fR to the end of the library path list. If \fIpath\fR is empty or already in the path list, the path list is not changed.
 .PP
 The default path list consists of a single entry, the installation directory for plugins. The default installation directory for plugins is \fCINSTALL/plugins\fR, where \fCINSTALL\fR is the directory where TQt was installed.
 .PP
 See also removeLibraryPath(), libraryPaths(), and setLibraryPaths().
-.SH "TQWidgetList * QApplication::allWidgets ()\fC [static]\fR"
+.SH "TQWidgetList * TQApplication::allWidgets ()\fC [static]\fR"
 Returns a list of all the widgets in the application.
 .PP
 The list is created using \fCnew\fR and must be deleted by the caller.
@@ -661,7 +661,7 @@ Example that updates all widgets:
 .PP
 .nf
 .br
-    TQWidgetList  *list = QApplication::allWidgets();
+    TQWidgetList  *list = TQApplication::allWidgets();
 .br
     TQWidgetListIt it( *list );         // iterate over the widgets
 .br
@@ -684,7 +684,7 @@ The TQWidgetList class is defined in the \fCtqwidgetlist.h\fR header file.
 \fBWarning:\fR Delete the list as soon as you have finished using it. The widgets in the list may be deleted by someone else at any time.
 .PP
 See also topLevelWidgets(), TQWidget::visible, and TQPtrList::isEmpty().
-.SH "TQString QApplication::applicationDirPath ()"
+.SH "TQString TQApplication::applicationDirPath ()"
 Returns the directory that contains the application executable.
 .PP
 For example, if you have installed TQt in the \fCC:&#92;Trolltech&#92;Qt\fR directory, and you run the \fCdemo\fR example, this function will return "C:/Trolltech/Qt/examples/demo".
@@ -694,7 +694,7 @@ On Mac OS X this will point to the directory actually containing the executable,
 \fBWarning:\fR On Unix, this function assumes that argv[0] contains the file name of the executable (which it normally does). It also assumes that the current directory hasn't been changed by the application.
 .PP
 See also applicationFilePath().
-.SH "TQString QApplication::applicationFilePath ()"
+.SH "TQString TQApplication::applicationFilePath ()"
 Returns the file path of the application executable.
 .PP
 For example, if you have installed TQt in the \fCC:&#92;Trolltech&#92;Qt\fR directory, and you run the \fCdemo\fR example, this function will return "C:/Trolltech/Qt/examples/demo/demo.exe".
@@ -702,21 +702,21 @@ For example, if you have installed TQt in the \fCC:&#92;Trolltech&#92;Qt\fR dire
 \fBWarning:\fR On Unix, this function assumes that argv[0] contains the file name of the executable (which it normally does). It also assumes that the current directory hasn't been changed by the application.
 .PP
 See also applicationDirPath().
-.SH "int QApplication::argc () const"
+.SH "int TQApplication::argc () const"
 Returns the number of command line arguments.
 .PP
 The documentation for argv() describes how to process command line arguments.
 .PP
-See also argv() and QApplication::QApplication().
+See also argv() and TQApplication::TQApplication().
 .PP
 Examples:
 .)l chart/main.cpp and scribble/scribble.cpp.
-.SH "char ** QApplication::argv () const"
+.SH "char ** TQApplication::argv () const"
 Returns the command line argument vector.
 .PP
 \fCargv()[0]\fR is the program name, \fCargv()[1]\fR is the first argument and \fCargv()[argc()-1]\fR is the last argument.
 .PP
-A QApplication object is constructed by passing \fIargc\fR and \fIargv\fR from the \fCmain()\fR function. Some of the arguments may be recognized as TQt options and removed from the argument vector. For example, the X11 version of TQt knows about \fC-display\fR, \fC-font\fR and a few more options.
+A TQApplication object is constructed by passing \fIargc\fR and \fIargv\fR from the \fCmain()\fR function. Some of the arguments may be recognized as TQt options and removed from the argument vector. For example, the X11 version of TQt knows about \fC-display\fR, \fC-font\fR and a few more options.
 .PP
 Example:
 .PP
@@ -725,7 +725,7 @@ Example:
         // showargs.cpp - displays program arguments in a list box
 .br
 .br
-        #include <ntqapplication.h>
+        #include <tqapplication.h>
 .br
         #include <tqlistbox.h>
 .br
@@ -734,7 +734,7 @@ Example:
 .br
         {
 .br
-            QApplication a( argc, argv );
+            TQApplication a( argc, argv );
 .br
             TQListBox b;
 .br
@@ -754,20 +754,20 @@ Example:
 .PP
 If you run \fCshowargs -display unix:0 -font 9x15bold hello world\fR under X11, the list box contains the three strings "showargs"," hello" and "world".
 .PP
-Qt provides a global pointer, \fCqApp\fR, that points to the QApplication object, and through which you can access argc() and argv() in functions other than main().
+Qt provides a global pointer, \fCqApp\fR, that points to the TQApplication object, and through which you can access argc() and argv() in functions other than main().
 .PP
-See also argc() and QApplication::QApplication().
+See also argc() and TQApplication::TQApplication().
 .PP
 Examples:
 .)l chart/main.cpp and scribble/scribble.cpp.
-.SH "void QApplication::beep ()\fC [static]\fR"
+.SH "void TQApplication::beep ()\fC [static]\fR"
 Sounds the bell, using the default volume and sound.
-.SH "TQClipboard * QApplication::clipboard ()\fC [static]\fR"
+.SH "TQClipboard * TQApplication::clipboard ()\fC [static]\fR"
 Returns a pointer to the application global clipboard.
 .PP
 Examples:
 .)l regexptester/regexptester.cpp and showimg/showimg.cpp.
-.SH "void QApplication::closeAllWindows ()\fC [slot]\fR"
+.SH "void TQApplication::closeAllWindows ()\fC [slot]\fR"
 Closes all top-level windows.
 .PP
 This function is particularly useful for applications with many top-level windows. It could, for example, be connected to a "Quit" entry in the file menu as shown in the following code example:
@@ -793,17 +793,17 @@ See also TQWidget::close(), TQWidget::closeEvent(), lastWindowClosed(), quit(),
 .PP
 Examples:
 .)l action/application.cpp, application/application.cpp, helpviewer/helpwindow.cpp, mdi/application.cpp, and qwerty/qwerty.cpp.
-.SH "bool QApplication::closingDown ()\fC [static]\fR"
+.SH "bool TQApplication::closingDown ()\fC [static]\fR"
 Returns TRUE if the application objects are being destroyed; otherwise returns FALSE.
 .PP
 See also startingUp().
-.SH "int QApplication::colorSpec ()\fC [static]\fR"
+.SH "int TQApplication::colorSpec ()\fC [static]\fR"
 Returns the color specification.
 .PP
-See also QApplication::setColorSpec().
+See also TQApplication::setColorSpec().
 .PP
 Example: showimg/showimg.cpp.
-.SH "void QApplication::commitData ( TQSessionManager & sm )\fC [virtual]\fR"
+.SH "void TQApplication::commitData ( TQSessionManager & sm )\fC [virtual]\fR"
 This function deals with session management. It is invoked when the TQSessionManager wants the application to commit all its data.
 .PP
 Usually this means saving all open files, after getting permission from the user. Furthermore you may want to provide a means by which the user can cancel the shutdown.
@@ -815,7 +815,7 @@ Note that you should not exit the application within this function. Instead, the
 The default implementation requests interaction and sends a close event to all visible top level widgets. If any event was rejected, the shutdown is canceled.
 .PP
 See also isSessionRestored(), sessionId(), saveState(), and the Session Management overview.
-.SH "int QApplication::cursorFlashTime ()\fC [static]\fR"
+.SH "int TQApplication::cursorFlashTime ()\fC [static]\fR"
 Returns the text cursor's flash (blink) time in milliseconds. The flash time is the time required to display, invert and restore the caret display.
 .PP
 The default value on X11 is 1000 milliseconds. On Windows, the control panel value is used.
@@ -823,18 +823,18 @@ The default value on X11 is 1000 milliseconds. On Windows, the control panel val
 Widgets should not cache this value since it may be changed at any time by the user changing the global desktop settings.
 .PP
 See also setCursorFlashTime().
-.SH "TQTextCodec * QApplication::defaultCodec () const"
+.SH "TQTextCodec * TQApplication::defaultCodec () const"
 \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
 .PP
 Returns TQTextCodec::codecForTr().
-.SH "TQDesktopWidget * QApplication::desktop ()\fC [static]\fR"
+.SH "TQDesktopWidget * TQApplication::desktop ()\fC [static]\fR"
 Returns the desktop widget (also called the root window).
 .PP
 The desktop widget is useful for obtaining the size of the screen. It may also be possible to draw on the desktop. We recommend against assuming that it's possible to draw on the desktop, since this does not work on all operating systems.
 .PP
 .nf
 .br
-    TQDesktopWidget *d = QApplication::desktop();
+    TQDesktopWidget *d = TQApplication::desktop();
 .br
     int w = d->width();     // returns desktop width
 .br
@@ -844,31 +844,31 @@ The desktop widget is useful for obtaining the size of the screen. It may also b
 .PP
 Examples:
 .)l canvas/main.cpp, desktop/desktop.cpp, helpviewer/main.cpp, i18n/main.cpp, qmag/qmag.cpp, qwerty/main.cpp, and scribble/main.cpp.
-.SH "bool QApplication::desktopSettingsAware ()\fC [static]\fR"
+.SH "bool TQApplication::desktopSettingsAware ()\fC [static]\fR"
 Returns the value set by setDesktopSettingsAware(); by default TRUE.
 .PP
 See also setDesktopSettingsAware().
-.SH "int QApplication::doubleClickInterval ()\fC [static]\fR"
+.SH "int TQApplication::doubleClickInterval ()\fC [static]\fR"
 Returns the maximum duration for a double click.
 .PP
 The default value on X11 is 400 milliseconds. On Windows, the control panel value is used.
 .PP
 See also setDoubleClickInterval().
-.SH "int QApplication::enter_loop ()"
+.SH "int TQApplication::enter_loop ()"
 \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
 .PP
 This function enters the main event loop (recursively). Do not call it unless you really know what you are doing.
 .PP
-Use QApplication::eventLoop()->enterLoop() instead.
-.SH "TQEventLoop * QApplication::eventLoop ()\fC [static]\fR"
-Returns the application event loop. This function will return zero if called during and after destroying QApplication.
+Use TQApplication::eventLoop()->enterLoop() instead.
+.SH "TQEventLoop * TQApplication::eventLoop ()\fC [static]\fR"
+Returns the application event loop. This function will return zero if called during and after destroying TQApplication.
 .PP
-To create your own instance of TQEventLoop or TQEventLoop subclass create it before you create the QApplication object.
+To create your own instance of TQEventLoop or TQEventLoop subclass create it before you create the TQApplication object.
 .PP
 See also TQEventLoop.
 .PP
 Example: distributor/distributor.ui.h.
-.SH "int QApplication::exec ()"
+.SH "int TQApplication::exec ()"
 Enters the main event loop and waits until exit() is called or the main widget is destroyed, and returns the value that was set to exit() (which is 0 if exit() is called via quit()).
 .PP
 It is necessary to call this function to start event handling. The main event loop receives events from the window system and dispatches these to the application widgets.
@@ -881,7 +881,7 @@ See also quit(), exit(), processEvents(), and setMainWidget().
 .PP
 Examples:
 .)l helpsystem/main.cpp, life/main.cpp, network/archivesearch/main.cpp, network/ftpclient/main.cpp, opengl/main.cpp, t1/main.cpp, and t4/main.cpp.
-.SH "void QApplication::exit ( int retcode = 0 )\fC [static]\fR"
+.SH "void TQApplication::exit ( int retcode = 0 )\fC [static]\fR"
 Tells the application to exit with a return code.
 .PP
 After this function has been called, the application leaves the main event loop and returns from the call to exec(). The exec() function returns \fIretcode\fR.
@@ -894,58 +894,58 @@ See also quit() and exec().
 .PP
 Examples:
 .)l chart/chartform.cpp, extension/mainform.ui.h, and picture/picture.cpp.
-.SH "void QApplication::exit_loop ()"
+.SH "void TQApplication::exit_loop ()"
 \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
 .PP
 This function exits from a recursive call to the main event loop. Do not call it unless you are an expert.
 .PP
-Use QApplication::eventLoop()->exitLoop() instead.
-.SH "void QApplication::flush ()\fC [static]\fR"
+Use TQApplication::eventLoop()->exitLoop() instead.
+.SH "void TQApplication::flush ()\fC [static]\fR"
 Flushes the window system specific event queues.
 .PP
 If you are doing graphical changes inside a loop that does not return to the event loop on asynchronous window systems like X11 or double buffered window systems like MacOS X, and you want to visualize these changes immediately (e.g. Splash Screens), call this function.
 .PP
 See also flushX(), sendPostedEvents(), and TQPainter::flush().
-.SH "void QApplication::flushX ()\fC [static]\fR"
+.SH "void TQApplication::flushX ()\fC [static]\fR"
 Flushes the X event queue in the X11 implementation. This normally returns almost immediately. Does nothing on other platforms.
 .PP
 See also syncX().
 .PP
 Example: xform/xform.cpp.
-.SH "TQWidget * QApplication::focusWidget () const"
+.SH "TQWidget * TQApplication::focusWidget () const"
 Returns the application widget that has the keyboard input focus, or 0 if no widget in this application has the focus.
 .PP
 See also TQWidget::setFocus(), TQWidget::focus, and activeWindow().
-.SH "TQFont QApplication::font ( const TQWidget * w = 0 )\fC [static]\fR"
+.SH "TQFont TQApplication::font ( const TQWidget * w = 0 )\fC [static]\fR"
 Returns the default font for the widget \fIw\fR, or the default application font if \fIw\fR is 0.
 .PP
 See also setFont(), fontMetrics(), and TQWidget::font.
 .PP
 Examples:
 .)l qfd/fontdisplayer.cpp, themes/metal.cpp, and themes/themes.cpp.
-.SH "TQFontMetrics QApplication::fontMetrics ()\fC [static]\fR"
+.SH "TQFontMetrics TQApplication::fontMetrics ()\fC [static]\fR"
 Returns display (screen) font metrics for the application font.
 .PP
 See also font(), setFont(), TQWidget::fontMetrics(), and TQPainter::fontMetrics().
-.SH "TQSize QApplication::globalStrut ()\fC [static]\fR"
+.SH "TQSize TQApplication::globalStrut ()\fC [static]\fR"
 Returns the application's global strut.
 .PP
 The strut is a size object whose dimensions are the minimum that any GUI element that the user can interact with should have. For example no button should be resized to be smaller than the global strut size.
 .PP
 See also setGlobalStrut().
-.SH "void QApplication::guiThreadAwake ()\fC [signal]\fR"
+.SH "void TQApplication::guiThreadAwake ()\fC [signal]\fR"
 This signal is emitted after the event loop returns from a function that could block.
 .PP
 See also wakeUpGuiThread().
-.SH "bool QApplication::hasGlobalMouseTracking ()\fC [static]\fR"
+.SH "bool TQApplication::hasGlobalMouseTracking ()\fC [static]\fR"
 Returns TRUE if global mouse tracking is enabled; otherwise returns FALSE.
 .PP
 See also setGlobalMouseTracking().
-.SH "bool QApplication::hasPendingEvents ()"
-This function returns TRUE if there are pending events; otherwise returns FALSE. Pending events can be either from the window system or posted events using QApplication::postEvent().
-.SH "int QApplication::horizontalAlignment ( int align )\fC [static]\fR"
+.SH "bool TQApplication::hasPendingEvents ()"
+This function returns TRUE if there are pending events; otherwise returns FALSE. Pending events can be either from the window system or posted events using TQApplication::postEvent().
+.SH "int TQApplication::horizontalAlignment ( int align )\fC [static]\fR"
 Strips out vertical alignment flags and transforms an alignment \fIalign\fR of AlignAuto into AlignLeft or AlignRight according to the language used. The other horizontal alignment flags are left untouched.
-.SH "void QApplication::installTranslator ( TQTranslator * mf )"
+.SH "void TQApplication::installTranslator ( TQTranslator * mf )"
 Adds the message file \fImf\fR to the list of message files to be used for translations.
 .PP
 Multiple message files can be installed. Translations are searched for in the last installed message file, then the one from last, and so on, back to the first installed message file. The search stops as soon as a matching translation is found.
@@ -953,7 +953,7 @@ Multiple message files can be installed. Translations are searched for in the la
 See also removeTranslator(), translate(), and TQTranslator::load().
 .PP
 Example: i18n/main.cpp.
-.SH "bool QApplication::isEffectEnabled ( TQt::UIEffect effect )\fC [static]\fR"
+.SH "bool TQApplication::isEffectEnabled ( TQt::UIEffect effect )\fC [static]\fR"
 Returns TRUE if \fIeffect\fR is enabled; otherwise returns FALSE.
 .PP
 By default, TQt will try to use the desktop settings. Call setDesktopSettingsAware(FALSE) to prevent this.
@@ -961,11 +961,11 @@ By default, TQt will try to use the desktop settings. Call setDesktopSettingsAwa
 Note: All effects are disabled on screens running at less than 16-bit color depth.
 .PP
 See also setEffectEnabled() and TQt::UIEffect.
-.SH "bool QApplication::isSessionRestored () const"
+.SH "bool TQApplication::isSessionRestored () const"
 Returns TRUE if the application has been restored from an earlier session; otherwise returns FALSE.
 .PP
 See also sessionId(), commitData(), and saveState().
-.SH "void QApplication::lastWindowClosed ()\fC [signal]\fR"
+.SH "void TQApplication::lastWindowClosed ()\fC [signal]\fR"
 This signal is emitted when the user has closed the last top level window.
 .PP
 The signal is very useful when your application has many top level widgets but no main widget. You can then connect it to the quit() slot.
@@ -976,7 +976,7 @@ See also mainWidget(), topLevelWidgets(), TQWidget::isTopLevel, and TQWidget::cl
 .PP
 Examples:
 .)l addressbook/main.cpp, extension/main.cpp, helpviewer/main.cpp, mdi/main.cpp, network/archivesearch/main.cpp, qwerty/main.cpp, and regexptester/main.cpp.
-.SH "TQStringList QApplication::libraryPaths ()\fC [static]\fR"
+.SH "TQStringList TQApplication::libraryPaths ()\fC [static]\fR"
 Returns a list of paths that the application will search when dynamically loading libraries. The installation directory for plugins is the only entry if no paths have been set. The default installation directory for plugins is \fCINSTALL/plugins\fR, where \fCINSTALL\fR is the directory where TQt was installed. The directory of the application executable (NOT the working directory) is also added to the plugin paths.
 .PP
 If you want to iterate over the list, you should iterate over a copy, e.g.
@@ -1000,33 +1000,33 @@ If you want to iterate over the list, you should iterate over a copy, e.g.
 See the plugins documentation for a description of how the library paths are used.
 .PP
 See also setLibraryPaths(), addLibraryPath(), removeLibraryPath(), and TQLibrary.
-.SH "void QApplication::lock ()"
+.SH "void TQApplication::lock ()"
 Lock the TQt Library Mutex. If another thread has already locked the mutex, the calling thread will block until the other thread has unlocked the mutex.
 .PP
 See also unlock(), locked(), and Thread Support in Qt.
-.SH "bool QApplication::locked ()"
+.SH "bool TQApplication::locked ()"
 Returns TRUE if the TQt Library Mutex is locked by a different thread; otherwise returns FALSE.
 .PP
 \fBWarning:\fR Due to different implementations of recursive mutexes on the supported platforms, calling this function from the same thread that previously locked the mutex will give undefined results.
 .PP
 See also lock(), unlock(), and Thread Support in Qt.
-.SH "int QApplication::loopLevel () const"
+.SH "int TQApplication::loopLevel () const"
 \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
 .PP
 Returns the current loop level.
 .PP
-Use QApplication::eventLoop()->loopLevel() instead.
-.SH "bool QApplication::macEventFilter ( EventHandlerCallRef, EventRef )\fC [virtual]\fR"
+Use TQApplication::eventLoop()->loopLevel() instead.
+.SH "bool TQApplication::macEventFilter ( EventHandlerCallRef, EventRef )\fC [virtual]\fR"
 This virtual function is only implemented under Macintosh.
 .PP
-If you create an application that inherits QApplication and reimplement this function, you get direct access to all Carbon Events that are received from the MacOS.
+If you create an application that inherits TQApplication and reimplement this function, you get direct access to all Carbon Events that are received from the MacOS.
 .PP
 Return TRUE if you want to stop the event from being processed. Return FALSE for normal event dispatching.
-.SH "TQWidget * QApplication::mainWidget () const"
+.SH "TQWidget * TQApplication::mainWidget () const"
 Returns the main application widget, or 0 if there is no main widget.
 .PP
 See also setMainWidget().
-.SH "bool QApplication::notify ( TQObject * receiver, TQEvent * e )\fC [virtual]\fR"
+.SH "bool TQApplication::notify ( TQObject * receiver, TQEvent * e )\fC [virtual]\fR"
 Sends event \fIe\fR to \fIreceiver\fR: \fIreceiver\fR->event(\fIe\fR). Returns the value that is returned from the receiver's event handler.
 .PP
 For certain types of events (e.g. mouse and key events), the event will be propagated to the receiver's parent and so on up to the top-level object if the receiver is not interested in the event (i.e., it returns FALSE).
@@ -1048,13 +1048,13 @@ Installing an event filter on the object. Such an event filter gets all the even
 Reimplementing paintEvent(), mousePressEvent() and so on. This is the commonest, easiest and least powerful way.
 .PP
 See also TQObject::event() and installEventFilter().
-.SH "TQCursor * QApplication::overrideCursor ()\fC [static]\fR"
+.SH "TQCursor * TQApplication::overrideCursor ()\fC [static]\fR"
 Returns the active application override cursor.
 .PP
 This function returns 0 if no application cursor has been defined (i.e. the internal cursor stack is empty).
 .PP
 See also setOverrideCursor() and restoreOverrideCursor().
-.SH "TQPalette QApplication::palette ( const TQWidget * w = 0 )\fC [static]\fR"
+.SH "TQPalette TQApplication::palette ( const TQWidget * w = 0 )\fC [static]\fR"
 Returns the application palette.
 .PP
 If a widget is passed in \fIw\fR, the default palette for the widget's class is returned. This may or may not be the application palette. In most cases there isn't a special palette for certain types of widgets, but one notable exception is the popup menu under Windows, if the user has defined a special background color for menus in the display settings.
@@ -1063,7 +1063,7 @@ See also setPalette() and TQWidget::palette.
 .PP
 Examples:
 .)l desktop/desktop.cpp, themes/metal.cpp, and themes/wood.cpp.
-.SH "void QApplication::polish ( TQWidget * w )\fC [virtual]\fR"
+.SH "void TQApplication::polish ( TQWidget * w )\fC [virtual]\fR"
 Initialization of the appearance of the widget \fIw\fR \fIbefore\fR it is first shown.
 .PP
 Usually widgets call this automatically when they are polished. It may be used to do some style-based central customization of widgets.
@@ -1071,7 +1071,7 @@ Usually widgets call this automatically when they are polished. It may be used t
 Note that you are not limited to the public functions of TQWidget. Instead, based on meta information like TQObject::className() you are able to customize any kind of widget.
 .PP
 See also TQStyle::polish(), TQWidget::polish(), setPalette(), and setFont().
-.SH "void QApplication::postEvent ( TQObject * receiver, TQEvent * event )\fC [static]\fR"
+.SH "void TQApplication::postEvent ( TQObject * receiver, TQEvent * event )\fC [static]\fR"
 \fBNote:\fR This function is thread-safe when TQt is built withthread support.</p> Adds the event \fIevent\fR with the object \fIreceiver\fR as the receiver of the event, to an event queue and returns immediately.
 .PP
 The event must be allocated on the heap since the post event queue will take ownership of the event and delete it once it has been posted.
@@ -1079,7 +1079,7 @@ The event must be allocated on the heap since the post event queue will take own
 When control returns to the main event loop, all events that are stored in the queue will be sent using the notify() function.
 .PP
 See also sendEvent() and notify().
-.SH "void QApplication::processEvents ()"
+.SH "void TQApplication::processEvents ()"
 Processes pending events, for 3 seconds or until there are no more events to process, whichever is shorter.
 .PP
 You can call this function occasionally when your program is busy performing a long operation (e.g. copying a file).
@@ -1088,7 +1088,7 @@ See also exec(), TQTimer, and TQEventLoop::processEvents().
 .PP
 Examples:
 .)l fileiconview/tqfileiconview.cpp and network/ftpclient/main.cpp.
-.SH "void QApplication::processEvents ( int maxtime )"
+.SH "void TQApplication::processEvents ( int maxtime )"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
 Processes pending events for \fImaxtime\fR milliseconds or until there are no more events to process, whichever is shorter.
@@ -1096,7 +1096,7 @@ Processes pending events for \fImaxtime\fR milliseconds or until there are no mo
 You can call this function occasionally when you program is busy doing a long operation (e.g. copying a file).
 .PP
 See also exec(), TQTimer, and TQEventLoop::processEvents().
-.SH "void QApplication::processOneEvent ()"
+.SH "void TQApplication::processOneEvent ()"
 \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
 .PP
 Waits for an event to occur, processes it, then returns.
@@ -1106,8 +1106,8 @@ This function is useful for adapting TQt to situations where the event processin
 Using this function in new applications may be an indication of design problems.
 .PP
 See also processEvents(), exec(), and TQTimer.
-.SH "void QApplication::quit ()\fC [slot]\fR"
-Tells the application to exit with return code 0 (success). Equivalent to calling QApplication::exit( 0 ).
+.SH "void TQApplication::quit ()\fC [slot]\fR"
+Tells the application to exit with return code 0 (success). Equivalent to calling TQApplication::exit( 0 ).
 .PP
 It's common to connect the lastWindowClosed() signal to quit(), and you also often connect e.g. TQButton::clicked() or signals in TQAction, TQPopupMenu or TQMenuBar to it.
 .PP
@@ -1125,21 +1125,21 @@ See also exit(), aboutToQuit(), lastWindowClosed(), and TQAction.
 .PP
 Examples:
 .)l addressbook/main.cpp, mdi/main.cpp, network/archivesearch/main.cpp, regexptester/main.cpp, t2/main.cpp, t4/main.cpp, and t6/main.cpp.
-.SH "void QApplication::removeLibraryPath ( const TQString & path )\fC [static]\fR"
+.SH "void TQApplication::removeLibraryPath ( const TQString & path )\fC [static]\fR"
 Removes \fIpath\fR from the library path list. If \fIpath\fR is empty or not in the path list, the list is not changed.
 .PP
 See also addLibraryPath(), libraryPaths(), and setLibraryPaths().
-.SH "void QApplication::removePostedEvents ( TQObject * receiver )\fC [static]\fR"
+.SH "void TQApplication::removePostedEvents ( TQObject * receiver )\fC [static]\fR"
 \fBNote:\fR This function is thread-safe when TQt is built withthread support.</p> Removes all events posted using postEvent() for \fIreceiver\fR.
 .PP
 The events are \fInot\fR dispatched, instead they are removed from the queue. You should never need to call this function. If you do call it, be aware that killing events may cause \fIreceiver\fR to break one or more invariants.
-.SH "void QApplication::removeTranslator ( TQTranslator * mf )"
+.SH "void TQApplication::removeTranslator ( TQTranslator * mf )"
 Removes the message file \fImf\fR from the list of message files used by this application. (It does not delete the message file from the file system.)
 .PP
 See also installTranslator(), translate(), and TQObject::tr().
 .PP
 Example: i18n/main.cpp.
-.SH "void QApplication::restoreOverrideCursor ()\fC [static]\fR"
+.SH "void TQApplication::restoreOverrideCursor ()\fC [static]\fR"
 Undoes the last setOverrideCursor().
 .PP
 If setOverrideCursor() has been called twice, calling restoreOverrideCursor() will activate the first cursor set. Calling this function a second time restores the original widgets' cursors.
@@ -1148,11 +1148,11 @@ See also setOverrideCursor() and overrideCursor().
 .PP
 Examples:
 .)l distributor/distributor.ui.h, network/archivesearch/archivedialog.ui.h, network/ftpclient/ftpmainwindow.ui.h, and showimg/showimg.cpp.
-.SH "bool QApplication::reverseLayout ()\fC [static]\fR"
+.SH "bool TQApplication::reverseLayout ()\fC [static]\fR"
 Returns TRUE if all dialogs and widgets will be laid out in a mirrored (right to left) fashion. Returns FALSE if dialogs and widgets will be laid out left to right.
 .PP
 See also setReverseLayout().
-.SH "void QApplication::saveState ( TQSessionManager & sm )\fC [virtual]\fR"
+.SH "void TQApplication::saveState ( TQSessionManager & sm )\fC [virtual]\fR"
 This function deals with session management. It is invoked when the session manager wants the application to preserve its state for a future session.
 .PP
 For example, a text editor would create a temporary file that includes the current contents of its edit buffers, the location of the cursor and other aspects of the current editing session.
@@ -1162,7 +1162,7 @@ Note that you should never exit the application within this function. Instead, t
 \fBWarning:\fR Within this function, no user interaction is possible, \fIunless\fR you ask the session manager \fIsm\fR for explicit permission. See TQSessionManager::allowsInteraction() and TQSessionManager::allowsErrorInteraction() for details.
 .PP
 See also isSessionRestored(), sessionId(), commitData(), and the Session Management overview.
-.SH "bool QApplication::sendEvent ( TQObject * receiver, TQEvent * event )\fC [static]\fR"
+.SH "bool TQApplication::sendEvent ( TQObject * receiver, TQEvent * event )\fC [static]\fR"
 Sends event \fIevent\fR directly to receiver \fIreceiver\fR, using the notify() function. Returns the value that was returned from the event handler.
 .PP
 The event is \fInot\fR deleted when the event has been sent. The normal approach is to create the event on the stack, e.g.
@@ -1171,7 +1171,7 @@ The event is \fInot\fR deleted when the event has been sent. The normal approach
 .br
     TQMouseEvent me( TQEvent::MouseButtonPress, pos, 0, 0 );
 .br
-    QApplication::sendEvent( mainWindow, &me );
+    TQApplication::sendEvent( mainWindow, &me );
 .br
 .fi
 If you create the event on the heap you must delete it.
@@ -1179,17 +1179,17 @@ If you create the event on the heap you must delete it.
 See also postEvent() and notify().
 .PP
 Example: popup/popup.cpp.
-.SH "void QApplication::sendPostedEvents ( TQObject * receiver, int event_type )\fC [static]\fR"
-Immediately dispatches all events which have been previously queued with QApplication::postEvent() and which are for the object \fIreceiver\fR and have the event type \fIevent_type\fR.
+.SH "void TQApplication::sendPostedEvents ( TQObject * receiver, int event_type )\fC [static]\fR"
+Immediately dispatches all events which have been previously queued with TQApplication::postEvent() and which are for the object \fIreceiver\fR and have the event type \fIevent_type\fR.
 .PP
 Note that events from the window system are \fInot\fR dispatched by this function, but by processEvents().
 .PP
 If \fIreceiver\fR is null, the events of \fIevent_type\fR are sent for all objects. If \fIevent_type\fR is 0, all the events are sent for \fIreceiver\fR.
-.SH "void QApplication::sendPostedEvents ()\fC [static]\fR"
+.SH "void TQApplication::sendPostedEvents ()\fC [static]\fR"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
 Dispatches all posted events, i.e. empties the event queue.
-.SH "TQString QApplication::sessionId () const"
+.SH "TQString TQApplication::sessionId () const"
 Returns the current session's identifier.
 .PP
 If the application has been restored from an earlier session, this identifier is the same as it was in that previous session.
@@ -1197,7 +1197,7 @@ If the application has been restored from an earlier session, this identifier is
 The session identifier is guaranteed to be unique both for different applications and for different instances of the same application.
 .PP
 See also isSessionRestored(), sessionKey(), commitData(), and saveState().
-.SH "TQString QApplication::sessionKey () const"
+.SH "TQString TQApplication::sessionKey () const"
 Returns the session key in the current session.
 .PP
 If the application has been restored from an earlier session, this key is the same as it was when the previous session ended.
@@ -1205,20 +1205,20 @@ If the application has been restored from an earlier session, this key is the sa
 The session key changes with every call of commitData() or saveState().
 .PP
 See also isSessionRestored(), sessionId(), commitData(), and saveState().
-.SH "void QApplication::setColorSpec ( int spec )\fC [static]\fR"
+.SH "void TQApplication::setColorSpec ( int spec )\fC [static]\fR"
 Sets the color specification for the application to \fIspec\fR.
 .PP
 The color specification controls how the application allocates colors when run on a display with a limited amount of colors, e.g. 8 bit / 256 color displays.
 .PP
-The color specification must be set before you create the QApplication object.
+The color specification must be set before you create the TQApplication object.
 .PP
 The options are:
 .TP
-QApplication::NormalColor. This is the default color allocation strategy. Use this option if your application uses buttons, menus, texts and pixmaps with few colors. With this option, the application uses system global colors. This works fine for most applications under X11, but on Windows machines it may cause dithering of non-standard colors.
+TQApplication::NormalColor. This is the default color allocation strategy. Use this option if your application uses buttons, menus, texts and pixmaps with few colors. With this option, the application uses system global colors. This works fine for most applications under X11, but on Windows machines it may cause dithering of non-standard colors.
 .TP
-QApplication::CustomColor. Use this option if your application needs a small number of custom colors. On X11, this option is the same as NormalColor. On Windows, TQt creates a Windows palette, and allocates colors to it on demand.
+TQApplication::CustomColor. Use this option if your application needs a small number of custom colors. On X11, this option is the same as NormalColor. On Windows, TQt creates a Windows palette, and allocates colors to it on demand.
 .TP
-QApplication::ManyColor. Use this option if your application is very color hungry (e.g. it requires thousands of colors). Under X11 the effect is:
+TQApplication::ManyColor. Use this option if your application is very color hungry (e.g. it requires thousands of colors). Under X11 the effect is:
 .TP
 For 256-color displays which have at best a 256 color true color visual, the default visual is used, and colors are allocated from a color cube. The color cube is the 6x6x6 (216 color) "Web palette"<sup>*</sup>, but the number of colors can be changed by the \fI-ncols\fR option. The user can force the application to use the true color visual with the -visual option.
 .TP
@@ -1234,9 +1234,9 @@ Example:
 .br
   {
 .br
-      QApplication::setColorSpec( QApplication::ManyColor );
+      TQApplication::setColorSpec( TQApplication::ManyColor );
 .br
-      QApplication a( argc, argv );
+      TQApplication a( argc, argv );
 .br
       ...
 .br
@@ -1246,7 +1246,7 @@ Example:
 .PP
 TQColor provides more functionality for controlling color allocation and freeing up certain colors. See TQColor::enterAllocContext() for more information.
 .PP
-To check what mode you end up with, call TQColor::numBitPlanes() once the QApplication object exists. A value greater than 8 (typically 16, 24 or 32) means true color.
+To check what mode you end up with, call TQColor::numBitPlanes() once the TQApplication object exists. A value greater than 8 (typically 16, 24 or 32) means true color.
 .PP
 <sup>*</sup> The color cube used by TQt has 216 colors whose red, green, and blue components always have one of the following values: 0x00, 0x33, 0x66, 0x99, 0xCC, or 0xFF.
 .PP
@@ -1254,28 +1254,28 @@ See also colorSpec(), TQColor::numBitPlanes(), and TQColor::enterAllocContext().
 .PP
 Examples:
 .)l helpviewer/main.cpp, opengl/main.cpp, showimg/main.cpp, t9/main.cpp, tetrax/tetrax.cpp, tetrix/tetrix.cpp, and themes/main.cpp.
-.SH "void QApplication::setCursorFlashTime ( int msecs )\fC [static]\fR"
+.SH "void TQApplication::setCursorFlashTime ( int msecs )\fC [static]\fR"
 Sets the text cursor's flash (blink) time to \fImsecs\fR milliseconds. The flash time is the time required to display, invert and restore the caret display. Usually the text cursor is displayed for \fImsecs/2\fR milliseconds, then hidden for \fImsecs/2\fR milliseconds, but this may vary.
 .PP
 Note that on Microsoft Windows, calling this function sets the cursor flash time for all windows.
 .PP
 See also cursorFlashTime().
-.SH "void QApplication::setDefaultCodec ( TQTextCodec * codec )"
+.SH "void TQApplication::setDefaultCodec ( TQTextCodec * codec )"
 \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
 .PP
 This is the same as TQTextCodec::setCodecForTr().
-.SH "void QApplication::setDesktopSettingsAware ( bool on )\fC [static]\fR"
+.SH "void TQApplication::setDesktopSettingsAware ( bool on )\fC [static]\fR"
 By default, TQt will try to use the current standard colors, fonts etc., from the underlying window system's desktop settings, and use them for all relevant widgets. This behavior can be switched off by calling this function with \fIon\fR set to FALSE.
 .PP
-This static function must be called before creating the QApplication object, like this:
+This static function must be called before creating the TQApplication object, like this:
 .PP
 .nf
 .br
   int main( int argc, char** argv ) {
 .br
-    QApplication::setDesktopSettingsAware( FALSE ); // I know better than the user
+    TQApplication::setDesktopSettingsAware( FALSE ); // I know better than the user
 .br
-    QApplication myApp( argc, argv ); // Use default fonts & colors
+    TQApplication myApp( argc, argv ); // Use default fonts & colors
 .br
     ...
 .br
@@ -1284,19 +1284,19 @@ This static function must be called before creating the QApplication object, lik
 .fi
 .PP
 See also desktopSettingsAware().
-.SH "void QApplication::setDoubleClickInterval ( int ms )\fC [static]\fR"
+.SH "void TQApplication::setDoubleClickInterval ( int ms )\fC [static]\fR"
 Sets the time limit that distinguishes a double click from two consecutive mouse clicks to \fIms\fR milliseconds.
 .PP
 Note that on Microsoft Windows, calling this function sets the double click interval for all windows.
 .PP
 See also doubleClickInterval().
-.SH "void QApplication::setEffectEnabled ( TQt::UIEffect effect, bool enable = TRUE )\fC [static]\fR"
+.SH "void TQApplication::setEffectEnabled ( TQt::UIEffect effect, bool enable = TRUE )\fC [static]\fR"
 Enables the UI effect \fIeffect\fR if \fIenable\fR is TRUE, otherwise the effect will not be used.
 .PP
 Note: All effects are disabled on screens running at less than 16-bit color depth.
 .PP
 See also isEffectEnabled(), TQt::UIEffect, and setDesktopSettingsAware().
-.SH "void QApplication::setFont ( const TQFont & font, bool informWidgets = FALSE, const char * className = 0 )\fC [static]\fR"
+.SH "void TQApplication::setFont ( const TQFont & font, bool informWidgets = FALSE, const char * className = 0 )\fC [static]\fR"
 Changes the default application font to \fIfont\fR. If \fIinformWidgets\fR is TRUE, then existing widgets are informed about the change and may adjust themselves to the new application setting. If \fIinformWidgets\fR is FALSE, the change only affects newly created widgets. If \fIclassName\fR is passed, the change applies only to classes that inherit \fIclassName\fR (as reported by TQObject::inherits()).
 .PP
 On application start-up, the default font depends on the window system. It can vary depending on both the window system version and the locale. This function lets you override the default font; but overriding may be a bad idea because, for example, some locales need extra-large fonts to support their special characters.
@@ -1305,7 +1305,7 @@ See also font(), fontMetrics(), and TQWidget::font.
 .PP
 Examples:
 .)l desktop/desktop.cpp, themes/metal.cpp, and themes/themes.cpp.
-.SH "void QApplication::setGlobalMouseTracking ( bool enable )\fC [static]\fR"
+.SH "void TQApplication::setGlobalMouseTracking ( bool enable )\fC [static]\fR"
 Enables global mouse tracking if \fIenable\fR is TRUE, or disables it if \fIenable\fR is FALSE.
 .PP
 Enabling global mouse tracking makes it possible for widget event filters or application event filters to get all mouse move events, even when no button is depressed. This is useful for special GUI elements, e.g. tooltips.
@@ -1318,22 +1318,22 @@ This function uses an internal counter. Each setGlobalMouseTracking(TRUE) must h
 .br
         // at this point global mouse tracking is off
 .br
-        QApplication::setGlobalMouseTracking( TRUE );
+        TQApplication::setGlobalMouseTracking( TRUE );
 .br
-        QApplication::setGlobalMouseTracking( TRUE );
+        TQApplication::setGlobalMouseTracking( TRUE );
 .br
-        QApplication::setGlobalMouseTracking( FALSE );
+        TQApplication::setGlobalMouseTracking( FALSE );
 .br
         // at this point it's still on
 .br
-        QApplication::setGlobalMouseTracking( FALSE );
+        TQApplication::setGlobalMouseTracking( FALSE );
 .br
         // but now it's off
 .br
 .fi
 .PP
 See also hasGlobalMouseTracking() and TQWidget::mouseTracking.
-.SH "void QApplication::setGlobalStrut ( const TQSize & strut )\fC [static]\fR"
+.SH "void TQApplication::setGlobalStrut ( const TQSize & strut )\fC [static]\fR"
 Sets the application's global strut to \fIstrut\fR.
 .PP
 The strut is a size object whose dimensions are the minimum that any GUI element that the user can interact with should have. For example no button should be resized to be smaller than the global strut size.
@@ -1348,21 +1348,21 @@ Example:
 .br
   {
 .br
-      return TQSize( 80, 25 ).expandedTo( QApplication::globalStrut() );
+      return TQSize( 80, 25 ).expandedTo( TQApplication::globalStrut() );
 .br
   }
 .br
 .fi
 .PP
 See also globalStrut().
-.SH "void QApplication::setLibraryPaths ( const TQStringList & paths )\fC [static]\fR"
+.SH "void TQApplication::setLibraryPaths ( const TQStringList & paths )\fC [static]\fR"
 Sets the list of directories to search when loading libraries to \fIpaths\fR. All existing paths will be deleted and the path list will consist of the paths given in \fIpaths\fR.
 .PP
 See also libraryPaths(), addLibraryPath(), removeLibraryPath(), and TQLibrary.
-.SH "void QApplication::setMainWidget ( TQWidget * mainWidget )\fC [virtual]\fR"
+.SH "void TQApplication::setMainWidget ( TQWidget * mainWidget )\fC [virtual]\fR"
 Sets the application's main widget to \fImainWidget\fR.
 .PP
-In most respects the main widget is like any other widget, except that if it is closed, the application exits. Note that QApplication does \fInot\fR take ownership of the \fImainWidget\fR, so if you create your main widget on the heap you must delete it yourself.
+In most respects the main widget is like any other widget, except that if it is closed, the application exits. Note that TQApplication does \fInot\fR take ownership of the \fImainWidget\fR, so if you create your main widget on the heap you must delete it yourself.
 .PP
 You need not have a main widget; connecting lastWindowClosed() to quit() is an alternative.
 .PP
@@ -1372,7 +1372,7 @@ See also mainWidget(), exec(), and quit().
 .PP
 Examples:
 .)l chart/main.cpp, helpsystem/main.cpp, life/main.cpp, network/ftpclient/main.cpp, opengl/main.cpp, t1/main.cpp, and t4/main.cpp.
-.SH "void QApplication::setOverrideCursor ( const TQCursor & cursor, bool replace = FALSE )\fC [static]\fR"
+.SH "void TQApplication::setOverrideCursor ( const TQCursor & cursor, bool replace = FALSE )\fC [static]\fR"
 Sets the application override cursor to \fIcursor\fR.
 .PP
 Application override cursors are intended for showing the user that the application is in a special state, for example during an operation that might take some time.
@@ -1387,11 +1387,11 @@ Example:
 .PP
 .nf
 .br
-        QApplication::setOverrideCursor( TQCursor(TQt::WaitCursor) );
+        TQApplication::setOverrideCursor( TQCursor(TQt::WaitCursor) );
 .br
         calculateHugeMandelbrot();              // lunch time...
 .br
-        QApplication::restoreOverrideCursor();
+        TQApplication::restoreOverrideCursor();
 .br
 .fi
 .PP
@@ -1399,7 +1399,7 @@ See also overrideCursor(), restoreOverrideCursor(), and TQWidget::cursor.
 .PP
 Examples:
 .)l distributor/distributor.ui.h, network/archivesearch/archivedialog.ui.h, network/ftpclient/ftpmainwindow.ui.h, and showimg/showimg.cpp.
-.SH "void QApplication::setPalette ( const TQPalette & palette, bool informWidgets = FALSE, const char * className = 0 )\fC [static]\fR"
+.SH "void TQApplication::setPalette ( const TQPalette & palette, bool informWidgets = FALSE, const char * className = 0 )\fC [static]\fR"
 Changes the default application palette to \fIpalette\fR. If \fIinformWidgets\fR is TRUE, then existing widgets are informed about the change and may adjust themselves to the new application setting. If \fIinformWidgets\fR is FALSE, the change only affects newly created widgets.
 .PP
 If \fIclassName\fR is passed, the change applies only to widgets that inherit \fIclassName\fR (as reported by TQObject::inherits()). If \fIclassName\fR is left 0, the change affects all widgets, thus overriding any previously set class specific palettes.
@@ -1410,28 +1410,28 @@ See also TQWidget::palette, palette(), and TQStyle::polish().
 .PP
 Examples:
 .)l i18n/main.cpp, themes/metal.cpp, themes/themes.cpp, and themes/wood.cpp.
-.SH "void QApplication::setReverseLayout ( bool b )\fC [static]\fR"
+.SH "void TQApplication::setReverseLayout ( bool b )\fC [static]\fR"
 If \fIb\fR is TRUE, all dialogs and widgets will be laid out in a mirrored fashion, as required by right to left languages such as Arabic and Hebrew. If \fIb\fR is FALSE, dialogs and widgets are laid out left to right.
 .PP
 Changing this flag in runtime does not cause a relayout of already instantiated widgets.
 .PP
 See also reverseLayout().
-.SH "void QApplication::setStartDragDistance ( int l )\fC [static]\fR"
+.SH "void TQApplication::setStartDragDistance ( int l )\fC [static]\fR"
 Sets the distance after which a drag should start to \fIl\fR pixels.
 .PP
 See also startDragDistance().
-.SH "void QApplication::setStartDragTime ( int ms )\fC [static]\fR"
+.SH "void TQApplication::setStartDragTime ( int ms )\fC [static]\fR"
 Sets the time after which a drag should start to \fIms\fR ms.
 .PP
 See also startDragTime().
-.SH "void QApplication::setStyle ( TQStyle * style )\fC [static]\fR"
-Sets the application's GUI style to \fIstyle\fR. Ownership of the style object is transferred to QApplication, so QApplication will delete the style object on application exit or when a new style is set.
+.SH "void TQApplication::setStyle ( TQStyle * style )\fC [static]\fR"
+Sets the application's GUI style to \fIstyle\fR. Ownership of the style object is transferred to TQApplication, so TQApplication will delete the style object on application exit or when a new style is set.
 .PP
 Example usage:
 .PP
 .nf
 .br
-    QApplication::setStyle( new TQWindowsStyle );
+    TQApplication::setStyle( new TQWindowsStyle );
 .br
 .fi
 .PP
@@ -1440,23 +1440,23 @@ When switching application styles, the color palette is set back to the initial
 See also style(), TQStyle, setPalette(), and desktopSettingsAware().
 .PP
 Example: themes/themes.cpp.
-.SH "TQStyle * QApplication::setStyle ( const TQString & style )\fC [static]\fR"
+.SH "TQStyle * TQApplication::setStyle ( const TQString & style )\fC [static]\fR"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
 Requests a TQStyle object for \fIstyle\fR from the TQStyleFactory.
 .PP
 The string must be one of the TQStyleFactory::keys(), typically one of "windows", "motif", "cde", "motifplus", "platinum", "sgi" and" compact". Depending on the platform, "windowsxp", "aqua" or" macintosh" may be available.
 .PP
-A later call to the QApplication constructor will override the requested style when a "-style" option is passed in as a commandline parameter.
+A later call to the TQApplication constructor will override the requested style when a "-style" option is passed in as a commandline parameter.
 .PP
 Returns 0 if an unknown \fIstyle\fR is passed, otherwise the TQStyle object returned is set as the application's GUI style.
-.SH "void QApplication::setWheelScrollLines ( int n )\fC [static]\fR"
+.SH "void TQApplication::setWheelScrollLines ( int n )\fC [static]\fR"
 Sets the number of lines to scroll when the mouse wheel is rotated to \fIn\fR.
 .PP
 If this number exceeds the number of visible lines in a certain widget, the widget should interpret the scroll operation as a single page up / page down operation instead.
 .PP
 See also wheelScrollLines().
-.SH "void QApplication::setWinStyleHighlightColor ( const TQColor & c )\fC [static]\fR"
+.SH "void TQApplication::setWinStyleHighlightColor ( const TQColor & c )\fC [static]\fR"
 \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
 .PP
 Sets the color used to mark selections in windows style for all widgets in the application. Will repaint all widgets if the color is changed.
@@ -1464,7 +1464,7 @@ Sets the color used to mark selections in windows style for all widgets in the a
 The default color is \fCdarkBlue\fR.
 .PP
 See also winStyleHighlightColor().
-.SH "int QApplication::startDragDistance ()\fC [static]\fR"
+.SH "int TQApplication::startDragDistance ()\fC [static]\fR"
 If you support drag and drop in you application and a drag should start after a mouse click and after moving the mouse a certain distance, you should use the value which this method returns as the distance.
 .PP
 For example, if the mouse position of the click is stored in \fCstartPos\fR and the current position (e.g. in the mouse move event) is \fCcurrPos\fR, you can find out if a drag should be started with code like this:
@@ -1473,7 +1473,7 @@ For example, if the mouse position of the click is stored in \fCstartPos\fR and
 .br
   if ( ( startPos - currPos ).manhattanLength() >
 .br
-       QApplication::startDragDistance() )
+       TQApplication::startDragDistance() )
 .br
     startTheDrag();
 .br
@@ -1484,7 +1484,7 @@ Qt uses this value internally, e.g. in TQFileDialog.
 The default value is 4 pixels.
 .PP
 See also setStartDragDistance(), startDragTime(), and TQPoint::manhattanLength().
-.SH "int QApplication::startDragTime ()\fC [static]\fR"
+.SH "int TQApplication::startDragTime ()\fC [static]\fR"
 If you support drag and drop in you application and a drag should start after a mouse click and after a certain time elapsed, you should use the value which this method returns as the delay (in ms).
 .PP
 Qt also uses this delay internally, e.g. in TQTextEdit and TQLineEdit, for starting a drag.
@@ -1492,19 +1492,19 @@ Qt also uses this delay internally, e.g. in TQTextEdit and TQLineEdit, for start
 The default value is 500 ms.
 .PP
 See also setStartDragTime() and startDragDistance().
-.SH "bool QApplication::startingUp ()\fC [static]\fR"
+.SH "bool TQApplication::startingUp ()\fC [static]\fR"
 Returns TRUE if an application object has not been created yet; otherwise returns FALSE.
 .PP
 See also closingDown().
-.SH "TQStyle & QApplication::style ()\fC [static]\fR"
+.SH "TQStyle & TQApplication::style ()\fC [static]\fR"
 Returns the application's style object.
 .PP
 See also setStyle() and TQStyle.
-.SH "void QApplication::syncX ()\fC [static]\fR"
+.SH "void TQApplication::syncX ()\fC [static]\fR"
 Synchronizes with the X server in the X11 implementation. This normally takes some time. Does nothing on other platforms.
 .PP
 See also flushX().
-.SH "TQWidgetList * QApplication::topLevelWidgets ()\fC [static]\fR"
+.SH "TQWidgetList * TQApplication::topLevelWidgets ()\fC [static]\fR"
 Returns a list of the top level widgets in the application.
 .PP
 The list is created using \fCnew\fR and must be deleted by the caller.
@@ -1519,7 +1519,7 @@ Example:
 .br
     // Show all hidden top level widgets.
 .br
-    TQWidgetList  *list = QApplication::topLevelWidgets();
+    TQWidgetList  *list = TQApplication::topLevelWidgets();
 .br
     TQWidgetListIt it( *list );  // iterate over the widgets
 .br
@@ -1542,7 +1542,7 @@ Example:
 \fBWarning:\fR Delete the list as soon you have finished using it. The widgets in the list may be deleted by someone else at any time.
 .PP
 See also allWidgets(), TQWidget::isTopLevel, TQWidget::visible, and TQPtrList::isEmpty().
-.SH "TQString QApplication::translate ( const char * context, const char * sourceText, const char * comment = 0, Encoding encoding = DefaultCodec ) const"
+.SH "TQString TQApplication::translate ( const char * context, const char * sourceText, const char * comment = 0, Encoding encoding = DefaultCodec ) const"
 \fBNote:\fR This function is reentrant when TQt is built with thread support.</p> Returns the translation text for \fIsourceText\fR, by querying the installed messages files. The message files are searched from the most recently installed message file back to the first installed message file.
 .PP
 TQObject::tr() and TQObject::trUtf8() provide this functionality more conveniently.
@@ -1560,27 +1560,27 @@ This function is not virtual. You can use alternative translation techniques by
 \fBWarning:\fR This method is reentrant only if all translators are installed \fIbefore\fR calling this method. Installing or removing translators while performing translations is not supported. Doing so will most likely result in crashes or other undesirable behavior.
 .PP
 See also TQObject::tr(), installTranslator(), and defaultCodec().
-.SH "bool QApplication::tryLock ()"
+.SH "bool TQApplication::tryLock ()"
 Attempts to lock the TQt Library Mutex, and returns immediately. If the lock was obtained, this function returns TRUE. If another thread has locked the mutex, this function returns FALSE, instead of waiting for the lock to become available.
 .PP
 The mutex must be unlocked with unlock() before another thread can successfully lock it.
 .PP
 See also lock(), unlock(), and Thread Support in Qt.
-.SH "Type QApplication::type () const"
+.SH "Type TQApplication::type () const"
 Returns the type of application, Tty, GuiClient or GuiServer.
-.SH "void QApplication::unlock ( bool wakeUpGui = TRUE )"
-Unlock the TQt Library Mutex. If \fIwakeUpGui\fR is TRUE (the default), then the GUI thread will be woken with QApplication::wakeUpGuiThread().
+.SH "void TQApplication::unlock ( bool wakeUpGui = TRUE )"
+Unlock the TQt Library Mutex. If \fIwakeUpGui\fR is TRUE (the default), then the GUI thread will be woken with TQApplication::wakeUpGuiThread().
 .PP
 See also lock(), locked(), and Thread Support in Qt.
-.SH "void QApplication::wakeUpGuiThread ()"
+.SH "void TQApplication::wakeUpGuiThread ()"
 Wakes up the GUI thread.
 .PP
 See also guiThreadAwake() and Thread Support in Qt.
-.SH "int QApplication::wheelScrollLines ()\fC [static]\fR"
+.SH "int TQApplication::wheelScrollLines ()\fC [static]\fR"
 Returns the number of lines to scroll when the mouse wheel is rotated.
 .PP
 See also setWheelScrollLines().
-.SH "TQWidget * QApplication::widgetAt ( int x, int y, bool child = FALSE )\fC [static]\fR"
+.SH "TQWidget * TQApplication::widgetAt ( int x, int y, bool child = FALSE )\fC [static]\fR"
 Returns a pointer to the widget at global screen position \fI(x, y)\fR, or 0 if there is no TQt widget there.
 .PP
 If \fIchild\fR is FALSE and there is a child widget at position \fI(x, y)\fR, the top-level widget containing it is returned. If \fIchild\fR is TRUE the child widget at position \fI(x, y)\fR is returned.
@@ -1588,35 +1588,35 @@ If \fIchild\fR is FALSE and there is a child widget at position \fI(x, y)\fR, th
 This function is normally rather slow.
 .PP
 See also TQCursor::pos(), TQWidget::grabMouse(), and TQWidget::grabKeyboard().
-.SH "TQWidget * QApplication::widgetAt ( const TQPoint & pos, bool child = FALSE )\fC [static]\fR"
+.SH "TQWidget * TQApplication::widgetAt ( const TQPoint & pos, bool child = FALSE )\fC [static]\fR"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
 Returns a pointer to the widget at global screen position \fIpos\fR, or 0 if there is no TQt widget there.
 .PP
 If \fIchild\fR is FALSE and there is a child widget at position \fIpos\fR, the top-level widget containing it is returned. If \fIchild\fR is TRUE the child widget at position \fIpos\fR is returned.
-.SH "bool QApplication::winEventFilter ( MSG * )\fC [virtual]\fR"
+.SH "bool TQApplication::winEventFilter ( MSG * )\fC [virtual]\fR"
 This virtual function is only implemented under Windows.
 .PP
 The message procedure calls this function for every message received. Reimplement this function if you want to process window messages that are not processed by Qt. If you don't want the event to be processed by Qt, then return TRUE; otherwise return FALSE.
-.SH "void QApplication::winFocus ( TQWidget * widget, bool gotFocus )"
+.SH "void TQApplication::winFocus ( TQWidget * widget, bool gotFocus )"
 This function is available only on Windows.
 .PP
 If \fIgotFocus\fR is TRUE, \fIwidget\fR will become the active window. Otherwise the active window is reset to NULL.
-.SH "const TQColor & QApplication::winStyleHighlightColor ()\fC [static]\fR"
+.SH "const TQColor & TQApplication::winStyleHighlightColor ()\fC [static]\fR"
 \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
 .PP
 Returns the color used to mark selections in windows style.
 .PP
 See also setWinStyleHighlightColor().
-.SH "bool QApplication::x11EventFilter ( XEvent * )\fC [virtual]\fR"
+.SH "bool TQApplication::x11EventFilter ( XEvent * )\fC [virtual]\fR"
 This virtual function is only implemented under X11.
 .PP
-If you create an application that inherits QApplication and reimplement this function, you get direct access to all X events that the are received from the X server.
+If you create an application that inherits TQApplication and reimplement this function, you get direct access to all X events that the are received from the X server.
 .PP
 Return TRUE if you want to stop the event from being processed. Return FALSE for normal event dispatching.
 .PP
 See also x11ProcessEvent().
-.SH "int QApplication::x11ProcessEvent ( XEvent * event )"
+.SH "int TQApplication::x11ProcessEvent ( XEvent * event )"
 This function does the core processing of individual X \fIevent\fRs, normally by dispatching TQt events to the right destination.
 .PP
 It returns 1 if the event was consumed by special handling, 0 if the \fIevent\fR was consumed by normal handling, and -1 if the \fIevent\fR was for an unrecognized widget.
@@ -1688,7 +1688,7 @@ Example:
 .PP
 See also tqWarning() and Debugging.
 .SH "void tqAddPostRoutine ( QtCleanUpFunction p )"
-Adds a global routine that will be called from the QApplication destructor. This function is normally used to add cleanup routines for program-wide functionality.
+Adds a global routine that will be called from the TQApplication destructor. This function is normally used to add cleanup routines for program-wide functionality.
 .PP
 The function given by \fIp\fR should take no arguments and return nothing, like this:
 .PP
@@ -1720,7 +1720,7 @@ The function given by \fIp\fR should take no arguments and return nothing, like
 .br
 .fi
 .PP
-Note that for an application- or module-wide cleanup, tqAddPostRoutine() is often not suitable. People have a tendency to make such modules dynamically loaded, and then unload those modules long before the QApplication destructor is called, for example.
+Note that for an application- or module-wide cleanup, tqAddPostRoutine() is often not suitable. People have a tendency to make such modules dynamically loaded, and then unload those modules long before the TQApplication destructor is called, for example.
 .PP
 For modules and libraries, using a reference-counted initialization manager or Qt' parent-child delete mechanism may be better. Here is an example of a private class which uses the parent-child mechanism to call a cleanup function at the right time:
 .PP
@@ -1828,7 +1828,7 @@ Example:
 .PP
 .nf
 .br
-        #include <ntqapplication.h>
+        #include <tqapplication.h>
 .br
         #include <stdio.h>
 .br
@@ -1870,7 +1870,7 @@ Example:
 .br
             qInstallMsgHandler( myMessageOutput );
 .br
-            QApplication a( argc, argv );
+            TQApplication a( argc, argv );
 .br
             ...
 .br
@@ -1925,7 +1925,7 @@ Under X11, the text is printed to stderr. Under Windows, the text is sent to the
 See also tqDebug(), tqFatal(), qInstallMsgHandler(), and Debugging.
 
 .SH "SEE ALSO"
-.BR http://doc.trolltech.com/ntqapplication.html
+.BR http://doc.trolltech.com/tqapplication.html
 .BR http://www.trolltech.com/faq/tech.html
 .SH COPYRIGHT
 Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com.  See the