summaryrefslogtreecommitdiffstats
path: root/doc/html/objecttrees.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/objecttrees.html')
-rw-r--r--doc/html/objecttrees.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/html/objecttrees.html b/doc/html/objecttrees.html
index fb1aa594..62783f34 100644
--- a/doc/html/objecttrees.html
+++ b/doc/html/objecttrees.html
@@ -33,14 +33,14 @@ body { background: #ffffff; color: black; }
-<p> <a href="ntqobject.html">TQObjects</a> organize themselves in object trees.
-When you create a <a href="ntqobject.html">TQObject</a> with another object as parent, it's added to
-the parent's <a href="ntqobject.html#children">children()</a> list, and
+<p> <a href="tqobject.html">TQObjects</a> organize themselves in object trees.
+When you create a <a href="tqobject.html">TQObject</a> with another object as parent, it's added to
+the parent's <a href="tqobject.html#children">children()</a> list, and
is deleted when the parent is. It turns out that this approach fits
the needs of GUI objects very well. For example, a <a href="ntqaccel.html">TQAccel</a> (keyboard
accelerator) is a child of the relevant window, so when the user closes
that window, the accelerator is deleted too.
-<p> The static function <a href="ntqobject.html#objectTrees">TQObject::objectTrees</a>() provides access to all
+<p> The static function <a href="tqobject.html#objectTrees">TQObject::objectTrees</a>() provides access to all
the root objects that currently exist.
<p> <a href="ntqwidget.html">TQWidget</a>, the base class of everything that appears on the screen,
extends the parent-child relationship. A child normally also becomes a
@@ -55,7 +55,7 @@ themselves from their parents. For example, when the user removes a
toolbar it may lead to the application deleting one of its <a href="ntqtoolbar.html">TQToolBar</a>
objects, in which case the tool bar's <a href="ntqmainwindow.html">TQMainWindow</a> parent would
detect the change and reconfigure its screen space accordingly.
-<p> The debugging functions <a href="ntqobject.html#dumpObjectTree">TQObject::dumpObjectTree</a>() and <a href="ntqobject.html#dumpObjectInfo">TQObject::dumpObjectInfo</a>() are often useful when an application looks or
+<p> The debugging functions <a href="tqobject.html#dumpObjectTree">TQObject::dumpObjectTree</a>() and <a href="tqobject.html#dumpObjectInfo">TQObject::dumpObjectInfo</a>() are often useful when an application looks or
acts strangely.
<p>
<!-- eof -->