summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/tqprogressdialog.3qt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man/man3/tqprogressdialog.3qt')
-rw-r--r--doc/man/man3/tqprogressdialog.3qt4
1 files changed, 2 insertions, 2 deletions
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