diff options
| author | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-08-25 15:36:25 +0900 |
|---|---|---|
| committer | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-08-29 22:23:36 +0900 |
| commit | 0917fbb5387978eb7b2e2fd68bcb6beaa8c46505 (patch) | |
| tree | 0ef68a6a92087957855c7607ac176821d10d049d /doc/html/threads.html | |
| parent | 7b1d2ad2df8cd011b487c43336aa67639fa359c9 (diff) | |
| download | tqt-0917fbb5.tar.gz tqt-0917fbb5.zip | |
Rename remaining ntq[a-c]* related files to equivalent tq* (except ntqapplication.h and ntqconfig.h)
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/html/threads.html')
| -rw-r--r-- | doc/html/threads.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/html/threads.html b/doc/html/threads.html index b3fb0f3b4..f76c459c7 100644 --- a/doc/html/threads.html +++ b/doc/html/threads.html @@ -198,7 +198,7 @@ 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 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 +event sent to the widget. See the documentation for <a href="tqcustomevent.html">TQCustomEvent</a> for more information on user-defined events. <p> <h2> Threads and <a href="tqobject.html">TQObject</a> subclasses </h2> @@ -208,7 +208,7 @@ thread. <p> <ol type=1> <p> <li> <em>None</em> of the TQObject based classes included in the TQt library are <em>reentrant</em>. This includes all widgets (e.g. <a href="tqwidget.html">TQWidget</a> and -subclasses), OS kernel classes (e.g. <a href="tqprocess.html">TQProcess</a>, <a href="ntqaccel.html">TQAccel</a>, <a href="tqtimer.html">TQTimer</a>), and +subclasses), OS kernel classes (e.g. <a href="tqprocess.html">TQProcess</a>, <a href="tqaccel.html">TQAccel</a>, <a href="tqtimer.html">TQTimer</a>), and all networking classes (e.g. <a href="tqsocket.html">TQSocket</a>, <a href="tqdns.html">TQDns</a>). <p> <li> TQObject and all of its subclasses are <em>not</em> <em>thread-safe</em>. This includes the entire event delivery system. It is important to @@ -297,7 +297,7 @@ Consult the manual of your database client for more information. <p> <ul> <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="tqwidget.html">TQWidget</a> and -subclasses), OS kernel classes (e.g. <a href="tqprocess.html">TQProcess</a>, <a href="ntqaccel.html">TQAccel</a>), and all +subclasses), OS kernel classes (e.g. <a href="tqprocess.html">TQProcess</a>, <a href="tqaccel.html">TQAccel</a>), and all networking classes (e.g. <a href="tqsocket.html">TQSocket</a>, <a href="tqdns.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 |