summaryrefslogtreecommitdiffstats
path: root/doc/html/ntqprogressdialog.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/ntqprogressdialog.html')
-rw-r--r--doc/html/ntqprogressdialog.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/html/ntqprogressdialog.html b/doc/html/ntqprogressdialog.html
index d8ee3b536..dda71b3b3 100644
--- a/doc/html/ntqprogressdialog.html
+++ b/doc/html/ntqprogressdialog.html
@@ -117,7 +117,7 @@ behavior.
<p> There are two ways of using TQProgressDialog: modal and modeless.
<p> Using a modal TQProgressDialog is simpler for the programmer, but you
must call <a href="ntqapplication.html#processEvents">TQApplication::processEvents</a>() or
-<a href="ntqeventloop.html#processEvents">TQEventLoop::processEvents</a>(ExcludeUserInput) to keep the event loop
+<a href="tqeventloop.html#processEvents">TQEventLoop::processEvents</a>(ExcludeUserInput) to keep the event loop
running to ensure that the application doesn't freeze. Do the
operation in a loop, call <a href="#setProgress">setProgress</a>() at intervals, and check
for cancellation with <a href="#wasCanceled">wasCanceled</a>(). For example: