Originally Posted by
gfunkdave
I don't understand the problem. If I set an appointment in my phone at 2pm when I'm in New York, then if I fly to Chicago that same meeting will show in my phone at 1pm. Is this not the behavior you want?
Technically, it's the right behavior due to the time zone differences however when people are referring to appointments in a different state/time zone they are usually referring to the destination time zone. In your case, if the appointment is set at 2 pm in NY with alerts scheduled 30 minutes prior to 2 then as you travel/fly to Chicago you will actually arrive early to your meeting and wonder if it was canceled.
Let's say you live in LA, you have a meeting in NYC at 3:30 PM (in NYC), the said meeting is added to iCal in LA, and you are one that highly depends on the notifications/alerts. With TZS off and without the floater setting, your meeting will now move to 6:30 PM as you travel east (when in reality the appointment is still at 3:30 PM EST). Inevitably you will be late to this meeting.
Originally Posted by
boberonicus
Your approach sounds solid. But there is no way to set "floating" as the default time zone for a new event. So you'd have to remember to modify each event as/after you create it, which is painful and prone to failure.
I wouldn't say it's exactly painful, but more of an inconvenience to the end user. It's just an extra couple of clicks/swipes.