kpilot/kpilot
ActionQueue Class Reference
#include <syncStack.h>
Detailed Description
The ActionQueue is a meta-action, which handles running a bunch of SyncActions in sequence.It is a SyncAction itself, so it can even be queued on another ActionQueue.
An ActionQueue is constructed with a device
. As usual, you should connect the device's deviceReady(KPilotDeviceLink*) signal with the exec() slot -- or something to that effect. The ActionQueue will then run all the actions in the queue in sequence.
Definition at line 61 of file syncStack.h.
Public Member Functions | |
ActionQueue (KPilotDeviceLink *device) | |
virtual | ~ActionQueue () |
bool | isEmpty () const |
void | addAction (SyncAction *a) |
void | queueInit (bool checkUser=false) |
void | queueConduits (const QStringList &conduits, const SyncAction::SyncMode &e, bool local=false) |
void | queueInstaller (const QString &dir) |
void | queueCleanup () |
Protected Slots | |
void | actionCompleted (SyncAction *) |
Protected Member Functions | |
void | clear () |
SyncAction * | nextAction () |
virtual bool | exec () |
Protected Attributes | |
bool | fReady |
QString | fInstallerDir |
QStringList | fInstallerFiles |
QStringList | fConduits |
Constructor & Destructor Documentation
|
Constructor. Pass in a KPilot device link for it to act on. It is legal to pass in 0 (NULL) as a device. Definition at line 257 of file syncStack.cc. |
Member Function Documentation
|
When one action finishes, start the next one.
Definition at line 328 of file syncStack.cc. |
|
You can push your own actions onto the stack, but you should only do so if you don't call prepare().
Definition at line 81 of file syncStack.h. |
|
Call these queue*() functions to append standard functional blocks. You should at least call queueInit() and queueCleanup() to add the welcome and cleanup actions to the queue (unless you do that yourself.)
For queueInit, Definition at line 271 of file syncStack.cc. |
The documentation for this class was generated from the following files: