• Skip to content
  • Skip to link menu
KDE API Reference
  • KDE API Reference
  • kdepimlibs API Reference
  • KDE Home
  • Contact Us
 

akonadi

  • Akonadi
  • ConflictHandler
Public Types | Public Slots | Signals | Public Member Functions | List of all members
Akonadi::ConflictHandler Class Reference

#include <conflicthandler_p.h>

Inherits QObject.

Public Types

enum  ConflictType { LocalLocalConflict, LocalRemoteConflict, BackendConflict }
 
enum  ResolveStrategy { UseLocalItem, UseOtherItem, UseBothItems }
 

Public Slots

void start ()
 

Signals

void conflictResolved ()
 
void error (const QString &message)
 

Public Member Functions

 ConflictHandler (ConflictType type, QObject *parent=0)
 
void setConflictingItems (const Akonadi::Item &changedItem, const Akonadi::Item &conflictingItem)
 

Detailed Description

A class to handle conflicts in Akonadi.

Author
Tobias Koenig tokoe.nosp@m.@kde.nosp@m..org

Definition at line 39 of file conflicthandler_p.h.

Member Enumeration Documentation

enum Akonadi::ConflictHandler::ConflictType

Describes the type of conflict that should be resolved by the conflict handler.

Enumerator
LocalLocalConflict 

Changes of two Akonadi client applications conflict.

LocalRemoteConflict 

Changes of an Akonadi client application and a resource conflict.

BackendConflict 

Changes of a resource and the backend data conflict.

Definition at line 48 of file conflicthandler_p.h.

enum Akonadi::ConflictHandler::ResolveStrategy

Describes the strategy that should be used for resolving the conflict.

Enumerator
UseLocalItem 

The local item overwrites the other item inside the Akonadi storage.

UseOtherItem 

The local item is dropped and the other item from the Akonadi storage is used.

UseBothItems 

Both items are kept in the Akonadi storage.

Definition at line 57 of file conflicthandler_p.h.

Constructor & Destructor Documentation

ConflictHandler::ConflictHandler ( ConflictType  type,
QObject *  parent = 0 
)
explicit

Creates a new conflict handler.

Parameters
typeThe type of the conflict that should be resolved.
parentThe parent object.

Definition at line 34 of file conflicthandler.cpp.

Member Function Documentation

void Akonadi::ConflictHandler::conflictResolved ( )
signal

This signal is emitted whenever the conflict has been resolved automatically or by the user.

void Akonadi::ConflictHandler::error ( const QString &  message)
signal

This signal is emitted whenever an error occurred during the conflict handling.

Parameters
messageA user visible string that describes the error.
void ConflictHandler::setConflictingItems ( const Akonadi::Item &  changedItem,
const Akonadi::Item &  conflictingItem 
)

Sets the items that causes the conflict.

Parameters
changedItemThe item that has been changed, it needs the complete payload set.
conflictingItemThe item from the Akonadi storage that is conflicting. This needs only the id set, the payload will be refetched automatically.

Definition at line 41 of file conflicthandler.cpp.

void ConflictHandler::start ( )
slot

Starts the conflict handling.

Definition at line 47 of file conflicthandler.cpp.


The documentation for this class was generated from the following files:
  • conflicthandler_p.h
  • conflicthandler.cpp
This file is part of the KDE documentation.
Documentation copyright © 1996-2014 The KDE developers.
Generated on Tue Oct 14 2014 23:00:28 by doxygen 1.8.7 written by Dimitri van Heesch, © 1997-2006

KDE's Doxygen guidelines are available online.

akonadi

Skip menu "akonadi"
  • Main Page
  • Namespace List
  • Namespace Members
  • Alphabetical List
  • Class List
  • Class Hierarchy
  • Class Members
  • File List
  • Modules
  • Related Pages

kdepimlibs API Reference

Skip menu "kdepimlibs API Reference"
  • akonadi
  •   contact
  •   kmime
  •   socialutils
  • kabc
  • kalarmcal
  • kblog
  • kcal
  • kcalcore
  • kcalutils
  • kholidays
  • kimap
  • kldap
  • kmbox
  • kmime
  • kpimidentities
  • kpimtextedit
  • kresources
  • ktnef
  • kxmlrpcclient
  • microblog

Search



Report problems with this website to our bug tracking system.
Contact the specific authors with questions and comments about the page contents.

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V. | Legal