Rename ntqapplication, ntqconfig and ntqmodules files to equivalent tq*

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

38 files changed, 322 insertions, 322 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
diff --git a/doc/man/man3/tqchildevent.3qt b/doc/man/man3/tqchildevent.3qt
index 652804899..6f2c6d923 100644
--- a/doc/man/man3/tqchildevent.3qt
+++ b/doc/man/man3/tqchildevent.3qt
@@ -33,7 +33,7 @@ The TQChildEvent class contains event parameters for child object events.
 .PP
 Child events are sent to objects when children are inserted or removed.
 .PP
-A ChildRemoved event is sent immediately, but a ChildInserted event is \fIposted\fR (with QApplication::postEvent()).
+A ChildRemoved event is sent immediately, but a ChildInserted event is \fIposted\fR (with TQApplication::postEvent()).
 .PP
 Note that if a child is removed immediately after it is inserted, the ChildInserted event may be suppressed, but the ChildRemoved event will always be sent. In this case there will be a ChildRemoved event without a corresponding ChildInserted event.
 .PP
diff --git a/doc/man/man3/tqclipboard.3qt b/doc/man/man3/tqclipboard.3qt
index 761819cbd..844594131 100644
--- a/doc/man/man3/tqclipboard.3qt
+++ b/doc/man/man3/tqclipboard.3qt
@@ -110,13 +110,13 @@ The clipboard offers a simple mechanism to copy and paste data between applicati
 .PP
 TQClipboard supports the same data types that TQDragObject does, and uses similar mechanisms. For advanced clipboard usage read the drag-and-drop documentation.
 .PP
-There is a single TQClipboard object in an application, and you can access it using QApplication::clipboard().
+There is a single TQClipboard object in an application, and you can access it using TQApplication::clipboard().
 .PP
 Example:
 .PP
 .nf
 .br
-    TQClipboard *cb = QApplication::clipboard();
+    TQClipboard *cb = TQApplication::clipboard();
 .br
 .br
     // Copy text from the clipboard (paste)
diff --git a/doc/man/man3/tqcloseevent.3qt b/doc/man/man3/tqcloseevent.3qt
index e8d80d362..47f01da1e 100644
--- a/doc/man/man3/tqcloseevent.3qt
+++ b/doc/man/man3/tqcloseevent.3qt
@@ -35,7 +35,7 @@ Close events are sent to widgets that the user wants to close, usually by choosi
 .PP
 Close events contain a flag that indicates whether the receiver wants the widget to be closed or not. When a widget accepts the close event, it is hidden (and destroyed if it was created with the WDestructiveClose flag). If it refuses to accept the close event nothing happens. (Under X11 it is possible that the window manager will forcibly close the window; but at the time of writing we are not aware of any window manager that does this.)
 .PP
-The application's main widget -- QApplication::mainWidget() -- is a special case. When it accepts the close event, TQt leaves the main event loop and the application is immediately terminated (i.e. it returns from the call to QApplication::exec() in the main() function).
+The application's main widget -- TQApplication::mainWidget() -- is a special case. When it accepts the close event, TQt leaves the main event loop and the application is immediately terminated (i.e. it returns from the call to TQApplication::exec() in the main() function).
 .PP
 The event handler TQWidget::closeEvent() receives close events. The default implementation of this event handler accepts the close event. If you do not want your widget to be hidden, or want some special handing, you should reimplement the event handler.
 .PP
@@ -45,11 +45,11 @@ If you want the widget to be deleted when it is closed, create it with the WDest
 .PP
 TQObjects emits the destroyed() signal when they are deleted.
 .PP
-If the last top-level window is closed, the QApplication::lastWindowClosed() signal is emitted.
+If the last top-level window is closed, the TQApplication::lastWindowClosed() signal is emitted.
 .PP
 The isAccepted() function returns TRUE if the event's receiver has agreed to close the widget; call accept() to agree to close the widget and call ignore() if the receiver of this event does not want the widget to be closed.
 .PP
-See also TQWidget::close(), TQWidget::hide(), TQObject::destroyed(), QApplication::setMainWidget(), QApplication::lastWindowClosed(), QApplication::exec(), QApplication::quit(), and Event Classes.
+See also TQWidget::close(), TQWidget::hide(), TQObject::destroyed(), TQApplication::setMainWidget(), TQApplication::lastWindowClosed(), TQApplication::exec(), TQApplication::quit(), and Event Classes.
 .SH MEMBER FUNCTION DOCUMENTATION
 .SH "TQCloseEvent::TQCloseEvent ()"
 Constructs a close event object with the accept parameter flag set to FALSE.
diff --git a/doc/man/man3/tqcolor.3qt b/doc/man/man3/tqcolor.3qt
index 62dd6f426..3d5c89b91 100644
--- a/doc/man/man3/tqcolor.3qt
+++ b/doc/man/man3/tqcolor.3qt
@@ -227,7 +227,7 @@ Here are some examples: Pure red is H=0, S=255, V=255. A dark red, moving slight
 .PP
 Qt returns a hue value of -1 for achromatic colors. If you pass a too-big hue value, TQt forces it into range. Hue 360 or 720 is treated as 0; hue 540 is treated as 180.
 .PP
-See also TQPalette, TQColorGroup, QApplication::setColorSpec(), Color FAQ, Widget Appearance and Style, Graphics Classes, and Image Processing Classes.
+See also TQPalette, TQColorGroup, TQApplication::setColorSpec(), Color FAQ, Widget Appearance and Style, Graphics Classes, and Image Processing Classes.
 .SS "Member Type Documentation"
 .SH "TQColor::Spec"
 The type of color specified, either RGB or HSV, e.g. in the \fCTQColor::TQColor( x, y, z, colorSpec)\fR constructor.
@@ -285,7 +285,7 @@ See also enterAllocContext().
 .SH "int TQColor::blue () const"
 Returns the B (blue) component of the RGB value.
 .SH "void TQColor::cleanup ()\fC [static]\fR"
-Internal clean up required for TQColor. This function is called from the QApplication destructor.
+Internal clean up required for TQColor. This function is called from the TQApplication destructor.
 .PP
 See also initialize().
 .SH "TQStringList TQColor::colorNames ()\fC [static]\fR"
@@ -382,9 +382,9 @@ Calling enterAllocContext() enters an allocation context. The allocation context
 .br
 .fi
 .PP
-You may also want to set the application's color specification. See QApplication::setColorSpec() for more information.
+You may also want to set the application's color specification. See TQApplication::setColorSpec() for more information.
 .PP
-See also leaveAllocContext(), currentAllocContext(), destroyAllocContext(), and QApplication::setColorSpec().
+See also leaveAllocContext(), currentAllocContext(), destroyAllocContext(), and TQApplication::setColorSpec().
 .PP
 Example: showimg/showimg.cpp.
 .SH "void TQColor::getHsv ( int * h, int * s, int * v ) const"
@@ -408,7 +408,7 @@ Returns the G (green) component of the RGB value.
 .PP
 Example: themes/metal.cpp.
 .SH "void TQColor::initialize ()\fC [static]\fR"
-Internal initialization required for TQColor. This function is called from the QApplication constructor.
+Internal initialization required for TQColor. This function is called from the TQApplication constructor.
 .PP
 See also cleanup().
 .SH "bool TQColor::isValid () const"
diff --git a/doc/man/man3/tqcursor.3qt b/doc/man/man3/tqcursor.3qt
index b308c7cbb..e107fe863 100644
--- a/doc/man/man3/tqcursor.3qt
+++ b/doc/man/man3/tqcursor.3qt
@@ -95,7 +95,7 @@ This class is mainly used to create mouse cursors that are associated with parti
 .PP
 Qt has a number of standard cursor shapes, but you can also make custom cursor shapes based on a TQBitmap, a mask and a hotspot.
 .PP
-To associate a cursor with a widget, use TQWidget::setCursor(). To associate a cursor with all widgets (normally for a short period of time), use QApplication::setOverrideCursor().
+To associate a cursor with a widget, use TQWidget::setCursor(). To associate a cursor with all widgets (normally for a short period of time), use TQApplication::setOverrideCursor().
 .PP
 To set a cursor shape use TQCursor::setShape() or use the TQCursor constructor which takes the shape as argument, or you can use one of the predefined cursors defined in the CursorShape enum.
 .PP
@@ -173,7 +173,7 @@ Destroys the cursor.
 .SH "const TQBitmap * TQCursor::bitmap () const"
 Returns the cursor bitmap, or 0 if it is one of the standard cursors.
 .SH "void TQCursor::cleanup ()\fC [static]\fR"
-Internal function that deinitializes the predefined cursors. This function is called from the QApplication destructor.
+Internal function that deinitializes the predefined cursors. This function is called from the TQApplication destructor.
 .PP
 See also initialize().
 .SH "HANDLE TQCursor::handle () const"
@@ -183,7 +183,7 @@ Returns the window system cursor handle.
 .SH "TQPoint TQCursor::hotSpot () const"
 Returns the cursor hot spot, or (0, 0) if it is one of the standard cursors.
 .SH "void TQCursor::initialize ()\fC [static]\fR"
-Internal function that initializes the predefined cursors. This function is called from the QApplication constructor.
+Internal function that initializes the predefined cursors. This function is called from the TQApplication constructor.
 .PP
 See also cleanup().
 .SH "const TQBitmap * TQCursor::mask () const"
diff --git a/doc/man/man3/tqcustomevent.3qt b/doc/man/man3/tqcustomevent.3qt
index a3e3dddaf..77da419d8 100644
--- a/doc/man/man3/tqcustomevent.3qt
+++ b/doc/man/man3/tqcustomevent.3qt
@@ -31,7 +31,7 @@ Inherits TQEvent.
 .SH DESCRIPTION
 The TQCustomEvent class provides support for custom events.
 .PP
-TQCustomEvent is a generic event class for user-defined events. User defined events can be sent to widgets or other TQObject instances using QApplication::postEvent() or QApplication::sendEvent(). Subclasses of TQObject can easily receive custom events by implementing the TQObject::customEvent() event handler function.
+TQCustomEvent is a generic event class for user-defined events. User defined events can be sent to widgets or other TQObject instances using TQApplication::postEvent() or TQApplication::sendEvent(). Subclasses of TQObject can easily receive custom events by implementing the TQObject::customEvent() event handler function.
 .PP
 TQCustomEvent objects should be created with a type ID that uniquely identifies the event type. To avoid clashes with the Qt-defined events types, the value should be at least as large as the value of the "User" entry in the TQEvent::Type enum.
 .PP
@@ -67,7 +67,7 @@ Example:
 .br
     ColorChangeEvent* ce = new ColorChangeEvent( blue );
 .br
-    QApplication::postEvent( receiver, ce );  // TQt will delete it when done
+    TQApplication::postEvent( receiver, ce );  // TQt will delete it when done
 .br
 .br
     // To receive an event of this custom event type:
@@ -89,7 +89,7 @@ Example:
 .br
 .fi
 .PP
-See also TQWidget::customEvent(), QApplication::notify(), and Event Classes.
+See also TQWidget::customEvent(), TQApplication::notify(), and Event Classes.
 .SH MEMBER FUNCTION DOCUMENTATION
 .SH "TQCustomEvent::TQCustomEvent ( int type )"
 Constructs a custom event object with event type \fItype\fR. The value of \fItype\fR must be at least as large as TQEvent::User. The data pointer is set to 0.
diff --git a/doc/man/man3/tqdesktopwidget.3qt b/doc/man/man3/tqdesktopwidget.3qt
index 348ef05ed..6e8003a6f 100644
--- a/doc/man/man3/tqdesktopwidget.3qt
+++ b/doc/man/man3/tqdesktopwidget.3qt
@@ -90,7 +90,7 @@ Creates the desktop widget.
 .PP
 If the system supports a virtual desktop, this widget will have the size of the virtual desktop; otherwise this widget will have the size of the primary screen.
 .PP
-Instead of using TQDesktopWidget directly, use QApplication::desktop().
+Instead of using TQDesktopWidget directly, use TQApplication::desktop().
 .SH "TQDesktopWidget::~TQDesktopWidget ()"
 Destroy the object and free allocated resources.
 .SH "const TQRect & TQDesktopWidget::availableGeometry ( int screen = -1 ) const"
@@ -128,7 +128,7 @@ Returns a widget that represents the screen with index \fIscreen\fR. This widget
 .PP
 .nf
 .br
-    TQPainter paint( QApplication::desktop()->screen( 0 ), TRUE );
+    TQPainter paint( TQApplication::desktop()->screen( 0 ), TRUE );
 .br
     paint.draw...
 .br
diff --git a/doc/man/man3/tqdialog.3qt b/doc/man/man3/tqdialog.3qt
index 80cc1b7f1..c6fa8d468 100644
--- a/doc/man/man3/tqdialog.3qt
+++ b/doc/man/man3/tqdialog.3qt
@@ -104,7 +104,7 @@ A \fBmodal\fR dialog is a dialog that blocks input to other visible windows in t
 .PP
 The most common way to display a modal dialog is to call its exec() function. When the user closes the dialog, exec() will provide a useful return value. Typically we connect a default button, e.g. "OK", to the accept() slot and a" Cancel" button to the reject() slot, to get the dialog to close and return the appropriate value. Alternatively you can connect to the done() slot, passing it Accepted or Rejected.
 .PP
-An alternative is to call setModal(TRUE), then show(). Unlike exec(), show() returns control to the caller immediately. Calling setModal(TRUE) is especially useful for progress dialogs, where the user must have the ability to interact with the dialog, e.g. to cancel a long running operation. If you use show() and setModal(TRUE) together you must call QApplication::processEvents() periodically during processing to enable the user to interact with the dialog. (See TQProgressDialog.)
+An alternative is to call setModal(TRUE), then show(). Unlike exec(), show() returns control to the caller immediately. Calling setModal(TRUE) is especially useful for progress dialogs, where the user must have the ability to interact with the dialog, e.g. to cancel a long running operation. If you use show() and setModal(TRUE) together you must call TQApplication::processEvents() periodically during processing to enable the user to interact with the dialog. (See TQProgressDialog.)
 .SH "Modeless Dialogs"
 A \fBmodeless\fR dialog is a dialog that operates independently of other windows in the same application. Find and replace dialogs in word-processors are often modeless to allow the user to interact with both the application's main window and with the dialog.
 .PP
@@ -153,7 +153,7 @@ A modeless dialog. After the show() call, control returns to the main event loop
 .br
     {
 .br
-        QApplication a( argc, argv );
+        TQApplication a( argc, argv );
 .fi
 .PP
 .nf
@@ -211,9 +211,9 @@ Examples:
 .SH "void TQDialog::done ( int r )\fC [virtual protected slot]\fR"
 Closes the dialog and sets its result code to \fIr\fR. If this dialog is shown with exec(), done() causes the local event loop to finish, and exec() to return \fIr\fR.
 .PP
-As with TQWidget::close(), done() deletes the dialog if the WDestructiveClose flag is set. If the dialog is the application's main widget, the application terminates. If the dialog is the last window closed, the QApplication::lastWindowClosed() signal is emitted.
+As with TQWidget::close(), done() deletes the dialog if the WDestructiveClose flag is set. If the dialog is the application's main widget, the application terminates. If the dialog is the last window closed, the TQApplication::lastWindowClosed() signal is emitted.
 .PP
-See also accept(), reject(), QApplication::mainWidget(), and QApplication::quit().
+See also accept(), reject(), TQApplication::mainWidget(), and TQApplication::quit().
 .SH "int TQDialog::exec ()\fC [slot]\fR"
 Shows the dialog as a modal dialog, blocking until the user closes it. The function returns a DialogCode result.
 .PP
diff --git a/doc/man/man3/tqdir.3qt b/doc/man/man3/tqdir.3qt
index 8aaeb93f8..1cf380043 100644
--- a/doc/man/man3/tqdir.3qt
+++ b/doc/man/man3/tqdir.3qt
@@ -210,7 +210,7 @@ The "current" path refers to the application's working directory. A TQDir's own
 .PP
 An example of an absolute path is the string "/tmp/quartz", a relative path might look like "src/fatlib". You can use the function isRelative() to check if a TQDir is using a relative or an absolute file path. Call convertToAbs() to convert a relative TQDir to an absolute one. For a simplified path use cleanDirPath(). To obtain a path which has no symbolic links or redundant ".." elements use canonicalPath(). The path can be set with setPath(), and changed with cd() and cdUp().
 .PP
-TQDir provides several static functions, for example, setCurrent() to set the application's working directory and currentDirPath() to retrieve the application's working directory. Access to some common paths is provided with the static functions, current(), home() and root() which return TQDir objects or currentDirPath(), homeDirPath() and rootDirPath() which return the path as a string. If you want to know about your application's path use QApplication::applicationDirPath().
+TQDir provides several static functions, for example, setCurrent() to set the application's working directory and currentDirPath() to retrieve the application's working directory. Access to some common paths is provided with the static functions, current(), home() and root() which return TQDir objects or currentDirPath(), homeDirPath() and rootDirPath() which return the path as a string. If you want to know about your application's path use TQApplication::applicationDirPath().
 .PP
 The number of entries in a directory is returned by count(). Obtain a string list of the names of all the files and directories in a directory with entryList(). If you prefer a list of TQFileInfo pointers use entryInfoList(). Both these functions can apply a name filter, an attributes filter (e.g. read-only, files not directories, etc.), and a sort order. The filters and sort may be set with calls to setNameFilter(), setFilter() and setSorting(). They may also be specified in the entryList() and entryInfoList()'s arguments.
 .PP
@@ -302,7 +302,7 @@ A program that lists all the files in the current directory (excluding symbolic
 .br
 .fi
 .PP
-See also QApplication::applicationDirPath() and Input/Output and Networking.
+See also TQApplication::applicationDirPath() and Input/Output and Networking.
 .SS "Member Type Documentation"
 .SH "TQDir::FilterSpec"
 This enum describes the filtering options available to TQDir, e.g. for entryList() and entryInfoList(). The filter value is specified by OR-ing together values from the following list:
diff --git a/doc/man/man3/tqevent.3qt b/doc/man/man3/tqevent.3qt
index f00357f2e..ba1272dab 100644
--- a/doc/man/man3/tqevent.3qt
+++ b/doc/man/man3/tqevent.3qt
@@ -36,15 +36,15 @@ Inherited by TQTimerEvent, TQMouseEvent, QWheelEvent, TQTabletEvent, TQKeyEvent,
 .SH DESCRIPTION
 The TQEvent class is the base class of all event classes. Event objects contain event parameters.
 .PP
-Qt's main event loop (QApplication::exec()) fetches native window system events from the event queue, translates them into TQEvents and sends the translated events to TQObjects.
+Qt's main event loop (TQApplication::exec()) fetches native window system events from the event queue, translates them into TQEvents and sends the translated events to TQObjects.
 .PP
-In general, events come from the underlying window system (spontaneous() returns TRUE) but it is also possible to manually send events using QApplication::sendEvent() and QApplication::postEvent() (spontaneous() returns FALSE).
+In general, events come from the underlying window system (spontaneous() returns TRUE) but it is also possible to manually send events using TQApplication::sendEvent() and TQApplication::postEvent() (spontaneous() returns FALSE).
 .PP
 TQObjects receive events by having their TQObject::event() function called. The function can be reimplemented in subclasses to customize event handling and add additional event types; TQWidget::event() is a notable example. By default, events are dispatched to event handlers like TQObject::timerEvent() and TQWidget::mouseMoveEvent(). TQObject::installEventFilter() allows an object to intercept events destined for another object.
 .PP
 The basic TQEvent contains only an event type parameter. Subclasses of TQEvent contain additional parameters that describe the particular event.
 .PP
-See also TQObject::event(), TQObject::installEventFilter(), TQWidget::event(), QApplication::sendEvent(), QApplication::postEvent(), QApplication::processEvents(), Environment Classes, and Event Classes.
+See also TQObject::event(), TQObject::installEventFilter(), TQWidget::event(), TQApplication::sendEvent(), TQApplication::postEvent(), TQApplication::processEvents(), Environment Classes, and Event Classes.
 .SS "Member Type Documentation"
 .SH "TQEvent::Type"
 This enum type defines the valid event types in Qt. The event types and the specialized classes for each type are these:
diff --git a/doc/man/man3/tqeventloop.3qt b/doc/man/man3/tqeventloop.3qt
index 55c907fe4..37e9e878d 100644
--- a/doc/man/man3/tqeventloop.3qt
+++ b/doc/man/man3/tqeventloop.3qt
@@ -85,13 +85,13 @@ Inherits TQObject.
 .SH DESCRIPTION
 The TQEventLoop class manages the event queue.
 .PP
-It receives events from the window system and other sources. It then sends them to QApplication for processing and delivery.
+It receives events from the window system and other sources. It then sends them to TQApplication for processing and delivery.
 .PP
 TQEventLoop allows the application programmer to have more control over event delivery. Programs that perform long operations can call either processOneEvent() or processEvents() with various ProcessEvent values OR'ed together to control which events should be delivered.
 .PP
 TQEventLoop also allows the integration of an external event loop with the TQt event loop.
 .PP
-To use your own instance of TQEventLoop or TQEventLoop subclass create it before you create the QApplication object.
+To use your own instance of TQEventLoop or TQEventLoop subclass create it before you create the TQApplication object.
 .PP
 See also Main Window and Related Classes and Event Classes.
 .SS "Member Type Documentation"
@@ -113,7 +113,7 @@ A \fCtypedef\fR to allow various ProcessEvents values to be OR'ed together.
 See also ProcessEvents.
 .SH MEMBER FUNCTION DOCUMENTATION
 .SH "TQEventLoop::TQEventLoop ( TQObject * parent = 0, const char * name = 0 )"
-Creates a TQEventLoop object, this object becomes the global event loop object. There can only be one event loop object. The TQEventLoop is usually constructed by calling QApplication::eventLoop(). To create your own event loop object create it before you instantiate the QApplication object.
+Creates a TQEventLoop object, this object becomes the global event loop object. There can only be one event loop object. The TQEventLoop is usually constructed by calling TQApplication::eventLoop(). To create your own event loop object create it before you instantiate the TQApplication object.
 .PP
 The \fIparent\fR and \fIname\fR arguments are passed on to the TQObject constructor.
 .SH "TQEventLoop::~TQEventLoop ()"
@@ -145,7 +145,7 @@ Generally speaking, no user interaction can take place before calling exec(). As
 .PP
 To make your application perform idle processing, i.e. executing a special function whenever there are no pending events, use a TQTimer with 0 timeout. More advanced idle processing schemes can be achieved using processEvents().
 .PP
-See also QApplication::quit(), exit(), and processEvents().
+See also TQApplication::quit(), exit(), and processEvents().
 .SH "void TQEventLoop::exit ( int retcode = 0 )\fC [virtual]\fR"
 Tells the event loop to exit with a return code.
 .PP
@@ -155,7 +155,7 @@ By convention, a \fIretcode\fR of 0 means success, and any non-zero value indica
 .PP
 Note that unlike the C library function of the same name, this function \fIdoes\fR return to the caller -- it is event processing that stops.
 .PP
-See also QApplication::quit() and exec().
+See also TQApplication::quit() and exec().
 .SH "void TQEventLoop::exitLoop ()\fC [virtual]\fR"
 This function exits from a recursive call to the main event loop. Do not call it unless you really know what you are doing.
 .SH "bool TQEventLoop::hasPendingEvents () const\fC [virtual]\fR"
diff --git a/doc/man/man3/tqfile.3qt b/doc/man/man3/tqfile.3qt
index 6284c9938..c18c09573 100644
--- a/doc/man/man3/tqfile.3qt
+++ b/doc/man/man3/tqfile.3qt
@@ -244,7 +244,7 @@ Example: distributor/distributor.ui.h.
 .SH "TQString TQFile::errorString () const"
 Returns a human-readable description of the reason of an error that occurred on the device. The error described by the string corresponds to changes of TQIODevice::status(). If the status is reset, the error string is also reset.
 .PP
-The returned strings are not translated with the TQObject::tr() or QApplication::translate() functions. They are marked as translatable strings in the "TQFile" context. Before you show the string to the user you should translate it first, for example:
+The returned strings are not translated with the TQObject::tr() or TQApplication::translate() functions. They are marked as translatable strings in the "TQFile" context. Before you show the string to the user you should translate it first, for example:
 .PP
 .nf
 .br
diff --git a/doc/man/man3/tqfont.3qt b/doc/man/man3/tqfont.3qt
index 714153c4b..799ba253c 100644
--- a/doc/man/man3/tqfont.3qt
+++ b/doc/man/man3/tqfont.3qt
@@ -229,7 +229,7 @@ The TQFont class specifies a font used for drawing text.
 .PP
 When you create a TQFont object you specify various attributes that you want the font to have. TQt will use the font with the specified attributes, or if no matching font exists, TQt will use the closest matching installed font. The attributes of the font that is actually used are retrievable from a TQFontInfo object. If the window system provides an exact match exactMatch() returns TRUE. Use TQFontMetrics to get measurements, e.g. the pixel length of a string using TQFontMetrics::width().
 .PP
-Use QApplication::setFont() to set the application's default font.
+Use TQApplication::setFont() to set the application's default font.
 .PP
 If a choosen X11 font does not include all the characters that need to be displayed, TQFont will try to find the characters in the nearest equivalent fonts. When a TQPainter draws a character from a font the TQFont will report whether or not it has the character; if it does not, TQPainter will draw an unfilled square.
 .PP
@@ -330,7 +330,7 @@ To find out font metrics use a TQFontMetrics object, e.g.
 .PP
 For more general information on fonts, see the comp.fonts FAQ. Information on encodings can be found from Roman Czyborra's page.
 .PP
-See also TQFontMetrics, TQFontInfo, TQFontDatabase, QApplication::setFont(), TQWidget::font, TQPainter::setFont(), TQFont::StyleHint, TQFont::Weight, Widget Appearance and Style, Graphics Classes, and Implicitly and Explicitly Shared Classes.
+See also TQFontMetrics, TQFontInfo, TQFontDatabase, TQApplication::setFont(), TQWidget::font, TQPainter::setFont(), TQFont::StyleHint, TQFont::Weight, Widget Appearance and Style, Graphics Classes, and Implicitly and Explicitly Shared Classes.
 .SS "Member Type Documentation"
 .SH "TQFont::Script"
 This enum represents Unicode allocated scripts. For exhaustive coverage see The Unicode Standard Version 3.0. The following scripts are supported:
@@ -544,7 +544,7 @@ This enum contains the predefined font weights:
 .SH "TQFont::TQFont ()"
 Constructs a font object that uses the application's default font.
 .PP
-See also QApplication::setFont() and QApplication::font().
+See also TQApplication::setFont() and TQApplication::font().
 .SH "TQFont::TQFont ( const TQString & family, int pointSize = 12, int weight = Normal, bool italic = FALSE )"
 Constructs a font object with the specified \fIfamily\fR, \fIpointSize\fR, \fIweight\fR and \fIitalic\fR settings.
 .PP
@@ -552,7 +552,7 @@ If \fIpointSize\fR is <= 0 it is set to 1.
 .PP
 The \fIfamily\fR name may optionally also include a foundry name, e.g. "Helvetica [Cronyx]". (The TQt 2.x syntax, i.e." Cronyx-Helvetica", is also supported.) If the \fIfamily\fR is available from more than one foundry and the foundry isn't specified, an arbitrary foundry is chosen. If the family isn't available a family will be set using the font matching algorithm.
 .PP
-See also Weight, setFamily(), setPointSize(), setWeight(), setItalic(), setStyleHint(), and QApplication::font().
+See also Weight, setFamily(), setPointSize(), setWeight(), setItalic(), setStyleHint(), and TQApplication::font().
 .SH "TQFont::TQFont ( const TQFont & font )"
 Constructs a font that is a copy of \fIfont\fR.
 .SH "TQFont::~TQFont ()"
@@ -576,7 +576,7 @@ See also StyleHint, styleHint(), and setStyleHint().
 .SH "TQFont TQFont::defaultFont ()\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
-Please use QApplication::font() instead.
+Please use TQApplication::font() instead.
 .SH "bool TQFont::dirty () const\fC [protected]\fR"
 Returns TRUE if the font attributes have been changed and the font has to be (re)loaded; otherwise returns FALSE.
 .SH "bool TQFont::exactMatch () const"
@@ -705,7 +705,7 @@ Examples:
 .SH "void TQFont::setDefaultFont ( const TQFont & f )\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
-Please use QApplication::setFont() instead.
+Please use TQApplication::setFont() instead.
 .SH "void TQFont::setFamily ( const TQString & family )"
 Sets the family name of the font. The name is case insensitive and may include a foundry name.
 .PP
diff --git a/doc/man/man3/tqfontdatabase.3qt b/doc/man/man3/tqfontdatabase.3qt
index c40050b45..28101cf1a 100644
--- a/doc/man/man3/tqfontdatabase.3qt
+++ b/doc/man/man3/tqfontdatabase.3qt
@@ -126,7 +126,7 @@ Example:
 .PP
 .nf
 .br
-#include <ntqapplication.h>
+#include <tqapplication.h>
 .br
 #include <tqfontdatabase.h>
 .br
@@ -137,7 +137,7 @@ int main( int argc, char **argv )
 .br
 {
 .br
-    QApplication app( argc, argv );
+    TQApplication app( argc, argv );
 .br
     TQFontDatabase fdb;
 .br
diff --git a/doc/man/man3/tqfontdialog.3qt b/doc/man/man3/tqfontdialog.3qt
index 546e9c340..41500d1ba 100644
--- a/doc/man/man3/tqfontdialog.3qt
+++ b/doc/man/man3/tqfontdialog.3qt
@@ -130,7 +130,7 @@ Example:
 .br
         // the user canceled the dialog; font is set to the default
 .br
-        // application font, QApplication::font()
+        // application font, TQApplication::font()
 .br
     }
 .br
diff --git a/doc/man/man3/tqglcolormap.3qt b/doc/man/man3/tqglcolormap.3qt
index 2b614ad60..1a5d7624e 100644
--- a/doc/man/man3/tqglcolormap.3qt
+++ b/doc/man/man3/tqglcolormap.3qt
@@ -71,7 +71,7 @@ Example of use:
 .PP
 .nf
 .br
-    #include <ntqapplication.h>
+    #include <tqapplication.h>
 .br
     #include <tqglcolormap.h>
 .br
@@ -80,7 +80,7 @@ Example of use:
 .br
     {
 .br
-        QApplication a( argc, argv );
+        TQApplication a( argc, argv );
 .br
 .br
         MySuperGLWidget widget( 0 ); // A TQGLWidget in color-index mode
diff --git a/doc/man/man3/tqglformat.3qt b/doc/man/man3/tqglformat.3qt
index 0b22d19ef..7e13cc141 100644
--- a/doc/man/man3/tqglformat.3qt
+++ b/doc/man/man3/tqglformat.3qt
@@ -313,11 +313,11 @@ See also setDoubleBuffer().
 .SH "bool TQGLFormat::hasOpenGL ()\fC [static]\fR"
 Returns TRUE if the window system has any OpenGL support; otherwise returns FALSE.
 .PP
-\fBWarning:\fR This function must not be called until the QApplication object has been created.
+\fBWarning:\fR This function must not be called until the TQApplication object has been created.
 .SH "bool TQGLFormat::hasOpenGLOverlays ()\fC [static]\fR"
 Returns TRUE if the window system supports OpenGL overlays; otherwise returns FALSE.
 .PP
-\fBWarning:\fR This function must not be called until the QApplication object has been created.
+\fBWarning:\fR This function must not be called until the TQApplication object has been created.
 .SH "bool TQGLFormat::hasOverlay () const"
 Returns TRUE if overlay plane is enabled; otherwise returns FALSE.
 .PP
@@ -353,7 +353,7 @@ Sets a new default TQGLFormat for the application to \fIf\fR. For example, to se
 .PP
 .nf
 .br
-    QApplication a(argc, argv);
+    TQApplication a(argc, argv);
 .br
     TQGLFormat f;
 .br
diff --git a/doc/man/man3/tqlistboxitem.3qt b/doc/man/man3/tqlistboxitem.3qt
index 686fa033d..9a3b36ffc 100644
--- a/doc/man/man3/tqlistboxitem.3qt
+++ b/doc/man/man3/tqlistboxitem.3qt
@@ -97,7 +97,7 @@ Destroys the list box item.
 .SH "int TQListBoxItem::height ( const TQListBox * lb ) const\fC [virtual]\fR"
 Implement this function to return the height of your item. The \fIlb\fR parameter is the same as listBox() and is provided for convenience and compatibility.
 .PP
-The default implementation returns QApplication::globalStrut()'s height.
+The default implementation returns TQApplication::globalStrut()'s height.
 .PP
 See also paint() and width().
 .PP
@@ -171,7 +171,7 @@ Example: listboxcombo/listboxcombo.cpp.
 .SH "int TQListBoxItem::width ( const TQListBox * lb ) const\fC [virtual]\fR"
 Reimplement this function to return the width of your item. The \fIlb\fR parameter is the same as listBox() and is provided for convenience and compatibility.
 .PP
-The default implementation returns QApplication::globalStrut()'s width.
+The default implementation returns TQApplication::globalStrut()'s width.
 .PP
 See also paint() and height().
 .PP
diff --git a/doc/man/man3/tqmap.3qt b/doc/man/man3/tqmap.3qt
index 402ab40bb..e3c5ee9a7 100644
--- a/doc/man/man3/tqmap.3qt
+++ b/doc/man/man3/tqmap.3qt
@@ -240,7 +240,7 @@ Example:
 .br
     {
 .br
-        QApplication app( argc, argv );
+        TQApplication app( argc, argv );
 .br
 .br
         typedef TQMap<TQString, Employee> EmployeeMap;
diff --git a/doc/man/man3/tqmessagebox.3qt b/doc/man/man3/tqmessagebox.3qt
index a3b208d81..081098afe 100644
--- a/doc/man/man3/tqmessagebox.3qt
+++ b/doc/man/man3/tqmessagebox.3qt
@@ -532,7 +532,7 @@ As a last resort it uses the Information icon.
 .PP
 The about box has a single button labelled "OK".
 .PP
-See also TQWidget::icon and QApplication::mainWidget().
+See also TQWidget::icon and TQApplication::mainWidget().
 .PP
 Examples:
 .)l action/application.cpp, application/application.cpp, chart/chartform.cpp, helpviewer/helpwindow.cpp, mdi/application.cpp, menu/menu.cpp, and themes/themes.cpp.
@@ -541,9 +541,9 @@ Displays a simple message box about Qt, with caption \fIcaption\fR and centered
 .PP
 This is useful for inclusion in the Help menu of an application. See the examples/menu/menu.cpp example.
 .PP
-QApplication provides this functionality as a slot.
+TQApplication provides this functionality as a slot.
 .PP
-See also QApplication::aboutTQt().
+See also TQApplication::aboutTQt().
 .PP
 Examples:
 .)l action/application.cpp, application/application.cpp, chart/chartform.cpp, helpviewer/helpwindow.cpp, menu/menu.cpp and themes/themes.cpp.
diff --git a/doc/man/man3/tqmotifstyle.3qt b/doc/man/man3/tqmotifstyle.3qt
index a78bf7295..81036289f 100644
--- a/doc/man/man3/tqmotifstyle.3qt
+++ b/doc/man/man3/tqmotifstyle.3qt
@@ -41,7 +41,7 @@ If \fIuseHighlightCols\fR is FALSE (the default), the style will polish the appl
 .SH "void TQMotifStyle::setUseHighlightColors ( bool arg )"
 If \fIarg\fR is FALSE, the style will polish the application's color palette to emulate the Motif way of highlighting, which is a simple inversion between the base and the text color.
 .PP
-The effect will show up the next time an application palette is set via QApplication::setPalette(). The current color palette of the application remains unchanged.
+The effect will show up the next time an application palette is set via TQApplication::setPalette(). The current color palette of the application remains unchanged.
 .PP
 See also TQStyle::polish().
 .SH "bool TQMotifStyle::useHighlightColors () const"
diff --git a/doc/man/man3/tqobject.3qt b/doc/man/man3/tqobject.3qt
index ecf09e225..1db0cf235 100644
--- a/doc/man/man3/tqobject.3qt
+++ b/doc/man/man3/tqobject.3qt
@@ -15,7 +15,7 @@ All the functions in this class are reentrant when TQt is built with thread supp
 .PP
 Inherits Qt.
 .PP
--Inherited by TQAccel, TQAccessibleObject, TQAction, QApplication, TQAssistantClient, TQDataPump, TQWidget, TQCanvas, TQStyle, TQClipboard, TQDns, TQLayout, TQDragObject, TQEditorFactory, TQEventLoop, TQFileIconProvider, TQNetworkProtocol, TQNetworkOperation, TQObjectCleanupHandler, TQProcess, TQServerSocket, TQSessionManager, TQSignal, TQSignalMapper, TQSocket, TQSocketNotifier, TQSound, TQSqlDatabase, TQSqlDriver, TQSqlForm, TQStyleSheet, TQTimer, TQToolTipGroup, TQTranslator, TQUrlOperator, and TQValidator.
+-Inherited by TQAccel, TQAccessibleObject, TQAction, TQApplication, TQAssistantClient, TQDataPump, TQWidget, TQCanvas, TQStyle, TQClipboard, TQDns, TQLayout, TQDragObject, TQEditorFactory, TQEventLoop, TQFileIconProvider, TQNetworkProtocol, TQNetworkOperation, TQObjectCleanupHandler, TQProcess, TQServerSocket, TQSessionManager, TQSignal, TQSignalMapper, TQSocket, TQSocketNotifier, TQSound, TQSqlDatabase, TQSqlDriver, TQSqlForm, TQStyleSheet, TQTimer, TQToolTipGroup, TQTranslator, TQUrlOperator, and TQValidator.
 .PP
 .SS "Public Members"
 .in +1c
@@ -259,7 +259,7 @@ This event handler can be reimplemented in a subclass to receive child events.
 .PP
 Child events are sent to objects when children are inserted or removed.
 .PP
-Note that events with TQEvent::type() TQEvent::ChildInserted are posted (with QApplication::postEvent()) to make sure that the child's construction is completed before this function is called.
+Note that events with TQEvent::type() TQEvent::ChildInserted are posted (with TQApplication::postEvent()) to make sure that the child's construction is completed before this function is called.
 .PP
 If a child is removed immediately after it is inserted, the \fCChildInserted\fR event may be suppressed, but the \fCChildRemoved\fR event will always be sent. In such cases it is possible that there will be a \fCChildRemoved\fR event without a corresponding \fCChildInserted\fR event.
 .PP
@@ -267,7 +267,7 @@ If you change state based on \fCChildInserted\fR events, call TQWidget::constPol
 .PP
 .nf
 .br
-        QApplication::sendPostedEvents( this, TQEvent::ChildInserted );
+        TQApplication::sendPostedEvents( this, TQEvent::ChildInserted );
 .br
 .fi
 in functions that depend on the state. One notable example is TQWidget::sizeHint().
@@ -497,7 +497,7 @@ This virtual function receives events to an object and should return TRUE if the
 .PP
 The event() function can be reimplemented to customize the behavior of an object.
 .PP
-See also installEventFilter(), timerEvent(), QApplication::sendEvent(), QApplication::postEvent(), and TQWidget::event().
+See also installEventFilter(), timerEvent(), TQApplication::sendEvent(), TQApplication::postEvent(), and TQWidget::event().
 .PP
 Reimplemented in TQWidget.
 .SH "bool TQObject::eventFilter ( TQObject * watched, TQEvent * e )\fC [virtual]\fR"
@@ -928,7 +928,7 @@ Returns a translated version of \fIsourceText\fR, or \fIsourceText\fR itself if
 .PP
 \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 probably result in crashes or other undesirable behavior.
 .PP
-See also trUtf8(), QApplication::translate(), and Internationalization with Qt.
+See also trUtf8(), TQApplication::translate(), and Internationalization with Qt.
 .PP
 Example: network/networkprotocol/view.cpp.
 .SH "TQString TQObject::trUtf8 ( const char * sourceText, const char * comment )\fC [static]\fR"
@@ -936,7 +936,7 @@ Returns a translated version of \fIsourceText\fR, or TQString::fromUtf8(\fIsourc
 .PP
 \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 probably result in crashes or other undesirable behavior.
 .PP
-See also tr() and QApplication::translate().
+See also tr() and TQApplication::translate().
 .SS "Property Documentation"
 .SH "TQCString name"
 This property holds the name of this object.
diff --git a/doc/man/man3/tqpaintdevice.3qt b/doc/man/man3/tqpaintdevice.3qt
index 83db6825c..c7ea10702 100644
--- a/doc/man/man3/tqpaintdevice.3qt
+++ b/doc/man/man3/tqpaintdevice.3qt
@@ -189,7 +189,7 @@ Example (scroll widget contents 10 pixels to the right):
 .br
 .fi
 .PP
-\fBWarning:\fR TQt requires that a QApplication object exists before any paint devices can be created. Paint devices access window system resources, and these resources are not initialized before an application object is created.
+\fBWarning:\fR TQt requires that a TQApplication object exists before any paint devices can be created. Paint devices access window system resources, and these resources are not initialized before an application object is created.
 .PP
 See also Graphics Classes and Image Processing Classes.
 .SH MEMBER FUNCTION DOCUMENTATION
diff --git a/doc/man/man3/tqpainter.3qt b/doc/man/man3/tqpainter.3qt
index b7e586ee5..b223bea72 100644
--- a/doc/man/man3/tqpainter.3qt
+++ b/doc/man/man3/tqpainter.3qt
@@ -1027,23 +1027,23 @@ Draws a tiled pixmap, \fIpm\fR, inside rectangle \fIr\fR.
 .SH "void TQPainter::drawWinFocusRect ( int x, int y, int w, int h, const TQColor & bgColor )"
 Draws a Windows focus rectangle with upper left corner at (\fIx\fR, \fIy\fR) and with width \fIw\fR and height \fIh\fR using a pen color that contrasts with \fIbgColor\fR.
 .PP
-This function draws a stippled rectangle (XOR is not used) that is used to indicate keyboard focus (when the QApplication::style() is \fCWindowStyle\fR).
+This function draws a stippled rectangle (XOR is not used) that is used to indicate keyboard focus (when the TQApplication::style() is \fCWindowStyle\fR).
 .PP
 The pen color used to draw the rectangle is either white or black depending on the color of \fIbgColor\fR (see TQColor::gray()).
 .PP
 \fBWarning:\fR This function draws nothing if the coordinate system has been rotated or sheared.
 .PP
-See also drawRect() and QApplication::style().
+See also drawRect() and TQApplication::style().
 .SH "void TQPainter::drawWinFocusRect ( int x, int y, int w, int h )"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
 Draws a Windows focus rectangle with upper left corner at (\fIx\fR, \fIy\fR) and with width \fIw\fR and height \fIh\fR.
 .PP
-This function draws a stippled XOR rectangle that is used to indicate keyboard focus (when QApplication::style() is \fCWindowStyle\fR).
+This function draws a stippled XOR rectangle that is used to indicate keyboard focus (when TQApplication::style() is \fCWindowStyle\fR).
 .PP
 \fBWarning:\fR This function draws nothing if the coordinate system has been rotated or sheared.
 .PP
-See also drawRect() and QApplication::style().
+See also drawRect() and TQApplication::style().
 .SH "void TQPainter::drawWinFocusRect ( const TQRect & r )"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
@@ -1585,7 +1585,7 @@ The rectangle's interior is filled with the \fIfill\fR brush unless \fIfill\fR i
 .PP
 If you want to use a TQFrame widget instead, you can make it display a plain rectangle, for example \fCTQFrame::setFrameStyle( TQFrame::Box | TQFrame::Plain )\fR.
 .PP
-\fBWarning:\fR This function does not look at TQWidget::style() or QApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
+\fBWarning:\fR This function does not look at TQWidget::style() or TQApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
 .PP
 See also qDrawShadeRect() and TQStyle::drawPrimitive().
 .SH "void qDrawShadeLine ( TQPainter * p, int x1, int y1, int x2, int y2, const TQColorGroup & g, bool sunken, int lineWidth, int midLineWidth )"
@@ -1605,7 +1605,7 @@ The \fImidLineWidth\fR argument specifies the width of a middle line drawn in th
 .PP
 If you want to use a TQFrame widget instead, you can make it display a shaded line, for example \fCTQFrame::setFrameStyle( TQFrame::HLine | TQFrame::Sunken )\fR.
 .PP
-\fBWarning:\fR This function does not look at TQWidget::style() or QApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
+\fBWarning:\fR This function does not look at TQWidget::style() or TQApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
 .PP
 See also qDrawShadeRect(), qDrawShadePanel(), and TQStyle::drawPrimitive().
 .SH "void qDrawShadePanel ( TQPainter * p, int x, int y, int w, int h, const TQColorGroup & g, bool sunken, int lineWidth, const TQBrush * fill )"
@@ -1623,7 +1623,7 @@ The panel's interior is filled with the \fIfill\fR brush unless \fIfill\fR is 0.
 .PP
 If you want to use a TQFrame widget instead, you can make it display a shaded panel, for example \fCTQFrame::setFrameStyle( TQFrame::Panel | TQFrame::Sunken )\fR.
 .PP
-\fBWarning:\fR This function does not look at TQWidget::style() or QApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
+\fBWarning:\fR This function does not look at TQWidget::style() or TQApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
 .PP
 See also qDrawWinPanel(), qDrawShadeLine(), qDrawShadeRect(), and TQStyle::drawPrimitive().
 .SH "void qDrawShadeRect ( TQPainter * p, int x, int y, int w, int h, const TQColorGroup & g, bool sunken, int lineWidth, int midLineWidth, const TQBrush * fill )"
@@ -1643,7 +1643,7 @@ The rectangle's interior is filled with the \fIfill\fR brush unless \fIfill\fR i
 .PP
 If you want to use a TQFrame widget instead, you can make it display a shaded rectangle, for example \fCTQFrame::setFrameStyle( TQFrame::Box | TQFrame::Raised )\fR.
 .PP
-\fBWarning:\fR This function does not look at TQWidget::style() or QApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
+\fBWarning:\fR This function does not look at TQWidget::style() or TQApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
 .PP
 See also qDrawShadeLine(), qDrawShadePanel(), qDrawPlainRect(), TQStyle::drawItem(), TQStyle::drawControl(), and TQStyle::drawComplexControl().
 .SH "void qDrawWinButton ( TQPainter * p, int x, int y, int w, int h, const TQColorGroup & g, bool sunken, const TQBrush * fill )"
@@ -1659,7 +1659,7 @@ The line width is 2 pixels.
 .PP
 The button's interior is filled with the \fI*fill\fR brush unless \fIfill\fR is 0.
 .PP
-\fBWarning:\fR This function does not look at TQWidget::style() or QApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
+\fBWarning:\fR This function does not look at TQWidget::style() or TQApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
 .PP
 See also qDrawWinPanel() and TQStyle::drawControl().
 .SH "void qDrawWinPanel ( TQPainter * p, int x, int y, int w, int h, const TQColorGroup & g, bool sunken, const TQBrush * fill )"
@@ -1677,7 +1677,7 @@ The button's interior is filled with the \fIfill\fR brush unless \fIfill\fR is 0
 .PP
 If you want to use a TQFrame widget instead, you can make it display a shaded panel, for example \fCTQFrame::setFrameStyle( TQFrame::WinPanel | TQFrame::Raised )\fR.
 .PP
-\fBWarning:\fR This function does not look at TQWidget::style() or QApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
+\fBWarning:\fR This function does not look at TQWidget::style() or TQApplication::style(). Use the drawing functions in TQStyle to make widgets that follow the current GUI style.
 .PP
 See also qDrawShadePanel(), qDrawWinButton(), and TQStyle::drawPrimitive().
 
diff --git a/doc/man/man3/tqpalette.3qt b/doc/man/man3/tqpalette.3qt
index e6b30193f..b758c709a 100644
--- a/doc/man/man3/tqpalette.3qt
+++ b/doc/man/man3/tqpalette.3qt
@@ -123,7 +123,7 @@ Colors and brushes can be set for particular roles in any of a palette's color g
 .PP
 You can copy a palette using the copy constructor and test to see if two palettes are \fIidentical\fR using isCopyOf().
 .PP
-See also QApplication::setPalette(), TQWidget::palette, TQColorGroup, TQColor, Widget Appearance and Style, Graphics Classes, Image Processing Classes, and Implicitly and Explicitly Shared Classes.
+See also TQApplication::setPalette(), TQWidget::palette, TQColorGroup, TQColor, Widget Appearance and Style, Graphics Classes, Image Processing Classes, and Implicitly and Explicitly Shared Classes.
 .SS "Member Type Documentation"
 .SH "TQPalette::ColorGroup"
 .TP
diff --git a/doc/man/man3/tqprogressdialog.3qt b/doc/man/man3/tqprogressdialog.3qt
index 5b5aace77..aa1125a0b 100644
--- a/doc/man/man3/tqprogressdialog.3qt
+++ b/doc/man/man3/tqprogressdialog.3qt
@@ -149,7 +149,7 @@ The dialog automatically resets and hides itself at the end of the operation. Us
 .PP
 There are two ways of using TQProgressDialog: modal and modeless.
 .PP
-Using a modal TQProgressDialog is simpler for the programmer, but you must call QApplication::processEvents() or TQEventLoop::processEvents(ExcludeUserInput) to keep the event loop running to ensure that the application doesn't freeze. Do the operation in a loop, call setProgress() at intervals, and check for cancellation with wasCanceled(). For example:
+Using a modal TQProgressDialog is simpler for the programmer, but you must call TQApplication::processEvents() or TQEventLoop::processEvents(ExcludeUserInput) to keep the event loop running to ensure that the application doesn't freeze. Do the operation in a loop, call setProgress() at intervals, and check for cancellation with wasCanceled(). For example:
 .PP
 .nf
 .br
@@ -378,7 +378,7 @@ This property holds the current amount of progress made.
 .PP
 For the progress dialog to work as expected, you should initially set this property to 0 and finally set it to TQProgressDialog::totalSteps(); you can call setProgress() any number of times in-between.
 .PP
-\fBWarning:\fR If the progress dialog is modal (see TQProgressDialog::TQProgressDialog()), this function calls QApplication::processEvents(), so take care that this does not cause undesirable re-entrancy in your code. For example, don't use a TQProgressDialog inside a paintEvent()!
+\fBWarning:\fR If the progress dialog is modal (see TQProgressDialog::TQProgressDialog()), this function calls TQApplication::processEvents(), so take care that this does not cause undesirable re-entrancy in your code. For example, don't use a TQProgressDialog inside a paintEvent()!
 .PP
 See also totalSteps.
 .PP
diff --git a/doc/man/man3/tqsessionmanager.3qt b/doc/man/man3/tqsessionmanager.3qt
index 57edd4fdf..070972691 100644
--- a/doc/man/man3/tqsessionmanager.3qt
+++ b/doc/man/man3/tqsessionmanager.3qt
@@ -75,7 +75,7 @@ The TQSessionManager class provides access to the session manager.
 .PP
 The session manager is responsible for session management, most importantly for interruption and resumption. A "session" is a kind of record of the state of the system, e.g. which applications were run at start up and which applications are currently running. The session manager is used to save the session, e.g. when the machine is shut down; and to restore a session, e.g. when the machine is started up. Use TQSettings to save and restore an individual application's settings, e.g. window positions, recently used files, etc.
 .PP
-TQSessionManager provides an interface between the application and the session manager so that the program can work well with the session manager. In Qt, session management requests for action are handled by the two virtual functions QApplication::commitData() and QApplication::saveState(). Both provide a reference to a session manager object as argument, to allow the application to communicate with the session manager.
+TQSessionManager provides an interface between the application and the session manager so that the program can work well with the session manager. In Qt, session management requests for action are handled by the two virtual functions TQApplication::commitData() and TQApplication::saveState(). Both provide a reference to a session manager object as argument, to allow the application to communicate with the session manager.
 .PP
 During a session management action (i.e. within commitData() and saveState()), no user interaction is possible \fIunless\fR the application got explicit permission from the session manager. You ask for permission by calling allowsInteraction() or, if it's really urgent, allowsErrorInteraction(). TQt does not enforce this, but the session manager may.
 .PP
@@ -111,7 +111,7 @@ When the interaction is completed we strongly recommend releasing the user inter
 .PP
 If the user decides to cancel the shutdown process during the interaction phase, you must tell the session manager that this has happened by calling cancel().
 .PP
-Here's an example of how an application's QApplication::commitData() might be implemented:
+Here's an example of how an application's TQApplication::commitData() might be implemented:
 .PP
 .nf
 .br
@@ -168,7 +168,7 @@ void MyApplication::commitData( TQSessionManager& sm ) {
 .PP
 If an error occurred within the application while saving its data, you may want to try allowsErrorInteraction() instead.
 .PP
-See also QApplication::commitData(), release(), and cancel().
+See also TQApplication::commitData(), release(), and cancel().
 .SH "void TQSessionManager::cancel ()"
 Tells the session manager to cancel the shutdown process. Applications should not call this function without first asking the user.
 .PP
@@ -206,7 +206,7 @@ Releases the session manager's interaction semaphore after an interaction phase.
 .PP
 See also allowsInteraction() and allowsErrorInteraction().
 .SH "void TQSessionManager::requestPhase2 ()"
-Requests a second session management phase for the application. The application may then return immediately from the QApplication::commitData() or QApplication::saveState() function, and they will be called again once most or all other applications have finished their session management.
+Requests a second session management phase for the application. The application may then return immediately from the TQApplication::commitData() or TQApplication::saveState() function, and they will be called again once most or all other applications have finished their session management.
 .PP
 The two phases are useful for applications such as the X11 window manager that need to store information about another application's windows and therefore have to wait until these applications have completed their respective session management tasks.
 .PP
@@ -244,7 +244,7 @@ Returns the identifier of the current session.
 .PP
 If the application has been restored from an earlier session, this identifier is the same as it was in that earlier session.
 .PP
-See also sessionKey() and QApplication::sessionId().
+See also sessionKey() and TQApplication::sessionId().
 .SH "TQString TQSessionManager::sessionKey () const"
 Returns the session key in the current session.
 .PP
@@ -252,7 +252,7 @@ If the application has been restored from an earlier session, this key is the sa
 .PP
 The session key changes with every call of commitData() or saveState().
 .PP
-See also sessionId() and QApplication::sessionKey().
+See also sessionId() and TQApplication::sessionKey().
 .SH "void TQSessionManager::setDiscardCommand ( const TQStringList & )"
 See also discardCommand() and setRestartCommand().
 .SH "void TQSessionManager::setManagerProperty ( const TQString & name, const TQStringList & value )"
@@ -274,7 +274,7 @@ If the session manager is capable of restoring sessions it will execute \fIcomma
 .br
 .fi
 .PP
-The \fC-session\fR option is mandatory; otherwise QApplication cannot tell whether it has been restored or what the current session identifier is. See QApplication::isSessionRestored() and QApplication::sessionId() for details.
+The \fC-session\fR option is mandatory; otherwise TQApplication cannot tell whether it has been restored or what the current session identifier is. See TQApplication::isSessionRestored() and TQApplication::sessionId() for details.
 .PP
 If your application is very simple, it may be possible to store the entire application state in additional command line options. This is usually a very bad idea because command lines are often limited to a few hundred bytes. Instead, use TQSettings, or temporary files or a database for this purpose. By marking the data with the unique sessionId(), you will be able to restore the application in a future session.
 .PP
@@ -284,7 +284,7 @@ Sets the application's restart hint to \fIhint\fR. On application startup the hi
 .PP
 Note that these flags are only hints, a session manager may or may not respect them.
 .PP
-We recommend setting the restart hint in QApplication::saveState() because most session managers perform a checkpoint shortly after an application's startup.
+We recommend setting the restart hint in TQApplication::saveState() because most session managers perform a checkpoint shortly after an application's startup.
 .PP
 See also restartHint().
 
diff --git a/doc/man/man3/tqsjiscodec.3qt b/doc/man/man3/tqsjiscodec.3qt
index 3d1973f67..db8cce557 100644
--- a/doc/man/man3/tqsjiscodec.3qt
+++ b/doc/man/man3/tqsjiscodec.3qt
@@ -49,7 +49,7 @@ THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS". ANY EXPRESS OR
 See also Internationalization with Qt.
 .SH MEMBER FUNCTION DOCUMENTATION
 .SH "TQSjisCodec::TQSjisCodec ()"
-Creates a Shift-JIS codec. Note that this is done automatically by the QApplication, you do not need construct your own.
+Creates a Shift-JIS codec. Note that this is done automatically by the TQApplication, you do not need construct your own.
 .SH "TQSjisCodec::~TQSjisCodec ()"
 Destroys the Shift-JIS codec.
 .SH "const char * TQSjisCodec::mimeName () const\fC [virtual]\fR"
diff --git a/doc/man/man3/tqsocket.3qt b/doc/man/man3/tqsocket.3qt
index b8dbd811f..9e440fb79 100644
--- a/doc/man/man3/tqsocket.3qt
+++ b/doc/man/man3/tqsocket.3qt
@@ -153,7 +153,7 @@ The TQSocket class provides a buffered TCP connection.
 .PP
 It provides a totally non-blocking TQIODevice, and modifies and extends the API of TQIODevice with socket-specific code.
 .PP
-Note that a QApplication must have been constructed before this class can be used.
+Note that a TQApplication must have been constructed before this class can be used.
 .PP
 The functions you're likely to call most are connectToHost(), bytesAvailable(), canReadLine() and the ones it inherits from TQIODevice.
 .PP
@@ -199,7 +199,7 @@ Creates a TQSocket object in TQSocket::Idle state.
 .PP
 The \fIparent\fR and \fIname\fR arguments are passed on to the TQObject constructor.
 .PP
-Note that a QApplication must have been constructed before sockets can be used.
+Note that a TQApplication must have been constructed before sockets can be used.
 .SH "TQSocket::~TQSocket ()\fC [virtual]\fR"
 Destroys the socket. Closes the connection if necessary.
 .PP
diff --git a/doc/man/man3/tqsplashscreen.3qt b/doc/man/man3/tqsplashscreen.3qt
index 260f8e321..ade23bf8e 100644
--- a/doc/man/man3/tqsplashscreen.3qt
+++ b/doc/man/man3/tqsplashscreen.3qt
@@ -72,7 +72,7 @@ The most common usage is to show a splash screen before the main widget is displ
 .br
    {
 .br
-       QApplication app( argc, argv );
+       TQApplication app( argc, argv );
 .br
        TQPixmap pixmap( "splash.png" );
 .br
@@ -100,7 +100,7 @@ The most common usage is to show a splash screen before the main widget is displ
 .PP
 It is sometimes useful to update the splash screen with messages, for example, announcing connections established or modules loaded as the application starts up. TQSplashScreen supports this with the message() function. If you wish to do your own drawing you can get a pointer to the pixmap used in the splash screen with pixmap(). Alternatively, you can subclass TQSplashScreen and reimplement drawContents().
 .PP
-The user can hide the splash screen by clicking on it with the mouse. Since the splash screen is typically displayed before the event loop has started running, it is necessary to periodically call QApplication::processEvents() to receive the mouse clicks.
+The user can hide the splash screen by clicking on it with the mouse. Since the splash screen is typically displayed before the event loop has started running, it is necessary to periodically call TQApplication::processEvents() to receive the mouse clicks.
 .PP
 .nf
 .br
@@ -151,7 +151,7 @@ See also message() and clear().
 .SH "TQPixmap * TQSplashScreen::pixmap () const"
 Returns the pixmap that is used in the splash screen. The image does not have any of the text drawn by message() calls.
 .SH "void TQSplashScreen::repaint ()"
-This overrides TQWidget::repaint(). It differs from the standard repaint function in that it also calls QApplication::flush() to ensure the updates are displayed, even when there is no event loop present.
+This overrides TQWidget::repaint(). It differs from the standard repaint function in that it also calls TQApplication::flush() to ensure the updates are displayed, even when there is no event loop present.
 .SH "void TQSplashScreen::setPixmap ( const TQPixmap & pixmap )"
 Sets the pixmap that will be used as the splash screen's image to
 \fIpixmap\fR.
diff --git a/doc/man/man3/tqstyle.3qt b/doc/man/man3/tqstyle.3qt
index 40c4fd206..6d1d18a8b 100644
--- a/doc/man/man3/tqstyle.3qt
+++ b/doc/man/man3/tqstyle.3qt
@@ -30,10 +30,10 @@ Inherited by TQCommonStyle.
 .BI "virtual void \fBunPolish\fR ( TQWidget * )"
 .br
 .ti -1c
-.BI "virtual void \fBpolish\fR ( QApplication * )"
+.BI "virtual void \fBpolish\fR ( TQApplication * )"
 .br
 .ti -1c
-.BI "virtual void \fBunPolish\fR ( QApplication * )"
+.BI "virtual void \fBunPolish\fR ( TQApplication * )"
 .br
 .ti -1c
 .BI "virtual void \fBpolish\fR ( TQPalette & )"
@@ -953,10 +953,10 @@ Reasonable actions in this function might be to call TQWidget::setBackgroundMode
 The TQWidget::inherits() function may provide enough information to allow class-specific customizations. But be careful not to hard-code things too much because new TQStyle subclasses are expected to work reasonably with all current and \fIfuture\fR widgets.
 .PP
 See also unPolish().
-.SH "void TQStyle::polish ( QApplication * )\fC [virtual]\fR"
+.SH "void TQStyle::polish ( TQApplication * )\fC [virtual]\fR"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
-Late initialization of the QApplication object.
+Late initialization of the TQApplication object.
 .PP
 See also unPolish().
 .SH "void TQStyle::polish ( TQPalette & )\fC [virtual]\fR"
@@ -964,7 +964,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
 .PP
 The style may have certain requirements for color palettes. In this function it has the chance to change the palette according to these requirements.
 .PP
-See also TQPalette and QApplication::setPalette().
+See also TQPalette and TQApplication::setPalette().
 .SH "void TQStyle::polishPopupMenu ( TQPopupMenu * )\fC [pure virtual]\fR"
 Polishes the popup menu according to the GUI style. This usually means setting the mouse tracking (TQPopupMenu::setMouseTracking()) and whether the menu is checkable by default (TQPopupMenu::setCheckable()).
 .SH "SubControl TQStyle::querySubControl ( ComplexControl control, const TQWidget * widget, const TQPoint & pos, const TQStyleOption & opt = TQStyleOption::Default ) const\fC [pure virtual]\fR"
@@ -1046,7 +1046,7 @@ Undoes the initialization of a widget's appearance.
 This function is the counterpart to polish. It is called for every polished widget when the style is dynamically changed. The former style has to unpolish its settings before the new style can polish them again.
 .PP
 See also polish().
-.SH "void TQStyle::unPolish ( QApplication * )\fC [virtual]\fR"
+.SH "void TQStyle::unPolish ( TQApplication * )\fC [virtual]\fR"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
 Undoes the application polish.
@@ -1055,13 +1055,13 @@ See also polish().
 .SH "TQRect TQStyle::visualRect ( const TQRect & logical, const TQWidget * w )\fC [static]\fR"
 Returns the rect \fIlogical\fR in screen coordinates. The bounding rect for widget \fIw\fR is used to perform the translation. This function is provided to aid style implementors in supporting right-to-left mode.
 .PP
-See also QApplication::reverseLayout().
+See also TQApplication::reverseLayout().
 .SH "TQRect TQStyle::visualRect ( const TQRect & logical, const TQRect & bounding )\fC [static]\fR"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
 Returns the rect \fIlogical\fR in screen coordinates. The rect \fIbounding\fR is used to perform the translation. This function is provided to aid style implementors in supporting right-to-left mode.
 .PP
-See also QApplication::reverseLayout().
+See also TQApplication::reverseLayout().
 
 .SH "SEE ALSO"
 .BR http://doc.trolltech.com/tqstyle.html
diff --git a/doc/man/man3/tqtextcodec.3qt b/doc/man/man3/tqtextcodec.3qt
index f7f9950e4..45311536a 100644
--- a/doc/man/man3/tqtextcodec.3qt
+++ b/doc/man/man3/tqtextcodec.3qt
@@ -424,9 +424,9 @@ Deletes all the created codecs.
 .PP
 \fBWarning:\fR Do not call this function.
 .PP
-QApplication calls this function just before exiting to delete any TQTextCodec objects that may be lying around. Since various other classes hold pointers to TQTextCodec objects, it is not safe to call this function earlier.
+TQApplication calls this function just before exiting to delete any TQTextCodec objects that may be lying around. Since various other classes hold pointers to TQTextCodec objects, it is not safe to call this function earlier.
 .PP
-If you are using the utility classes (like TQString) but not using QApplication, calling this function at the very end of your application may be helpful for chasing down memory leaks by eliminating any TQTextCodec objects.
+If you are using the utility classes (like TQString) but not using TQApplication, calling this function at the very end of your application may be helpful for chasing down memory leaks by eliminating any TQTextCodec objects.
 .SH "TQCString TQTextCodec::fromUnicode ( const TQString & uc, int & lenInOut ) const\fC [virtual]\fR"
 TQTextCodec subclasses must reimplement either this function or makeEncoder(). It converts the first \fIlenInOut\fR characters of \fIuc\fR from Unicode to the encoding of the subclass. If \fIlenInOut\fR is negative or too large, the length of \fIuc\fR is used instead.
 .PP
@@ -518,7 +518,7 @@ If the literal quoted text in the program is not in the Latin-1 encoding, this f
 .br
     {
 .br
-        QApplication app(argc, argv);
+        TQApplication app(argc, argv);
 .br
         ... install any additional codecs ...
 .br
diff --git a/doc/man/man3/tqthreadstorage.3qt b/doc/man/man3/tqthreadstorage.3qt
index 3384c66dc..a56d04774 100644
--- a/doc/man/man3/tqthreadstorage.3qt
+++ b/doc/man/man3/tqthreadstorage.3qt
@@ -95,7 +95,7 @@ TQThreadStorage can only be used with threads started with TQThread. It \fIcanno
 As a corollary to the above, platform-specific APIs cannot be used to exit or terminate a TQThread using TQThreadStorage. Doing so will cause all per-thread data to be leaked. See TQThread::exit() and TQThread::terminate().
 .IP
 .TP
-TQThreadStorage \fIcan\fR be used to store data for the \fImain()\fR thread \fIafter\fR QApplication has been constructed. TQThreadStorage deletes all data set for the \fImain()\fR thread when QApplication is destroyed, regardless of whether or not the \fImain()\fR thread has actually finished.
+TQThreadStorage \fIcan\fR be used to store data for the \fImain()\fR thread \fIafter\fR TQApplication has been constructed. TQThreadStorage deletes all data set for the \fImain()\fR thread when TQApplication is destroyed, regardless of whether or not the \fImain()\fR thread has actually finished.
 .IP
 .TP
 The implementation of TQThreadStorage limits the total number of TQThreadStorage objects to 256. An unlimited number of threads can store per-thread data in each TQThreadStorage object.
diff --git a/doc/man/man3/tqtimer.3qt b/doc/man/man3/tqtimer.3qt
index 0750c2d76..e62c1308a 100644
--- a/doc/man/man3/tqtimer.3qt
+++ b/doc/man/man3/tqtimer.3qt
@@ -119,7 +119,7 @@ Example:
 .PP
 .nf
 .br
-        #include <ntqapplication.h>
+        #include <tqapplication.h>
 .br
         #include <tqtimer.h>
 .br
@@ -128,7 +128,7 @@ Example:
 .br
         {
 .br
-            QApplication a( argc, argv );
+            TQApplication a( argc, argv );
 .br
             TQTimer::singleShot( 10*60*1000, &a, TQ_SLOT(quit()) );
 .br
diff --git a/doc/man/man3/tqtranslator.3qt b/doc/man/man3/tqtranslator.3qt
index 6ccb0cb1f..18217c245 100644
--- a/doc/man/man3/tqtranslator.3qt
+++ b/doc/man/man3/tqtranslator.3qt
@@ -75,7 +75,7 @@ The TQTranslator class provides internationalization support for text output.
 .PP
 An object of this class contains a set of TQTranslatorMessage objects, each of which specifies a translation from a source language to a target language. TQTranslator provides functions to look up translations, add new ones, remove them, load and save them, etc.
 .PP
-The most common use of TQTranslator is to: load a translator file created with TQt Linguist, install it using QApplication::installTranslator(), and use it via TQObject::tr(). For example:
+The most common use of TQTranslator is to: load a translator file created with TQt Linguist, install it using TQApplication::installTranslator(), and use it via TQObject::tr(). For example:
 .PP
 .nf
 .br
@@ -83,7 +83,7 @@ The most common use of TQTranslator is to: load a translator file created with T
 .br
     {
 .br
-        QApplication app( argc, argv );
+        TQApplication app( argc, argv );
 .br
 .br
         TQTranslator translator( 0 );
@@ -111,7 +111,7 @@ Most applications will never need to do anything else with this class. The other
 .PP
 We call a translation a "messsage". For this reason, translation files are sometimes referred to as "message files".
 .PP
-It is possible to lookup a translation using findMessage() (as tr() and QApplication::translate() do) and contains(), to insert a new translation messsage using insert(), and to remove one using remove().
+It is possible to lookup a translation using findMessage() (as tr() and TQApplication::translate() do) and contains(), to insert a new translation messsage using insert(), and to remove one using remove().
 .PP
 Translation tools often need more information than the bare source text and translation, for example, context information to help the translator. But end-user programs that are using translations usually only need lookup. To cater for these different needs, TQTranslator can use stripped translator files that use the minimum of memory and which support little more functionality than findMessage().
 .PP
@@ -137,7 +137,7 @@ But it's not always so simple. The Spanish version of a printer dialog with sett
 .PP
 Note that when TQTranslator loads a stripped file, most functions do not work. The functions that do work with stripped files are explicitly documented as such.
 .PP
-See also TQTranslatorMessage, QApplication::installTranslator(), QApplication::removeTranslator(), TQObject::tr(), QApplication::translate(), Environment Classes, and Internationalization with Qt.
+See also TQTranslatorMessage, TQApplication::installTranslator(), TQApplication::removeTranslator(), TQObject::tr(), TQApplication::translate(), Environment Classes, and Internationalization with Qt.
 .SS "Member Type Documentation"
 .SH "TQTranslator::SaveMode"
 This enum type defines how TQTranslator writes translation files. There are two modes:
diff --git a/doc/man/man3/tqwidget.3qt b/doc/man/man3/tqwidget.3qt
index d95f88ee6..418f0de23 100644
--- a/doc/man/man3/tqwidget.3qt
+++ b/doc/man/man3/tqwidget.3qt
@@ -1207,7 +1207,7 @@ If the widget has active focus, a focus out event is sent to this widget to tell
 .PP
 This widget must enable focus setting in order to get the keyboard input focus, i.e. it must call setFocusPolicy().
 .PP
-See also focus, setFocus(), focusInEvent(), focusOutEvent(), focusPolicy, and QApplication::focusWidget().
+See also focus, setFocus(), focusInEvent(), focusOutEvent(), focusPolicy, and TQApplication::focusWidget().
 .SH "void TQWidget::clearMask ()"
 Removes any mask set by setMask().
 .PP
@@ -1229,7 +1229,7 @@ Closes this widget. Returns TRUE if the widget was closed; otherwise returns FAL
 .PP
 First it sends the widget a TQCloseEvent. The widget is hidden if it accepts the close event. The default implementation of TQWidget::closeEvent() accepts the close event.
 .PP
-The QApplication::lastWindowClosed() signal is emitted when the last visible top level widget is closed.
+The TQApplication::lastWindowClosed() signal is emitted when the last visible top level widget is closed.
 .PP
 Examples:
 .)l dialog/mainwindow.cpp, mdi/application.cpp, popup/popup.cpp, and toplevel/options.ui.h.
@@ -1240,11 +1240,11 @@ Closes this widget. Returns TRUE if the widget was closed; otherwise returns FAL
 .PP
 If \fIalsoDelete\fR is TRUE or the widget has the WDestructiveClose widget flag, the widget is also deleted. The widget can prevent itself from being closed by rejecting the TQCloseEvent it gets. A close events is delivered to the widget no matter if the widget is visible or not.
 .PP
-The QApplication::lastWindowClosed() signal is emitted when the last visible top level widget is closed.
+The TQApplication::lastWindowClosed() signal is emitted when the last visible top level widget is closed.
 .PP
-Note that closing the QApplication::mainWidget() terminates the application.
+Note that closing the TQApplication::mainWidget() terminates the application.
 .PP
-See also closeEvent(), TQCloseEvent, hide(), QApplication::quit(), QApplication::setMainWidget(), and QApplication::lastWindowClosed().
+See also closeEvent(), TQCloseEvent, hide(), TQApplication::quit(), TQApplication::setMainWidget(), and TQApplication::lastWindowClosed().
 .SH "void TQWidget::closeEvent ( TQCloseEvent * e )\fC [virtual protected]\fR"
 This event handler, for event \fIe\fR, can be reimplemented in a subclass to receive widget close events.
 .PP
@@ -1433,7 +1433,7 @@ Returns the focus proxy, or 0 if there is no focus proxy.
 .PP
 See also setFocusProxy().
 .SH "TQWidget * TQWidget::focusWidget () const"
-Returns the focus widget in this widget's window. This is not the same as QApplication::focusWidget(), which returns the focus widget in the currently active window.
+Returns the focus widget in this widget's window. This is not the same as TQApplication::focusWidget(), which returns the focus widget in the currently active window.
 .SH "TQFont TQWidget::font () const"
 Returns the font currently set for the widget. See the "font" property for details.
 .SH "void TQWidget::fontChange ( const TQFont & oldFont )\fC [virtual protected]\fR"
@@ -1674,7 +1674,7 @@ In your reimplementation of this function, if you want to stop the event being h
 .PP
 \fBWarning:\fR This function is not portable.
 .PP
-See also QApplication::macEventFilter().
+See also TQApplication::macEventFilter().
 .SH "TQPoint TQWidget::mapFrom ( TQWidget * parent, const TQPoint & pos ) const"
 Translates the widget coordinate \fIpos\fR from the coordinate system of \fIparent\fR to this widget's coordinate system. The \fIparent\fR must not be 0 and must be a parent of the calling widget.
 .PP
@@ -1838,11 +1838,11 @@ This function will be called \fIafter\fR a widget has been fully created and \fI
 .PP
 Polishing is useful for final initialization which depends on having an instantiated widget. This is something a constructor cannot guarantee since the initialization of the subclasses might not be finished.
 .PP
-After this function, the widget has a proper font and palette and QApplication::polish() has been called.
+After this function, the widget has a proper font and palette and TQApplication::polish() has been called.
 .PP
 Remember to call TQWidget's implementation first when reimplementing this function to ensure that your program does not end up in infinite recursion.
 .PP
-See also constPolish() and QApplication::polish().
+See also constPolish() and TQApplication::polish().
 .PP
 Example: menu/menu.cpp.
 .SH "TQPoint TQWidget::pos () const"
@@ -1955,7 +1955,7 @@ Reimplemented in TQFrame and TQGLWidget.
 .SH "void TQWidget::scroll ( int dx, int dy )"
 Scrolls the widget including its children \fIdx\fR pixels to the right and \fIdy\fR downwards. Both \fIdx\fR and \fIdy\fR may be negative.
 .PP
-After scrolling, scroll() sends a paint event for the the part that is read but not written. For example, when scrolling 10 pixels rightwards, the leftmost ten pixels of the widget need repainting. The paint event may be delivered immediately or later, depending on some heuristics (note that you might have to force processing of paint events using QApplication::sendPostedEvents() when using scroll() and move() in combination).
+After scrolling, scroll() sends a paint event for the the part that is read but not written. For example, when scrolling 10 pixels rightwards, the leftmost ten pixels of the widget need repainting. The paint event may be delivered immediately or later, depending on some heuristics (note that you might have to force processing of paint events using TQApplication::sendPostedEvents() when using scroll() and move() in combination).
 .PP
 See also TQScrollView, erase(), and bitBlt().
 .SH "void TQWidget::scroll ( int dx, int dy, const TQRect & r )"
@@ -2060,7 +2060,7 @@ Be aware that if the widget is hidden, it will not accept focus.
 .PP
 \fBWarning:\fR If you call setFocus() in a function which may itself be called from focusOutEvent() or focusInEvent(), you may get an infinite recursion.
 .PP
-See also focus, clearFocus(), focusInEvent(), focusOutEvent(), focusPolicy, QApplication::focusWidget(), grabKeyboard(), and grabMouse().
+See also focus, clearFocus(), focusInEvent(), focusOutEvent(), focusPolicy, TQApplication::focusWidget(), grabKeyboard(), and grabMouse().
 .PP
 Examples:
 .)l addressbook/centralwidget.cpp, lineedits/lineedits.cpp, mdi/application.cpp, popup/popup.cpp, rot13/rot13.cpp, t8/main.cpp, and wizard/wizard.cpp.
@@ -2195,13 +2195,13 @@ See also TQSizePolicy::TQSizePolicy().
 .SH "void TQWidget::setStyle ( TQStyle * style )"
 Sets the widget's GUI style to \fIstyle\fR. Ownership of the style object is not transferred.
 .PP
-If no style is set, the widget uses the application's style, QApplication::style() instead.
+If no style is set, the widget uses the application's style, TQApplication::style() instead.
 .PP
 Setting a widget's style has no effect on existing or future child widgets.
 .PP
 \fBWarning:\fR This function is particularly useful for demonstration purposes, where you want to show Qt's styling capabilities. Real applications should avoid it and use one consistent GUI style instead.
 .PP
-See also style(), TQStyle, QApplication::style(), and QApplication::setStyle().
+See also style(), TQStyle, TQApplication::style(), and TQApplication::setStyle().
 .PP
 Examples:
 .)l progressbar/progressbar.cpp.
@@ -2352,7 +2352,7 @@ See also raise() and lower().
 .SH "TQStyle & TQWidget::style () const"
 Returns the GUI style for this widget
 .PP
-See also TQWidget::setStyle(), QApplication::setStyle(), and QApplication::style().
+See also TQWidget::setStyle(), TQApplication::setStyle(), and TQApplication::style().
 .SH "void TQWidget::styleChange ( TQStyle & oldStyle )\fC [virtual protected]\fR"
 This virtual function is called when the style of the widgets changes. \fIoldStyle\fR is the previous GUI style; you can get the new style from style().
 .PP
@@ -2360,7 +2360,7 @@ Reimplement this function if your widget needs to know when its GUI style change
 .PP
 The default implementation updates the widget including its geometry.
 .PP
-See also QApplication::setStyle(), style(), update(), and updateGeometry().
+See also TQApplication::setStyle(), style(), update(), and updateGeometry().
 .SH "void TQWidget::tabletEvent ( TQTabletEvent * e )\fC [virtual protected]\fR"
 This event handler, for event \fIe\fR, can be reimplemented in a subclass to receive tablet events for the widget.
 .PP
@@ -2475,7 +2475,7 @@ In your reimplementation of this function, if you want to stop the event being h
 .PP
 \fBWarning:\fR This function is not portable.
 .PP
-See also QApplication::winEventFilter().
+See also TQApplication::winEventFilter().
 .SH "WId TQWidget::winId () const"
 Returns the window system identifier of the widget.
 .PP
@@ -2505,7 +2505,7 @@ In your reimplementation of this function, if you want to stop the event being h
 .PP
 \fBWarning:\fR This function is not portable.
 .PP
-See also QApplication::x11EventFilter().
+See also TQApplication::x11EventFilter().
 .SH "int TQWidget::y () const"
 Returns the y coordinate of the widget relative to its parent and including any window frame. See the "y" property for details.
 .SS "Property Documentation"
@@ -2546,7 +2546,7 @@ This property holds the widget's background brush.
 .PP
 The background brush depends on a widget's palette and its background mode.
 .PP
-See also backgroundColor(), backgroundPixmap(), eraseColor(), palette, and QApplication::setPalette().
+See also backgroundColor(), backgroundPixmap(), eraseColor(), palette, and TQApplication::setPalette().
 .PP
 Get this property's value with backgroundBrush().
 .SH "BackgroundMode backgroundMode"
@@ -2634,7 +2634,7 @@ An editor widget might use an I-beam cursor:
 .PP
 If no cursor has been set, or after a call to unsetCursor(), the parent's cursor is used. The function unsetCursor() has no effect on top-level widgets.
 .PP
-See also QApplication::setOverrideCursor().
+See also TQApplication::setOverrideCursor().
 .PP
 Set this property's value with setCursor(), get this property's value with cursor(), and reset this property's value with unsetCursor().
 .SH "bool customWhatsThis"
@@ -2666,7 +2666,7 @@ This property holds whether this widget (or its focus proxy) has the keyboard in
 .PP
 Effectively equivalent to \fCqApp->focusWidget() == this\fR.
 .PP
-See also setFocus(), clearFocus(), focusPolicy, and QApplication::focusWidget().
+See also setFocus(), clearFocus(), focusPolicy, and TQApplication::focusWidget().
 .PP
 Get this property's value with hasFocus().
 .SH "bool focusEnabled"
@@ -2792,7 +2792,7 @@ The active window is the window that contains the widget that has keyboard focus
 .PP
 When popup windows are visible, this property is TRUE for both the active window \fIand\fR for the popup.
 .PP
-See also setActiveWindow() and QApplication::activeWindow().
+See also setActiveWindow() and TQApplication::activeWindow().
 .PP
 Get this property's value with isActiveWindow().
 .SH "bool isDesktop"
@@ -2800,7 +2800,7 @@ This property holds whether the widget is a desktop widget, i.e. represents the
 .PP
 A desktop widget is also a top-level widget.
 .PP
-See also isTopLevel and QApplication::desktop().
+See also isTopLevel and TQApplication::desktop().
 .PP
 Get this property's value with isDesktop().
 .SH "bool isDialog"
@@ -2932,7 +2932,7 @@ If mouse tracking is disabled (the default), the widget only receives mouse move
 .PP
 If mouse tracking is enabled, the widget receives mouse move events even if no buttons are pressed.
 .PP
-See also mouseMoveEvent() and QApplication::setGlobalMouseTracking().
+See also mouseMoveEvent() and TQApplication::setGlobalMouseTracking().
 .PP
 Set this property's value with setMouseTracking() and get this property's value with hasMouseTracking().
 .SH "bool ownCursor"
@@ -2966,7 +2966,7 @@ As long as no special palette has been set, or after unsetPalette() has been cal
 .PP
 Instead of defining an entirely new palette, you can also use the paletteBackgroundColor, paletteBackgroundPixmap and paletteForegroundColor convenience properties to change a widget's background and foreground appearance only.
 .PP
-See also ownPalette, colorGroup, and QApplication::palette().
+See also ownPalette, colorGroup, and TQApplication::palette().
 .PP
 Set this property's value with setPalette(), get this property's value with palette(), and reset this property's value with unsetPalette().
 .SH "TQColor paletteBackgroundColor"
@@ -2994,7 +2994,7 @@ This property holds the foreground color of the widget.
 .PP
 setPaletteForegroundColor() is a convenience function that creates and sets a modified TQPalette with setPalette(). The palette is modified according to the widget's \fIbackground mode\fR. For example, if the background mode is PaletteButton the palette entry TQColorGroup::ButtonText is set to color.
 .PP
-See also palette, QApplication::setPalette(), backgroundMode, foregroundColor(), backgroundMode, and setEraseColor().
+See also palette, TQApplication::setPalette(), backgroundMode, foregroundColor(), backgroundMode, and setEraseColor().
 .PP
 Set this property's value with setPaletteForegroundColor(), get this property's value with paletteForegroundColor(), and reset this property's value with unsetPalette().
 .SH "TQPoint pos"
diff --git a/doc/man/man3/tqwizard.3qt b/doc/man/man3/tqwizard.3qt
index 8db06bff3..b5a22c22a 100644
--- a/doc/man/man3/tqwizard.3qt
+++ b/doc/man/man3/tqwizard.3qt
@@ -259,7 +259,7 @@ Returns the font used for page titles. See the "titleFont" property for details.
 .SH "TQFont titleFont"
 This property holds the font used for page titles.
 .PP
-The default is QApplication::font().
+The default is TQApplication::font().
 .PP
 Set this property's value with setTitleFont() and get this property's value with titleFont().