summaryrefslogtreecommitdiffstats
path: root/tdeparts/COMMENTS
diff options
context:
space:
mode:
Diffstat (limited to 'tdeparts/COMMENTS')
-rw-r--r--tdeparts/COMMENTS4
1 files changed, 2 insertions, 2 deletions
diff --git a/tdeparts/COMMENTS b/tdeparts/COMMENTS
index cd65e2db9..15472ac52 100644
--- a/tdeparts/COMMENTS
+++ b/tdeparts/COMMENTS
@@ -576,7 +576,7 @@ issue compared to what's above though.
delegation.
It works like this:
We have KReadOnlyPart (short KROP) and KonqyViewerExtension (short KVE). KVE is just
- a child of KROP that you can query with the QObject::child method.
+ a child of KROP that you can query with the TQObject::child method.
Views which are konquy aware feature their own implementation of KVE and konquy is
happy :-)
If a KROP does not feature a KVE then Konqui installs a default KVE that just ignores
@@ -588,7 +588,7 @@ issue compared to what's above though.
(Torben) About the fact that konqy can embed a KReadWritePart (short KRWP):
This is IMHO not a konqy problem but a KRWP design bug. KRWP overloads
KROP and changes the semantics (editing is possible). By default KRWP should
- go into ReadOnly mode. Only if one calls rwpart->setEditable( TRUE ) it should
+ go into ReadOnly mode. Only if one calls rwpart->setEditable( true ) it should
offer editing of the data. It may still happen that some KRWPs dont obeye the
"editable" flag, but that is a bug inside of the KRWP.