Automated update from Qt3

1 files changed, 22 insertions, 22 deletions

diff --git a/doc/threads.doc b/doc/threads.doc
index f05fe8d07..ee91ba305 100644
--- a/doc/threads.doc
+++ b/doc/threads.doc
@@ -1,11 +1,11 @@
 /****************************************************************************
 **
 **
-** Qt thread support
+** TQt thread support
 **
 ** Copyright (C) 1992-2008 Trolltech ASA.  All rights reserved.
 **
-** This file is part of the Qt GUI Toolkit.
+** This file is part of the TQt GUI Toolkit.
 **
 ** This file may be used under the terms of the GNU General
 ** Public License versions 2.0 or 3.0 as published by the Free
@@ -14,7 +14,7 @@
 ** Alternatively you may (at your option) use any later version
 ** of the GNU General Public License if such license has been
 ** publicly approved by Trolltech ASA (or its successors, if any)
-** and the KDE Free Qt Foundation.
+** and the KDE Free TQt Foundation.
 **
 ** Please review the following information to ensure GNU General
 ** Public Licensing requirements will be met:
@@ -47,7 +47,7 @@
 
 Qt provides thread support in the form of basic platform-independent
 threading classes, a thread-safe way of posting events, and a global
-Qt library lock that allows you to call Qt methods from different
+Qt library lock that allows you to call TQt methods from different
 threads.
 
 This document is intended for an audience that has knowledge of, and
@@ -57,7 +57,7 @@ threading see our \link #reading Recommended Reading\endlink list.
 
 \section1 Enabling Thread Support
 
-When Qt is installed on Windows, thread support is an option on some
+When TQt is installed on Windows, thread support is an option on some
 compilers. 
 
 On Mac OS X and Unix, thread support is enabled by adding the
@@ -75,7 +75,7 @@ entry in \c{ntqconfig.h}.
 
 \section1 The Thread Classes
 
-These classes are built into the Qt library when thread support is enabled:
+These classes are built into the TQt library when thread support is enabled:
 
 \list
 \i QThread - Provides the means to start a new thread, which begins
@@ -100,7 +100,7 @@ woken up by another thread.
 \target reentrant
 \target threadsafe
 
-When using Qt in a multithreaded program, it is important to
+When using TQt in a multithreaded program, it is important to
 understand the definition of the terms \e reentrant and \e
 thread-safe:
 
@@ -116,7 +116,7 @@ shared data.  Calling a thread-safe function simultaneously with the
 same data is safe, since all access to the shared data are serialized.
 \endlist
 
-Note that Qt provides both implictly and explicitly shared
+Note that TQt provides both implictly and explicitly shared
 classes. For more information, see the \link
 threads.html#threads-shared Threads and Shared Data \endlink
 section.
@@ -194,7 +194,7 @@ thread that creates a QApplication object and calls
 QApplication::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.  Qt does not support creating
+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.
@@ -216,7 +216,7 @@ thread.
 
 \list 1
 
-\i \e None of the QObject based classes included in the Qt library are
+\i \e None of the QObject based classes included in the TQt library are
 \e reentrant.  This includes all widgets (e.g. QWidget and
 subclasses), OS kernel classes (e.g. QProcess, QAccel, QTimer), and
 all networking classes (e.g. QSocket, QDns).
@@ -239,16 +239,16 @@ delivered to the object.
 
 \endlist
 
-\section1 The Qt Library Mutex
+\section1 The TQt Library Mutex
 
 QApplication 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 Qt event loop is recursive, and the library
+goes to sleep.  Note: The TQt event loop is recursive, and the library
 mutex is \e not unlocked when re-entering the event loop (e.g. when
 executing a modal dialog with QDialog::exec()).
 
-If another thread locks the Qt library mutex, then the event loop will
+If another thread locks the TQt library mutex, then the event loop will
 stop processing events, and the locking thread may do simple GUI
 operations.  Operations such as creating a QPainter and drawing a line
 are examples of simple GUI operations:
@@ -290,7 +290,7 @@ context that emitted the signal.
 
 \warning Slots that generate window system events or use window system
 functions \e must \e not be connected to a signal that is emitted from
-a thread that is not the GUI thread.  See the Qt Library Mutex section
+a thread that is not the GUI thread.  See the TQt Library Mutex section
 above for more details.
 
 \target threads-shared
@@ -299,7 +299,7 @@ above for more details.
 Qt provides many implicitly shared and explicitly shared classes.  In
 a multithreaded program, multiple instances of a shared class can
 reference shared data, which is dangerous if one or more threads
-attempt to modify the data.  Qt provides the QDeepCopy class, which
+attempt to modify the data.  TQt provides the QDeepCopy class, which
 ensures that shared classes reference unique data.
 
 See the description of \link shclass.html implicit sharing\endlink for more
@@ -334,20 +334,20 @@ delete the QObject directly.  Use the QObject::deleteLater() method
 instead, which will cause the event loop to delete the object after
 all pending events have been delivered to the object.
 
-\i Don't do any blocking operations while holding the Qt library
+\i Don't do any blocking operations while holding the TQt library
 mutex.  This will freeze up the event loop.
 
 \i Make sure you unlock a recursive QMutex as many times as you lock
 it, no more and no less.
 
-\i Don't mix the normal Qt library and the threaded Qt library in your
+\i Don't mix the normal TQt library and the threaded TQt library in your
 application.  This means that if your application uses the threaded Qt
-library, you should not link with the normal Qt library, dynamically
-load the normal Qt library or dynamically load another library or
-plugin that depends on the normal Qt library.  On some systems, doing
-this can corrupt the static data used in the Qt library.
+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.
 
-\i Qt does not support creating QApplication and running the event
+\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
 main() function in your program.