diff options
Diffstat (limited to 'doc/threads.doc')
| -rw-r--r-- | doc/threads.doc | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/doc/threads.doc b/doc/threads.doc index dc1a61d49..b7c6043d0 100644 --- a/doc/threads.doc +++ b/doc/threads.doc @@ -71,7 +71,7 @@ library. On both platforms, you should compile with the macro \c TQT_THREAD_SUPPORT defined (e.g. compile with \c{-DTQT_THREAD_SUPPORT}). On Windows, this is usually done by an -entry in \c{ntqconfig.h}. +entry in \c{tqconfig.h}. \section1 The Thread Classes @@ -190,18 +190,18 @@ mutex must be used: \section1 Thread-safe Event Posting In Qt, one thread is always the GUI or event thread. This is the -thread that creates a QApplication object and calls -QApplication::exec(). This is also the initial thread that calls +thread that creates a TQApplication object and calls +TQApplication::exec(). This is also the initial thread that calls main() at program start. This thread is the only thread that is allowed to perform GUI operations, including generating and receiving events from the window system. TQt does not support creating -QApplication and running the event loop (with QApplication::exec()) in -a secondary thread. You must create the QApplication object and call -QApplication::exec() from the main() function in your program. +TQApplication and running the event loop (with TQApplication::exec()) in +a secondary thread. You must create the TQApplication object and call +TQApplication::exec() from the main() function in your program. Threads that wish to display data in a widget cannot modify the widget directly, so they must post an event to the widget using -QApplication::postEvent(). The event will be delivered later on by +TQApplication::postEvent(). The event will be delivered later on by the GUI thread. Normally, the programmer would like to include some information in the @@ -241,7 +241,7 @@ delivered to the object. \section1 The TQt Library Mutex -QApplication includes a mutex that is used to protect access to window +TQApplication includes a mutex that is used to protect access to window system functions. This mutex is locked while the event loop is running (e.g. during event delivery) and unlocked when the eventloop goes to sleep. Note: The TQt event loop is recursive, and the library @@ -347,9 +347,9 @@ load the normal TQt library or dynamically load another library or plugin that depends on the normal TQt library. On some systems, doing this can corrupt the static data used in the TQt library. -\i TQt does not support creating QApplication and running the event -loop (with QApplication::exec()) in a secondary thread. You must -create the QApplication object and call QApplication::exec() from the +\i TQt does not support creating TQApplication and running the event +loop (with TQApplication::exec()) in a secondary thread. You must +create the TQApplication object and call TQApplication::exec() from the main() function in your program. \endlist |