Rename ntqapplication, ntqconfig and ntqmodules files to equivalent tq*

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

1 files changed, 4 insertions, 4 deletions

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