1 files changed, 5 insertions, 5 deletions

diff --git a/certmanager/lib/kleo/keylistjob.h b/certmanager/lib/kleo/keylistjob.h
index c419ad47d..9d566bcbc 100644
--- a/certmanager/lib/kleo/keylistjob.h
+++ b/certmanager/lib/kleo/keylistjob.h
@@ -55,17 +55,17 @@ namespace Kleo {
      and result() signals to suitable slots and then start the key
      listing with a call to start(). This call might fail, in which
      case the KeylistJob instance will have schedules it's own
-     destruction with a call to QObject::deleteLater().
+     destruction with a call to TQObject::deleteLater().
 
      During keylisting, you will receive new key objects through the
      nextKey() signal as they arrive. After result() is emitted, the
      KeyListJob will schedule it's own destruction by calling
-     QObject::deleteLater().
+     TQObject::deleteLater().
   */
   class KeyListJob : public Job {
     Q_OBJECT
   protected:
-    KeyListJob( QObject * parent, const char * name );
+    KeyListJob( TQObject * parent, const char * name );
 
   public:
    ~KeyListJob();
@@ -82,9 +82,9 @@ namespace Kleo {
        also available are returned. Use this if you need to select a
        key for signing.
     */
-    virtual GpgME::Error start( const QStringList & patterns, bool secretOnly=false ) = 0;
+    virtual GpgME::Error start( const TQStringList & patterns, bool secretOnly=false ) = 0;
 
-    virtual GpgME::KeyListResult exec( const QStringList & patterns, bool secretOnly, std::vector<GpgME::Key> & keys ) = 0;
+    virtual GpgME::KeyListResult exec( const TQStringList & patterns, bool secretOnly, std::vector<GpgME::Key> & keys ) = 0;
 
   signals:
     void nextKey( const GpgME::Key & key );