From 04d353236066b9aa85f6387fa05d3d37b75a7dd2 Mon Sep 17 00:00:00 2001 From: Michele Calgaro Date: Mon, 25 Sep 2023 12:03:00 +0900 Subject: Replace QObject, QWidget, QImage, QPair, QRgb, QColor, QChar, QString, QIODevice with TQ* version Signed-off-by: Michele Calgaro (cherry picked from commit 4c0dae60b2fbc60996fc8f4bd29ee6219b869527) --- tdeparts/COMMENTS | 2 +- tdeparts/browserextension.h | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'tdeparts') diff --git a/tdeparts/COMMENTS b/tdeparts/COMMENTS index cd65e2db9..d36d98eef 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 diff --git a/tdeparts/browserextension.h b/tdeparts/browserextension.h index ac6ec27ed..027bbd87f 100644 --- a/tdeparts/browserextension.h +++ b/tdeparts/browserextension.h @@ -257,7 +257,7 @@ class BrowserExtensionPrivate; * to implement the virtual methods [and the standard-actions slots, see below]. * * The way to associate the BrowserExtension with the part is to simply - * create the BrowserExtension as a child of the part (in QObject's terms). + * create the BrowserExtension as a child of the part (in TQObject's terms). * The hosting application will look for it automatically. * * Another aspect of the browser integration is that a set of standard @@ -796,7 +796,7 @@ public: enum Type { TypeVoid=0, TypeBool, TypeFunction, TypeNumber, TypeObject, TypeString }; - typedef TQValueList > ArgList; + typedef TQValueList > ArgList; LiveConnectExtension( KParts::ReadOnlyPart *parent, const char *name = 0L ); -- cgit v1.2.1