Update to latest tqt3 automated conversion

1 files changed, 9 insertions, 9 deletions

diff --git a/doc/html/objecttrees.html b/doc/html/objecttrees.html
index a7ea7c3ac..fb1aa594a 100644
--- a/doc/html/objecttrees.html
+++ b/doc/html/objecttrees.html
@@ -33,16 +33,16 @@ body { background: #ffffff; color: black; }
 
 
 
-<p> <a href="qobject.html">TQObjects</a> organize themselves in object trees.
-When you create a <a href="qobject.html">TQObject</a> with another object as parent, it's added to
-the parent's <a href="qobject.html#children">children()</a> list, and
+<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
 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="qaccel.html">TQAccel</a> (keyboard
+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="qobject.html#objectTrees">TQObject::objectTrees</a>() provides access to all
+<p> The static function <a href="ntqobject.html#objectTrees">TQObject::objectTrees</a>() provides access to all
 the root objects that currently exist.
-<p> <a href="qwidget.html">TQWidget</a>, the base class of everything that appears on the screen,
+<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
 child widget, i.e. it is displayed in its parent's coordinate system
 and is graphically clipped by its parent's boundaries. For example,
@@ -52,10 +52,10 @@ we'd want, because the buttons and label are children of the message
 box.
 <p> You can also delete child objects yourself, and they will remove
 themselves from their parents. For example, when the user removes a
-toolbar it may lead to the application deleting one of its <a href="qtoolbar.html">TQToolBar</a>
-objects, in which case the tool bar's <a href="qmainwindow.html">TQMainWindow</a> parent would
+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="qobject.html#dumpObjectTree">TQObject::dumpObjectTree</a>() and <a href="qobject.html#dumpObjectInfo">TQObject::dumpObjectInfo</a>() are often useful when an application looks or
+<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
 acts strangely.
 <p> 
 <!-- eof -->