Replace QObject, QWidget, QImage, QPair, QRgb, QColor, QChar, QString, QIODevice with TQ* version

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

1 files changed, 11 insertions, 11 deletions

diff --git a/doc/signalsandslots.doc b/doc/signalsandslots.doc
index 04c4fa966..d3c5c7c22 100644
--- a/doc/signalsandslots.doc
+++ b/doc/signalsandslots.doc
@@ -84,8 +84,8 @@ called with the signal's parameters at the right time. Signals and
 slots can take any number of arguments of any type. They are
 completely typesafe: no more callback core dumps!
 
-All classes that inherit from QObject or one of its subclasses
-(e.g. QWidget) can contain signals and slots. Signals are emitted by
+All classes that inherit from TQObject or one of its subclasses
+(e.g. TQWidget) can contain signals and slots. Signals are emitted by
 objects when they change their state in a way that may be interesting
 to the outside world. This is all the object does to communicate. It
 does not know or care whether anything is receiving the signals it
@@ -128,7 +128,7 @@ A minimal C++ class declaration might read:
 A small TQt class might read:
 
 \code
-    class Foo : public QObject
+    class Foo : public TQObject
     {
 	TQ_OBJECT
     public:
@@ -193,7 +193,7 @@ were connected to \c{a.setValue()}).
 
 A signal is emitted for \e{every} connection you make, so if you
 duplicate a connection, two signals will be emitted. You can always
-break a connection using \c{QObject::disconnect()}.
+break a connection using \c{TQObject::disconnect()}.
 
 This example illustrates that objects can work together without knowing
 about each other, as long as there is someone around to set up a
@@ -309,8 +309,8 @@ information on Qt's Meta Object System, see \link templates.html Why
 doesn't TQt use templates for signals and slots?\endlink.)
 
 The meta object contains additional information such as the object's \link
-QObject::className() class name\endlink. You can also check if an object
-\link QObject::inherits() inherits\endlink a specific class, for example:
+TQObject::className() class name\endlink. You can also check if an object
+\link TQObject::inherits() inherits\endlink a specific class, for example:
 
 \code
   if ( widget->inherits("QButton") ) {
@@ -329,8 +329,8 @@ Here is a simple commented example (code fragments from \l ntqlcdnumber.h ).
     class QLCDNumber : public QFrame
 \endcode
 
-QLCDNumber inherits QObject, which has most of the signal/slot
-knowledge, via QFrame and QWidget, and #include's the relevant
+QLCDNumber inherits TQObject, which has most of the signal/slot
+knowledge, via QFrame and TQWidget, and #include's the relevant
 declarations.
 
 \code
@@ -346,11 +346,11 @@ include the moc output in the link command.
 
 \code
     public:
-	QLCDNumber( QWidget *parent=0, const char *name=0 );
-	QLCDNumber( uint numDigits, QWidget *parent=0, const char *name=0 );
+	QLCDNumber( TQWidget *parent=0, const char *name=0 );
+	QLCDNumber( uint numDigits, TQWidget *parent=0, const char *name=0 );
 \endcode
 
-It's not obviously relevant to the moc, but if you inherit QWidget you
+It's not obviously relevant to the moc, but if you inherit TQWidget you
 almost certainly want to have the \e{parent} and \e{name}
 arguments in your constructors, and pass them to the parent
 constructor.