summaryrefslogtreecommitdiffstats
path: root/doc/threads.doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/threads.doc')
-rw-r--r--doc/threads.doc6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/threads.doc b/doc/threads.doc
index c4751f0c5..dc1a61d49 100644
--- a/doc/threads.doc
+++ b/doc/threads.doc
@@ -205,7 +205,7 @@ QApplication::postEvent(). The event will be delivered later on by
the GUI thread.
Normally, the programmer would like to include some information in the
-event sent to the widget. See the documentation for QCustomEvent for
+event sent to the widget. See the documentation for TQCustomEvent for
more information on user-defined events.
\section1 Threads and TQObject subclasses
@@ -218,7 +218,7 @@ thread.
\i \e None of the TQObject based classes included in the TQt library are
\e reentrant. This includes all widgets (e.g. TQWidget and
-subclasses), OS kernel classes (e.g. TQProcess, QAccel, TQTimer), and
+subclasses), OS kernel classes (e.g. TQProcess, TQAccel, TQTimer), and
all networking classes (e.g. TQSocket, TQDns).
\i TQObject and all of its subclasses are \e not \e thread-safe. This
@@ -324,7 +324,7 @@ Some things to watch out for when programming with threads:
\i As mentioned above, TQObject based classes are neither thread-safe
nor reentrant. This includes all widgets (e.g. TQWidget and
-subclasses), OS kernel classes (e.g. TQProcess, QAccel), and all
+subclasses), OS kernel classes (e.g. TQProcess, TQAccel), and all
networking classes (e.g. TQSocket, TQDns).
\i Deleting a TQObject while pending events are waiting to be delivered