QGpgME
10.3.4.0000000
Qt API for GpgME
|
A convenience class bundling together multiple DeleteJobs. More...
#include <multideletejob.h>
Signals | |
void | result (const GpgME::Error &result, const GpgME::Key &errorKey) |
![]() | |
void | progress (const QString &what, int current, int total) |
void | done () |
Public Member Functions | |
MultiDeleteJob (const Protocol *protocol) | |
GpgME::Error | start (const std::vector< GpgME::Key > &keys, bool allowSecretKeyDeletion=false) |
void | slotCancel () Q_DECL_OVERRIDE |
![]() | |
virtual QString | auditLogAsHtml () const |
virtual GpgME::Error | auditLogError () const |
bool | isAuditLogSupported () const |
Additional Inherited Members | |
![]() | |
![]() | |
static GpgME::Context * | context (Job *job) |
![]() | |
Job (QObject *parent) | |
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 QObject::deleteLater().
After result() is emitted, the MultiDeleteJob will schedule it's own destruction by calling QObject::deleteLater().
GpgME::Error QGpgME::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.