kpilot Library API Documentation

ActionQueue Class Reference

The constructor with one parameter is preferred. More...

#include <syncStack.h>

List of all members.

Public Types

enum  SyncModes {
  Test = 0, Backup = 1, Restore = 2, HotSync = 4,
  WithBackup = 0x10, WithUserCheck = 0x20, WithInstaller = 0x40, WithConduits = 0x80,
  FlagPCToHH = 0x100, FlagHHToPC = 0x200, FlagLocal = 0x1000, FlagFull = 0x2000,
  FlagTest = 0x4000, ActionMask = 0xf, MixinMask = 0xf0, FlagMask = 0xff00,
  TestMode = Test | WithUserCheck | WithConduits | FlagTest, BackupMode = Backup | WithUserCheck | WithConduits | WithBackup, RestoreMode = Restore | WithUserCheck, HotSyncMode = HotSync | WithUserCheck | WithConduits
}

Public Methods

 ActionQueue (KPilotDeviceLink *device)
virtual ~ActionQueue ()
bool isEmpty () const
void addAction (SyncAction *a)
void queueInit (int mode=WithUserCheck)
void queueConduits (KConfig *, const QStringList &conduits, int mode=0)
void queueInstaller (const QString &dir, const QStringList &files)
void queueCleanup ()

Protected Slots

void actionCompleted (SyncAction *)

Protected Methods

void clear ()
SyncAction * nextAction ()
virtual bool exec ()

Protected Attributes

bool fReady
KConfig * fConfig
QString fInstallerDir
QStringList fInstallerFiles
QStringList fConduits


Detailed Description

The constructor with one parameter is preferred.

You can call the public member functions to enqueue actions in several standard ways.

Definition at line 97 of file syncStack.h.


Member Function Documentation

void ActionQueue::addAction SyncAction *    a [inline]
 

You can push your own actions onto the stack, but you should only do so if you don't call prepare().

Definition at line 122 of file syncStack.h.

References QPtrQueue::enqueue().

Referenced by queueInit().

void ActionQueue::queueInit int    mode = WithUserCheck
 

Call these queue*() functions to append standard functional blocks.

They're pretty much mutually exclusive with the prepare*() functions above.

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, relevant modes are WithUserCheck (and 0 for no check). For queueConduits, whatever is relevant for the conduits can be used, usually things in the FlagMask and ActionMask.

Definition at line 331 of file syncStack.cc.

References addAction().

void ActionQueue::actionCompleted SyncAction *    [protected, slot]
 

When one action finishes, start the next one.

Definition at line 384 of file syncStack.cc.

References QObject::connect(), QObject::name(), and QTimer::singleShot().


The documentation for this class was generated from the following files:
KDE Logo
This file is part of the documentation for kpilot Library Version 3.2.2.
Documentation copyright © 1996-2004 the KDE developers.
Generated on Sat May 1 11:36:50 2004 by doxygen 1.2.15 written by Dimitri van Heesch, © 1997-2003