diff options
| author | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-05-23 14:04:45 +0900 |
|---|---|---|
| committer | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-05-27 16:08:54 +0900 |
| commit | 04913ce7a46fd027856e83a96205fdc388742a19 (patch) | |
| tree | a04a117317c14854a6b91072658ba0eb3ad8b3fc /doc/html/metaobjects.html | |
| parent | c11c0f228b65f7471a26513ef8dbde413e75f8fa (diff) | |
| download | tqt-04913ce7.tar.gz tqt-04913ce7.zip | |
Rename ntqobject*.h and qobject*.cpp to tqobject*
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/html/metaobjects.html')
| -rw-r--r-- | doc/html/metaobjects.html | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/html/metaobjects.html b/doc/html/metaobjects.html index 912f679eb..cfad30736 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="ntqobject.html">TQObject</a> class; +<li> the <a href="tqobject.html">TQObject</a> class; <li> the TQ_OBJECT macro inside the private section of the class declaration; <li> the <a href="moc.html">Meta Object Compiler (moc)</a>. @@ -55,20 +55,20 @@ 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="ntqobject.html#className">className()</a> function that +<p> <li> the <a href="tqobject.html#className">className()</a> function that returns the class name as a string at runtime, without requiring native runtime type information (RTTI) support through the C++ compiler. -<p> <li> the <a href="ntqobject.html#inherits">inherits()</a> function that +<p> <li> the <a href="tqobject.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="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 +specified class within the <a href="tqobject.html">TQObject</a> inheritance tree. +<p> <li> the <a href="tqobject.html#tr">tr()</a> and +<a href="tqobject.html#trUtf8">trUtf8()</a> functions for string translation as used for <a href="i18n.html#internationalization">internationalization</a>. -<p> <li> the <a href="ntqobject.html#setProperty">setProperty()</a> and <a href="ntqobject.html#property">property()</a> functions for dynamically +<p> <li> the <a href="tqobject.html#setProperty">setProperty()</a> and <a href="tqobject.html#property">property()</a> functions for dynamically setting and getting <a href="properties.html">object properties</a> by name. -<p> <li> the <a href="ntqobject.html#metaObject">metaObject()</a> function that +<p> <li> the <a href="tqobject.html#metaObject">metaObject()</a> function that returns the associated <a href="ntqmetaobject.html">meta object</a> for the class. <p> </ul> @@ -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="ntqobject.html">TQObject</a> use the TQ_OBJECT macro regardless of whether +subclasses of <a href="tqobject.html">TQObject</a> use the TQ_OBJECT macro regardless of whether they actually use signals, slots and properties or not. <p> <!-- eof --> |