summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/qeventloop.3qt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man/man3/qeventloop.3qt')
-rw-r--r--doc/man/man3/qeventloop.3qt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/man/man3/qeventloop.3qt b/doc/man/man3/qeventloop.3qt
index a72100022..cf7a0fee4 100644
--- a/doc/man/man3/qeventloop.3qt
+++ b/doc/man/man3/qeventloop.3qt
@@ -147,7 +147,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 QTimer with 0 timeout. More advanced idle processing schemes can be achieved using processEvents().
.PP
-See also QApplication::tquit(), exit(), and processEvents().
+See also QApplication::quit(), exit(), and processEvents().
.SH "void QEventLoop::exit ( int retcode = 0 )\fC [virtual]\fR"
Tells the event loop to exit with a return code.
.PP
@@ -157,7 +157,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::tquit() and exec().
+See also QApplication::quit() and exec().
.SH "void QEventLoop::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 QEventLoop::hasPendingEvents () const\fC [virtual]\fR"