diff options
| author | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-09-04 11:53:23 +0900 |
|---|---|---|
| committer | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-09-04 13:56:43 +0900 |
| commit | 0582c90a9ed4b965629267713f51c0da7c38b39d (patch) | |
| tree | cae95e850081d0a7f2be6cef5837f43a28d53d2c /doc/html/properties.html | |
| parent | 39f8a475b4ec5c87a11a7e9300a30ef1c5b4a7e1 (diff) | |
| download | tqt-0582c90a.tar.gz tqt-0582c90a.zip | |
Rename remaining ntq[m-r]* related files to equivalent tq* (except ntqmodules.h)
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/html/properties.html')
| -rw-r--r-- | doc/html/properties.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/html/properties.html b/doc/html/properties.html index 0ab6e463e..cc8685f85 100644 --- a/doc/html/properties.html +++ b/doc/html/properties.html @@ -76,12 +76,12 @@ function calls are equivalent: <p> Equivalent, that is, except that the first is faster, and provides much better diagnostics at compile time. When practical, the first is better. However, since you can get a list of all available properties -for any TQObject through its <a href="ntqmetaobject.html">TQMetaObject</a>, <a href="tqobject.html#setProperty">TQObject::setProperty</a>() +for any TQObject through its <a href="tqmetaobject.html">TQMetaObject</a>, <a href="tqobject.html#setProperty">TQObject::setProperty</a>() can give you control over classes that weren't available at compile time. -<p> As well as <a href="tqobject.html#setProperty">TQObject::setProperty</a>(), there is a corresponding <a href="tqobject.html#property">TQObject::property</a>() function. <a href="ntqmetaobject.html#propertyNames">TQMetaObject::propertyNames</a>() returns -the names of all available properties. <a href="ntqmetaobject.html#property">TQMetaObject::property</a>() -returns the property data for a named property: a <a href="qmetaproperty.html">TQMetaProperty</a> +<p> As well as <a href="tqobject.html#setProperty">TQObject::setProperty</a>(), there is a corresponding <a href="tqobject.html#property">TQObject::property</a>() function. <a href="tqmetaobject.html#propertyNames">TQMetaObject::propertyNames</a>() returns +the names of all available properties. <a href="tqmetaobject.html#property">TQMetaObject::property</a>() +returns the property data for a named property: a <a href="tqmetaproperty.html">TQMetaProperty</a> object. <p> Here's a simple example that shows the most important property functions in use: @@ -173,7 +173,7 @@ meta object, for example: </pre> <p> Like other meta data, class information is accessible at runtime -through the meta object, see <a href="ntqmetaobject.html#classInfo">TQMetaObject::classInfo</a>() for details. +through the meta object, see <a href="tqmetaobject.html#classInfo">TQMetaObject::classInfo</a>() for details. <p> <a name="override"></a> <h2> TQ_OVERRIDE </h2> |