Quote:
Originally Posted by ADGrant
Time zones are not just a UI feature. Adding them will require a change to the data model. Should really have been in version 1.0.
|
Quote:
Originally Posted by jbg7474
Time zones are there, they're just not exposed to the user. I proved this to myself by traveling to a different time zone. Went from Eastern to Central. Appointments moved. Entered a new appointment for later in the week when I would be back in Eastern, and moved when I went back (I had to enter it an hour earlier). So time zones are there in the data record, but new appointments always get whatever time zone the user is in right now. I agree that the time zone should be exposed to the user, but this is a UI issue, not a data model one.
|
there's no way to tell by the behavior whether the calendar's backend knows anything about timezones. it may or may not.
-just because it's not exposed doesn't mean it's there- it just means everything is defaulting to the time in whatever time zone you're in (when using network time). but it would be a trivial change- add the time zone field to the data model, and populate it with whatever time zone you're currently in (basically what it assumes right now anyways).
- just because it changes doesn't mean it's there. the phone itself knows what time zone you're in, and what time zone you were in. the calendar could be made aware of the *differences* in time zones and change the time appropriately, rather than keeping track of the 'real' time. i think this is less likely, but it wouldn't be the dumbest thing someone's programmed.