summaryrefslogtreecommitdiffstats
path: root/doc/html/metaobjects.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/metaobjects.html')
-rw-r--r--doc/html/metaobjects.html20
1 files changed, 10 insertions, 10 deletions
diff --git a/doc/html/metaobjects.html b/doc/html/metaobjects.html
index 4b0e832d9..e4e804b77 100644
--- a/doc/html/metaobjects.html
+++ b/doc/html/metaobjects.html
@@ -39,7 +39,7 @@ inter-object communication, runtime type information, and the dynamic
property system.
<p> The Meta Object System is based on three things:
<ol type=1>
-<li> the <a href="qobject.html">TQObject</a> class;
+<li> the <a href="ntqobject.html">TQObject</a> class;
<li> the Q_OBJECT macro inside the private section of the class
declaration;
<li> the <a href="moc.html">Meta Object Compiler (moc)</a>.
@@ -55,21 +55,21 @@ slots</a> mechanism for communication between objects (the main
reason for introducing the system), the meta object code provides
additional features in TQObject:
<p> <ul>
-<p> <li> the <a href="qobject.html#className">className()</a> function that
+<p> <li> the <a href="ntqobject.html#className">className()</a> function that
returns the class name as a string at runtime, without retquiring
native runtime type information (RTTI) support through the C++
compiler.
-<p> <li> the <a href="qobject.html#inherits">inherits()</a> function that
+<p> <li> the <a href="ntqobject.html#inherits">inherits()</a> function that
returns whether an object is an instance of a class that inherits a
-specified class within the <a href="qobject.html">TQObject</a> inheritance tree.
-<p> <li> the <a href="qobject.html#tr">tr()</a> and
-<a href="qobject.html#trUtf8">trUtf8()</a> functions for string
+specified class within the <a href="ntqobject.html">TQObject</a> inheritance tree.
+<p> <li> the <a href="ntqobject.html#tr">tr()</a> and
+<a href="ntqobject.html#trUtf8">trUtf8()</a> functions for string
translation as used for <a href="i18n.html#internationalization">internationalization</a>.
-<p> <li> the <a href="qobject.html#setProperty">setProperty()</a> and <a href="qobject.html#property">property()</a> functions for dynamically
+<p> <li> the <a href="ntqobject.html#setProperty">setProperty()</a> and <a href="ntqobject.html#property">property()</a> functions for dynamically
setting and getting <a href="properties.html">object properties</a> by
name.
-<p> <li> the <a href="qobject.html#metaObject">metaObject()</a> function that
-returns the associated <a href="qmetaobject.html">meta object</a> for the
+<p> <li> the <a href="ntqobject.html#metaObject">metaObject()</a> function that
+returns the associated <a href="ntqmetaobject.html">meta object</a> for the
class.
<p> </ul>
<p> While it is possible to use TQObject as a base class without the
@@ -80,7 +80,7 @@ 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 <em>strongly</em> recommend that all
-subclasses of <a href="qobject.html">TQObject</a> use the Q_OBJECT macro regardless of whether
+subclasses of <a href="ntqobject.html">TQObject</a> use the Q_OBJECT macro regardless of whether
they actually use signals, slots and properties or not.
<p>
<!-- eof -->