QGpgME
10.3.4.0000000
Qt API for GpgME
|
An abstract base class for protocol-specific jobs. More...
#include <specialjob.h>
Signals | |
void | result (const GpgME::Error &result, const QVariant &data) |
![]() | |
void | progress (const QString &what, int current, int total) |
void | done () |
Public Member Functions | |
virtual GpgME::Error | start ()=0 |
virtual GpgME::Error | exec ()=0 |
![]() | |
virtual QString | auditLogAsHtml () const |
virtual GpgME::Error | auditLogError () const |
bool | isAuditLogSupported () const |
Protected Member Functions | |
SpecialJob (QObject *parent) | |
![]() | |
Job (QObject *parent) | |
Additional Inherited Members | |
![]() | |
virtual void | slotCancel ()=0 |
![]() | |
static GpgME::Context * | context (Job *job) |
An abstract base class for protocol-specific jobs.
To use a SpecialJob, first obtain an instance from the CryptoBackend implementation, connect progress() and result() signals to suitable slots and then start the job with a call to start(). This call might fail, in which case the SpecialJob instance will have schedules its own destruction with a call to QObject::deleteLater().
After result() is emitted, the SpecialJob will schedule its own destruction by calling QObject::deleteLater().
Parameters are set using the Qt property system. More general, or constructor parameters are given in the call to QGpgME::Protocol::specialJob().
The result is made available through the result signal, and through the read-only result property, the latter of which needs to be defined in each SpecialJob subclass.
|
pure virtual |
Starts the special operation.