summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/tqdialog.3qt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man/man3/tqdialog.3qt')
-rw-r--r--doc/man/man3/tqdialog.3qt8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/man/man3/tqdialog.3qt b/doc/man/man3/tqdialog.3qt
index 311cfbb59..651b632ef 100644
--- a/doc/man/man3/tqdialog.3qt
+++ b/doc/man/man3/tqdialog.3qt
@@ -13,7 +13,7 @@ TQDialog \- The base class of dialog windows
.PP
Inherits TQWidget.
.PP
-Inherited by TQColorDialog, QErrorMessage, TQFileDialog, TQFontDialog, QInputDialog, QMessageBox, QMotifDialog, QProgressDialog, QTabDialog, and QWizard.
+Inherited by TQColorDialog, QErrorMessage, TQFileDialog, TQFontDialog, QInputDialog, QMessageBox, QMotifDialog, TQProgressDialog, TQTabDialog, and TQWizard.
.PP
.SS "Public Members"
.in +1c
@@ -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 QProgressDialog.)
+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.)
.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
@@ -179,7 +179,7 @@ A modeless dialog. After the show() call, control returns to the main event loop
}
.fi
.PP
-See also QTabDialog, TQWidget, QProgressDialog, GUI Design Handbook: Dialogs, Standard, Abstract Widget Classes, and Dialog Classes.
+See also TQTabDialog, TQWidget, TQProgressDialog, GUI Design Handbook: Dialogs, Standard, Abstract Widget Classes, and Dialog Classes.
.SS "Member Type Documentation"
.SH "TQDialog::DialogCode"
The value returned by a modal dialog.
@@ -273,7 +273,7 @@ Reimplemented from TQWidget.
.SH "void TQDialog::showExtension ( bool showIt )\fC [protected slot]\fR"
If \fIshowIt\fR is TRUE, the dialog's extension is shown; otherwise the extension is hidden.
.PP
-This slot is usually connected to the QButton::toggled() signal of a TQPushButton.
+This slot is usually connected to the TQButton::toggled() signal of a TQPushButton.
.PP
A dialog with a visible extension is not resizeable.
.PP