Yes. I am also seeing this kind of behaviour.
The google documentation for Exceptions is too old. I have posted about this on this group as well but nobody has responded on it from Google yet. ----- Original Message ---- From: Dave <[EMAIL PROTECTED]> To: Google Calendar Data API <[email protected]> Sent: Thursday, August 9, 2007 8:41:43 AM Subject: Orphaned Recurrence Exceptions If you create a repeating event with a recurrence exception in Google Calendar, then delete "all" occurrences of the repeating event, the recurrence exception will remain behind, an undeleted orphan. This behavior is at odds with other calendars I'm synching with where recurrence exceptions are deleted along with the original event. The GData documentation also implies that recurrence exceptions should not be orphaned: http://code.google.com/apis/gdata/elements.html#gdRecurrenceException > Regardless of whether an exception is specialized or not, if you do something > that > deletes the instance that the exception was derived from, then the exception > is deleted. Would you consider fixing this problem? Here are steps to reproduce it. 1. In Google Calendar, create a daily repeating event 8/6 through 8/10 2. Move event on 8/8 to 8/15 3. Select first event and delete all 4. The recurrence exception on 8/15 will not be deleted ____________________________________________________________________________________ Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
