#include <multideletejob.h>
Signals | |
| void | result (const GpgME::Error &result, const GpgME::Key &errorKey) |
 Signals inherited from Kleo::Job | |
| void | progress (const TQString &what, int current, int total) |
| void | done () |
Public Member Functions | |
| MultiDeleteJob (const CryptoBackend::Protocol *protocol) | |
| GpgME::Error | start (const std::vector< GpgME::Key > &keys, bool allowSecretKeyDeletion=false) |
| 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 |
Additional Inherited Members | |
| Public Slots inherited from Kleo::Job | |
| virtual void | slotCancel ()=0 |
| Protected Member Functions inherited from Kleo::Job | |
| Job (TQObject *parent, const char *name) | |
Detailed Description
A convenience class bundling together multiple DeleteJobs.
To use a MultiDeleteJob, pass it a 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 MultiDeleteJob instance will have scheduled it's own destruction with a call to TQObject::deleteLater().
After result() is emitted, the MultiDeleteJob will schedule it's own destruction by calling TQObject::deleteLater().
Definition at line 67 of file multideletejob.h.
Member Function Documentation
◆ start()
| GpgME::Error Kleo::MultiDeleteJob::start | ( | const std::vector< GpgME::Key > & | keys, |
| bool | allowSecretKeyDeletion = false |
||
| ) |
Starts the delete operation.
keys is the list of keys to delete, allowSecretKeyDeletion specifies if a key may also be deleted if the secret key part is available, too.
Definition at line 63 of file multideletejob.cpp.
The documentation for this class was generated from the following files: