From 970e6dc6586a9fd7d6de11e41d1f851059bfb288 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Wed, 21 Dec 2011 14:05:50 -0600 Subject: Rename obsolete tq methods to standard names --- lib/options.h | 2 +- lib/pilotAddress.h | 2 +- lib/plugin.h | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) (limited to 'lib') diff --git a/lib/options.h b/lib/options.h index 6a643e9..d8dcc0c 100644 --- a/lib/options.h +++ b/lib/options.h @@ -155,7 +155,7 @@ KDE_EXPORT struct tm writeTm(const TQDateTime &dt); KDE_EXPORT struct tm writeTm(const TQDate &dt); -// Some tqlayout macros +// Some layout macros // // SPACING is a generic distance between visual elements; // 10 seems reasonably good even at high resolutions. diff --git a/lib/pilotAddress.h b/lib/pilotAddress.h index 40b5630..db0f18c 100644 --- a/lib/pilotAddress.h +++ b/lib/pilotAddress.h @@ -314,7 +314,7 @@ public: protected: // Get the pointers in cases where no conversion to - // tqunicode is desired. + // unicode is desired. // const char *getFieldP(int field) const { diff --git a/lib/plugin.h b/lib/plugin.h index b4eb59f..f1dbec8 100644 --- a/lib/plugin.h +++ b/lib/plugin.h @@ -70,8 +70,8 @@ namespace Pilot * NB. The reason that this is a TQObject which needs to create a * separate widget - instead of a TQWidget subclass - has to do with * layouting. If you make the widget with designer then the easiest -* thing to do is to use a grid tqlayout there. Making ConduitConfigBase -* a TQWidget subclass would require an additional tqlayout here, which +* thing to do is to use a grid layout there. Making ConduitConfigBase +* a TQWidget subclass would require an additional layout here, which * seems a little foolish. * */ -- cgit v1.2.1