From 8ac0e970e4464d9f8f73c0fb34a178ff135be8c3 Mon Sep 17 00:00:00 2001 From: Michele Calgaro Date: Sun, 2 Jun 2024 23:07:22 +0900 Subject: Rename ntqwidget* related files to equivalent tqwidget* Signed-off-by: Michele Calgaro --- doc/html/threads.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/html/threads.html') diff --git a/doc/html/threads.html b/doc/html/threads.html index 337eef330..392d1c49c 100644 --- a/doc/html/threads.html +++ b/doc/html/threads.html @@ -207,7 +207,7 @@ apply when creating and using TQObjects in a thread that is not the GUI thread.

  1. None of the TQObject based classes included in the TQt library are -reentrant. This includes all widgets (e.g. TQWidget and +reentrant. This includes all widgets (e.g. TQWidget and subclasses), OS kernel classes (e.g. TQProcess, TQAccel, TQTimer), and all networking classes (e.g. TQSocket, TQDns).

  2. TQObject and all of its subclasses are not thread-safe. This @@ -254,7 +254,7 @@ are examples of simple GUI operations:

    Any operations that generate events must not be called by any thread other than the GUI thread. Examples of such operations are:

      -
    • creating a TQWidget, TQTimer, TQSocketNotifier, TQSocket or other network class. +
    • creating a TQWidget, TQTimer, TQSocketNotifier, TQSocket or other network class.
    • moving, resizing, showing or hiding a TQWidget.
    • starting or stoping a TQTimer.
    • enabling or disabling a TQSocketNotifier. @@ -296,7 +296,7 @@ Consult the manual of your database client for more information.

      Some things to watch out for when programming with threads:

      • As mentioned above, TQObject based classes are neither thread-safe -nor reentrant. This includes all widgets (e.g. TQWidget and +nor reentrant. This includes all widgets (e.g. TQWidget and subclasses), OS kernel classes (e.g. TQProcess, TQAccel), and all networking classes (e.g. TQSocket, TQDns).

      • Deleting a TQObject while pending events are waiting to be delivered -- cgit v1.2.1