Maemo 5 calendar: import RECURRENCE-IDs as EXDATEs on parent event
Tell the engine to pass us EXDATEs created for each RECURRENCE-ID in a detached recurrence. Necessary because the storage and app do not support UID/RECURRENCE-ID and thus show duplicates without this workaround. (cherry picked from commit 165ea81fca9493d0dce55b82d127ad74cf7b56af) Conflicts: src/backends/maemo/MaemoCalendarSource.h
This commit is contained in:
parent
06643196f9
commit
3cbead2b86
2 changed files with 9 additions and 0 deletions
|
@ -73,6 +73,13 @@ std::string MaemoCalendarSource::getMimeVersion() const
|
|||
}
|
||||
}
|
||||
|
||||
void MaemoCalendarSource::getSynthesisInfo(SynthesisInfo &info,
|
||||
XMLConfigFragments &fragments)
|
||||
{
|
||||
TrackingSyncSource::getSynthesisInfo(info, fragments);
|
||||
info.m_backendRule = "HAVE-EXDATE-DETACHED";
|
||||
}
|
||||
|
||||
void MaemoCalendarSource::open()
|
||||
{
|
||||
string id = getDatabaseID();
|
||||
|
|
|
@ -56,6 +56,8 @@ class MaemoCalendarSource : public TrackingSyncSource, private boost::noncopyabl
|
|||
virtual Databases getDatabases();
|
||||
virtual std::string getMimeType() const;
|
||||
virtual std::string getMimeVersion() const;
|
||||
virtual void getSynthesisInfo(SynthesisInfo &info,
|
||||
XMLConfigFragments &fragments);
|
||||
|
||||
/* implementation of TrackingSyncSource interface */
|
||||
virtual void listAllItems(RevisionMap_t &revisions);
|
||||
|
|
Loading…
Reference in a new issue