diff options
Diffstat (limited to 'doc/html/threads.html')
| -rw-r--r-- | doc/html/threads.html | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/html/threads.html b/doc/html/threads.html index 9d4444352..492080901 100644 --- a/doc/html/threads.html +++ b/doc/html/threads.html @@ -82,7 +82,7 @@ against this library (with <tt>-ltqt-mt</tt>) rather than the standard TQt library. <p> On both platforms, you should compile with the macro <tt>TQT_THREAD_SUPPORT</tt> defined (e.g. compile with <tt>-DTQT_THREAD_SUPPORT</tt>). On Windows, this is usually done by an -entry in <tt>ntqconfig.h</tt>. +entry in <tt>tqconfig.h</tt>. <p> <h2> The Thread Classes </h2> <a name="3"></a><p> These classes are built into the TQt library when thread support is enabled: @@ -184,8 +184,8 @@ mutex must be used: <p> <h2> Thread-safe Event Posting </h2> <a name="5"></a><p> In TQt, one thread is always the GUI or event thread. This is the -thread that creates a <a href="ntqapplication.html">TQApplication</a> object and calls -<a href="ntqapplication.html#exec">TQApplication::exec</a>(). This is also the initial thread that calls +thread that creates a <a href="tqapplication.html">TQApplication</a> object and calls +<a href="tqapplication.html#exec">TQApplication::exec</a>(). 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 @@ -194,7 +194,7 @@ a secondary thread. You must create the TQApplication object and call TQApplication::exec() from the main() function in your program. <p> Threads that wish to display data in a widget cannot modify the widget directly, so they must post an event to the widget using -<a href="ntqapplication.html#postEvent">TQApplication::postEvent</a>(). The event will be delivered later on by +<a href="tqapplication.html#postEvent">TQApplication::postEvent</a>(). The event will be delivered later on by the GUI thread. <p> Normally, the programmer would like to include some information in the event sent to the widget. See the documentation for <a href="tqcustomevent.html">TQCustomEvent</a> for @@ -226,7 +226,7 @@ delivered to the object. <p> </ol> <p> <h2> The TQt Library Mutex </h2> -<a name="7"></a><p> <a href="ntqapplication.html">TQApplication</a> includes a mutex that is used to protect access to window +<a name="7"></a><p> <a href="tqapplication.html">TQApplication</a> 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 @@ -238,7 +238,7 @@ operations. Operations such as creating a <a href="tqpainter.html">TQPainter</a are examples of simple GUI operations: <p> <pre> ... - tqApp-><a href="ntqapplication.html#lock">lock</a>(); + tqApp-><a href="tqapplication.html#lock">lock</a>(); <a href="tqpainter.html">TQPainter</a> p; p.<a href="tqpainter.html#begin">begin</a>( mywidget ); @@ -246,7 +246,7 @@ are examples of simple GUI operations: p.<a href="tqpainter.html#drawLine">drawLine</a>( 0,0,100,100 ); p.<a href="tqpainter.html#end">end</a>(); - tqApp-><a href="ntqapplication.html#unlock">unlock</a>(); + tqApp-><a href="tqapplication.html#unlock">unlock</a>(); ... </pre> @@ -314,8 +314,8 @@ library, you should not link with the normal TQt library, dynamically 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. -<p> <li> TQt does not support creating <a href="ntqapplication.html">TQApplication</a> and running the event -loop (with <a href="ntqapplication.html#exec">TQApplication::exec</a>()) in a secondary thread. You must +<p> <li> TQt does not support creating <a href="tqapplication.html">TQApplication</a> and running the event +loop (with <a href="tqapplication.html#exec">TQApplication::exec</a>()) in a secondary thread. You must create the TQApplication object and call TQApplication::exec() from the main() function in your program. <p> </ul> |