Den 15. juli 2012 15:27, skrev Patrick Ohly:
>> should solve the problem.
> What is it supposed to do instead?
ITEM_OKAY if add or update worked as requested, ITEM_REPLACED if the
engine asks for adding the item (luid empty) and the incoming item has a
UID/RECURRENCE-ID property which matches an existing item, in which case
the backend has to turn the "add" into an "update" to avoid
Well, I should probably also update the N900 (Maemo) backend. From what
I can tell from the calendar-backend sources, when it detects a
duplicate, it compares the last-modification times, and if the new entry
is newer, it replaces the old entry. But if the backend keeps the
existing entry and discards the incoming one, what should insertItem
return to SyncEvolution?