Thanks Matt, I've figured out how everything hangs together now. It's just that the spec is so lose and the docs are so vague and inconsistent that I don't know if I can wrap a clean bug free implementation around it. The half use of iCal RFC2445 Recurrence is one thing but there are so many "IF this DO that" that the code gets to be extremely fragile. And since I think that this will be enhanced later (by Google) our code would break and that's not pretty for an end user application...
I'm thinking about giving up on the recurrence part atm. Cheers, Mikael On Nov 16, 1:04 pm, "MPH" <[EMAIL PROTECTED]> wrote: > Cheers Mikael > > I still don't know why RecurrenceExceptions field is always null. But I > did find out how to handle exceptions. There is a field called > originalEvent. This contains the GUID of the recurring appointment that > the exception belongs to and its original start time. This means that > you have to go through all your feeds and pick out the ones where > originalEvent is not null then match them all back to thier original > recurring appointments and add the dates to that recurring appointments > ExDates list. > > Also exceptions that were deleted have a Status of "cancelled" and ones > that were just changed are set to "confirmed". --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
