Rename ntqapplication, ntqconfig and ntqmodules files to equivalent tq*

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

1 files changed, 5 insertions, 5 deletions

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"