That makes some sense, but I have to say, I'm still a bit confused: Spanning Sync must have some mechanism for prioritizing sync information, right? In other words, are you suggesting that anytime an event is created in another application, it will acquire the notification characteristics of THAT application, rather than maintaining the original notifications? That doesn't seem to mesh with what actually happens. When I originally create an event in Google Calendar, and it syncs to iCal, it maintains the original notification scheme from Google—it doesn't
acquire the notification scheme from iCal when it's "created" by Spanning Sync in iCal. And vice versa. Which is kind of my problem.
Because Google Calendar allows for a much more robust system of default notifications on a per-calendar basis, I can set default notification schemes for each calendar—so that, say, my "Birthdays" calendar notifies me (by default) 7 days in advance, so I can send a card, whereas my "Appointments" calendar notifies me one hour in advance so I can get on the road. What I would like ideally is to dictate which system's notification scheme is used when syncing, so that regardless of where the event was created (whether in iCal, Google Calendar), the event would use Google's default notification scheme for the particular calendar on which it is created.
Does that make sense? If so, that does seem like it might be a Spanning Sync issue, and not an issue of how Google Calendar (or iCal) originally creates events. Of course, this all may be my misunderstanding of the way the syncing process works. If so, maybe you can explain?
-Celeste