summaryrefslogtreecommitdiffstats
path: root/doc/html/qt-template-lib.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/qt-template-lib.html')
-rw-r--r--doc/html/qt-template-lib.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/html/qt-template-lib.html b/doc/html/qt-template-lib.html
index 54b025ad6..e5971533d 100644
--- a/doc/html/qt-template-lib.html
+++ b/doc/html/qt-template-lib.html
@@ -53,7 +53,7 @@ object code.
<p> If you cannot make copies of the objects you want to store you should
use <a href="ntqptrcollection.html">TQPtrCollection</a> and friends, all of which operate on pointers
rather than values. This applies, for example, to all classes derived
-from <a href="ntqobject.html">TQObject</a>. A <a href="ntqobject.html">TQObject</a> does not have a copy constructor, so using
+from <a href="tqobject.html">TQObject</a>. A <a href="tqobject.html">TQObject</a> does not have a copy constructor, so using
it as value is impossible. You may choose to store pointers to
TQObjects in a <a href="ntqvaluelist.html">TQValueList</a>, but using <a href="ntqptrlist.html">TQPtrList</a> directly seems to be the
better choice for this kind of application domain. TQPtrList, like all