From 359640943bcf155faa9a067dde9e00a123276290 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Mon, 13 Feb 2012 17:43:39 -0600 Subject: Automated update from Qt3 --- doc/metaobjects.doc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'doc/metaobjects.doc') diff --git a/doc/metaobjects.doc b/doc/metaobjects.doc index e53c95e0..79c568b7 100644 --- a/doc/metaobjects.doc +++ b/doc/metaobjects.doc @@ -42,7 +42,7 @@ \title Meta Object System \keyword meta object -\keyword Q_OBJECT +\keyword TQ_OBJECT Qt's Meta Object System provides the signals and slots mechanism for inter-object communication, runtime type information, and the dynamic @@ -51,15 +51,15 @@ property system. The Meta Object System is based on three things: \list 1 \i the \l QObject class; -\i the Q_OBJECT macro inside the private section of the class +\i the TQ_OBJECT macro inside the private section of the class declaration; \i the \link moc.html Meta Object Compiler (moc)\endlink. \endlist The \e moc reads a C++ source file. If it finds one or more class -declarations that contain the Q_OBJECT macro, it produces another C++ +declarations that contain the TQ_OBJECT macro, it produces another C++ source file which contains the meta object code for the classes that -contain the Q_OBJECT macro. This generated source file is either +contain the TQ_OBJECT macro. This generated source file is either #included into the class's source file or compiled and linked with the class's implementation. @@ -95,14 +95,14 @@ class. \endlist While it is possible to use QObject as a base class without the -Q_OBJECT macro and without meta object code, neither signals and slots +TQ_OBJECT macro and without meta object code, neither signals and slots nor the other features described here will be available if the -Q_OBJECT macro is not used. From the meta object system's point of +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 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 Q_OBJECT macro regardless of whether +subclasses of QObject use the TQ_OBJECT macro regardless of whether they actually use signals, slots and properties or not. */ -- cgit v1.2.3