Den 29. sep. 2011 13:17, skrev Patrick Ohly: > Here's a possible solution which is perhaps not too hideous: > 1. introduce a new RECURRENCE-IDS field: an array of time stamps, > similar to EXDATE > 2. map it to an iCalendar 2.0 X-SYNCEVOLUTION-RECURRENCE-ID > property which is only used internally > 3. the CalDAV backends and ActiveSync backends create such > properties in the parent VEVENT > 4. the Synthesis engine passes it through to the Maemo 5 backend > (thanks to points 1 and 2) > 5. the Maemo 5 backend treats it like EXDATE when storing > > Retrieving an updated parent event from the Maemo 5 backend then will > add normal EXDATEs to the CalDAV server, which is redundant, but not > wrong. > > How does that sound?
Hmm. I suppose that'd work (though I'd have to learn what APIs to use to make the backend convert these properties). It'd perhaps be better if the added EXDATEs could be automatically stripped later, but if you don't think they're going to hurt... I've gotten another problem with recurrences, though; after changing some stuff around in Google Calendar, including rescheduling a single instance of a recurrent weekly appointment to a different day, I get the fatal error "new CalDAV item does not have right RECURRENCE-ID". I suppose that might also be related to Maemo 5 not storing RECURRENCE-IDs? I can send the logs privately... _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
