From f6f9c296c3f9d39a8c3d0ee64a542a47f450be28 Mon Sep 17 00:00:00 2001 From: tpearson Date: Fri, 1 Jul 2011 00:37:32 +0000 Subject: TQt4 port kpilot This enables compilation under both Qt3 and Qt4 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/kpilot@1238903 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- lib/kpilotlink.h | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'lib/kpilotlink.h') diff --git a/lib/kpilotlink.h b/lib/kpilotlink.h index 4389cb8..3816094 100644 --- a/lib/kpilotlink.h +++ b/lib/kpilotlink.h @@ -168,16 +168,17 @@ class PilotDatabase; * with a non-zero timeout and that timeout has elapsed. The * tickler is stopped before timeout is emitted. */ -class KDE_EXPORT KPilotLink : public QObject +class KDE_EXPORT KPilotLink : public TQObject { Q_OBJECT + TQ_OBJECT friend class SyncAction; public: /** A list of DBInfo structures. */ typedef TQValueList DBInfoList; /** Constructor. Use reset() to start looking for a device. */ - KPilotLink( TQObject *parent = 0, const char *name = 0 ); + KPilotLink( TQObject *tqparent = 0, const char *name = 0 ); /** Destructor. This rudely interrupts any communication in progress. * It is best to call endOfSync() or finishSync() before destroying @@ -381,7 +382,7 @@ signals: * time startTickle() is called, you can state how long * tickling should last (at most) before timing out. * - * You can only get a timeout when the Qt event loop is + * You can only get a timeout when the TQt event loop is * running, which somewhat limits the usefulness of timeouts. */ void timeout(); -- cgit v1.2.1