summaryrefslogtreecommitdiffstats
path: root/doc/metaobjects.doc
diff options
context:
space:
mode:
authorMichele Calgaro <michele.calgaro@yahoo.it>2023-09-23 12:42:20 +0900
committerMichele Calgaro <michele.calgaro@yahoo.it>2023-09-23 12:42:20 +0900
commitb35e0845dc9b3c8b9a5e52a682c769f383933fae (patch)
treee4eeca8f6fe0ca87e774be98eabf89b4c7fca347 /doc/metaobjects.doc
parent1ba13366a7a377d50b9e8df9044ce11d8209f98c (diff)
downloadtqt3-b35e0845dc9b3c8b9a5e52a682c769f383933fae.tar.gz
tqt3-b35e0845dc9b3c8b9a5e52a682c769f383933fae.zip
Replace QObject, QWidget, QImage, QPair, QRgb, QColor, QChar, QString, QIODevice with TQ* version
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/metaobjects.doc')
-rw-r--r--doc/metaobjects.doc26
1 files changed, 13 insertions, 13 deletions
diff --git a/doc/metaobjects.doc b/doc/metaobjects.doc
index 4403761fa..bd2612760 100644
--- a/doc/metaobjects.doc
+++ b/doc/metaobjects.doc
@@ -50,7 +50,7 @@ property system.
The Meta Object System is based on three things:
\list 1
-\i the \l QObject class;
+\i the \l TQObject class;
\i the TQ_OBJECT macro inside the private section of the class
declaration;
\i the \link moc.html Meta Object Compiler (moc)\endlink.
@@ -66,43 +66,43 @@ class's implementation.
In addition to providing the \link signalsandslots.html signals and
slots \endlink mechanism for communication between objects (the main
reason for introducing the system), the meta object code provides
-additional features in QObject:
+additional features in TQObject:
\list
-\i the \link QObject::className() className() \endlink function that
+\i the \link TQObject::className() className() \endlink function that
returns the class name as a string at runtime, without requiring
native runtime type information (RTTI) support through the C++
compiler.
-\i the \link QObject::inherits() inherits() \endlink function that
+\i the \link TQObject::inherits() inherits() \endlink function that
returns whether an object is an instance of a class that inherits a
-specified class within the QObject inheritance tree.
+specified class within the TQObject inheritance tree.
-\i the \link QObject::tr() tr() \endlink and
-\link QObject::trUtf8() trUtf8() \endlink functions for string
+\i the \link TQObject::tr() tr() \endlink and
+\link TQObject::trUtf8() trUtf8() \endlink functions for string
translation as used for internationalization.
-\i the \link QObject::setProperty() setProperty() \endlink and \link
-QObject::property() property() \endlink functions for dynamically
+\i the \link TQObject::setProperty() setProperty() \endlink and \link
+TQObject::property() property() \endlink functions for dynamically
setting and getting \link properties.html object properties\endlink by
name.
-\i the \link QObject::metaObject() metaObject() \endlink function that
+\i the \link TQObject::metaObject() metaObject() \endlink function that
returns the associated \link QMetaObject meta object \endlink for the
class.
\endlist
-While it is possible to use QObject as a base class without the
+While it is possible to use TQObject as a base class without the
TQ_OBJECT macro and without meta object code, neither signals and slots
nor the other features described here will be available if the
TQ_OBJECT macro is not used. From the meta object system's point of
-view, a QObject subclass without meta code is equivalent to its
+view, a TQObject subclass without meta code is equivalent to its
closest ancestor with meta object code. This means for example, that
className() will not return the actual name of your class, but the
class name of this ancestor. We \e strongly recommend that all
-subclasses of QObject use the TQ_OBJECT macro regardless of whether
+subclasses of TQObject use the TQ_OBJECT macro regardless of whether
they actually use signals, slots and properties or not.
*/