certmanager/lib

#include <deletejob.h>

Inheritance diagram for Kleo::DeleteJob:
Kleo::Job

Signals

void result (const GpgME::Error &result)
- Signals inherited from Kleo::Job
void progress (const TQString &what, int current, int total)
void done ()

Public Member Functions

virtual GpgME::Error start (const GpgME::Key &key, bool allowSecretKeyDeletion=false)=0
- Public Member Functions inherited from Kleo::Job
virtual void showErrorDialog (TQWidget *parent=0, const TQString &caption=TQString()) const
virtual TQString auditLogAsHtml () const
virtual GpgME::Error auditLogError () const
bool isAuditLogSupported () const

Protected Member Functions

 DeleteJob (TQObject *parent, const char *name)
- Protected Member Functions inherited from Kleo::Job
 Job (TQObject *parent, const char *name)

Additional Inherited Members

- Public Slots inherited from Kleo::Job
virtual void slotCancel ()=0

Detailed Description

An abstract base class for asynchronous deleters.

To use a DeleteJob, first obtain an instance from the CryptoBackend implementation, connect the progress() and result() signals to suitable slots and then start the delete with a call to start(). This call might fail, in which case the DeleteJob instance will have scheduled it's own destruction with a call to TQObject::deleteLater().

After result() is emitted, the DeleteJob will schedule it's own destruction by calling TQObject::deleteLater().

Definition at line 58 of file deletejob.h.

Member Function Documentation

virtual GpgME::Error Kleo::DeleteJob::start ( const GpgME::Key &  key,
bool  allowSecretKeyDeletion = false 
)
pure virtual

Starts the delete operation.

key represents the key to delete, allowSecretKeyDeletion specifies if a key may also be deleted if the secret key part is available, too.


The documentation for this class was generated from the following file: