diff options
Diffstat (limited to 'doc/html/threads.html')
| -rw-r--r-- | doc/html/threads.html | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/html/threads.html b/doc/html/threads.html index 6e13f2488..337eef330 100644 --- a/doc/html/threads.html +++ b/doc/html/threads.html @@ -200,7 +200,7 @@ 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="qcustomevent.html">TQCustomEvent</a> for more information on user-defined events. -<p> <h2> Threads and <a href="ntqobject.html">TQObject</a> subclasses +<p> <h2> Threads and <a href="tqobject.html">TQObject</a> subclasses </h2> <a name="6"></a><p> The TQObject class itself is <em>reentrant</em>. However, certain rules apply when creating and using TQObjects in a thread that is not the GUI @@ -218,10 +218,10 @@ you are using TQObject in a thread that is not the GUI thread, and you are handling events sent to this object, you <em>must</em> protect all access to your data with a mutex; otherwise you may experience crashes or other undesired behavior. -<p> <li> As a corollary to the above, deleting a <a href="ntqobject.html">TQObject</a> while pending +<p> <li> As a corollary to the above, deleting a <a href="tqobject.html">TQObject</a> while pending events are waiting to be delivered can cause a crash. You must not delete the TQObject directly from a thread that is not the GUI thread. -Use the <a href="ntqobject.html#deleteLater">TQObject::deleteLater</a>() method instead, which will cause the +Use the <a href="tqobject.html#deleteLater">TQObject::deleteLater</a>() method instead, which will cause the event loop to delete the object after all pending events have been delivered to the object. <p> </ol> @@ -264,7 +264,7 @@ other than the GUI thread. Examples of such operations are: <p> <h2> Threads and Signals and Slots </h2> <a name="8"></a><p> The Signals and Slots mechanism can be used in separate threads, as -long as the rules for <a href="ntqobject.html">TQObject</a> based classes are followed. The Signals +long as the rules for <a href="tqobject.html">TQObject</a> based classes are followed. The Signals and Slots mechanism is synchronous: when a signal is emitted, all slots are called immediately. The slots are executed in the thread context that emitted the signal. @@ -295,14 +295,14 @@ Consult the manual of your database client for more information. </h2> <a name="11"></a><p> Some things to watch out for when programming with threads: <p> <ul> -<p> <li> As mentioned above, <a href="ntqobject.html">TQObject</a> based classes are neither thread-safe +<p> <li> As mentioned above, <a href="tqobject.html">TQObject</a> based classes are neither thread-safe nor reentrant. This includes all widgets (e.g. <a href="ntqwidget.html">TQWidget</a> and subclasses), OS kernel classes (e.g. <a href="ntqprocess.html">TQProcess</a>, <a href="ntqaccel.html">TQAccel</a>), and all networking classes (e.g. <a href="ntqsocket.html">TQSocket</a>, <a href="ntqdns.html">TQDns</a>). <p> <li> Deleting a TQObject while pending events are waiting to be delivered will cause a crash. If you are creating TQObjects in a thread that is not the GUI thread and posting events to these objects, you should not -delete the TQObject directly. Use the <a href="ntqobject.html#deleteLater">TQObject::deleteLater</a>() method +delete the TQObject directly. Use the <a href="tqobject.html#deleteLater">TQObject::deleteLater</a>() method instead, which will cause the event loop to delete the object after all pending events have been delivered to the object. <p> <li> Don't do any blocking operations while holding the TQt library |