[This is not something we need to resolve for Preview. Just trying to
understand the issues so we can accurately capture them to include in
the list of known issues/bugs.]
Okay, so the workflow goes something like this:
User has not turned on time zones in Chandler.
+ Alarms are set to the system time zone, both custom alarms and
event-date-dependent alarms.
User turns on time zones and selects a default time zone.
+ All existing events are assigned this time zone.
+ Alarms' absolute times *change* so that they fire at the same time
as before, but are displayed in the new time zone.
- 3PM America/Los_Angeles (System time zone); becomes
- 6PM America/New_York (New default time zone).
+ What about event-date-dependent alarms? My 3PM Floating event is
now 3PM America/Los Angeles. When does my 15-minute before alarm
fire? It used to fire at 2:45PM America/Los_Angeles. Does it now fire
at 5:45PM America/New_York (that would be weird?) or 2:45PM America/
New_York?
+ If the latter is true, then there is a difference between the way
custom alarms and event-date-dependent alarms behave when users turn
on time zone support.
+ If the former is true, then I think we have a bug ;o)
Option 1: I wonder if custom alarms should just always adhere to the
system clock's time zone. Why? People sometimes change the default
time zone just to see their calendar from a different perspective.
So let's say you're in Auckland, NZ attending the semi-annual People-
Living-In-Time-Zones-That-Are-Off-By-A-Half-Hour Unite! and you want
to see the OSAF Office Calendar in Pacific_Rim_South/New_Zealand/
Auckland time zone (what an awesome time zone!) because you're too
jet-lagged to do the math and you need to call into the staff
meeting. While you're in Auckland time, you remember a task you need
to do when you get back to the Bay Area and set a custom alarm to
fire end-of-day, the day you get back. That custom alarm will be set
to Auckland time, no?
When you get back to the Bay Area, you re-set your time zone to
America/Los_Angeles, but who knows when that custom alarm is going to
fire!
Option 2: So...if it's hard to keep the custom alarm time zones in
sync with the system clock...could we always set them to the 1st
default time zone the user defines? Or is that not something we store?
Option 3: OR, we could add another field to the DV! and have a time
zone pulldown for custom alarms.
Mimi
On May 17, 2007, at 3:57 PM, Grant Baillie wrote:
On 17 May, 2007, at 15:23, Mimi Yin wrote:
Hi Grant,
If I have a note + custom alarm date set for Today at 3PM, when
does the alarm fire?
I'm interested in understanding...
+ How the time zone I picked for the calendar canvas affects the
alarm time zone.
+ How changing that time zone affects the alarm.
+ How my system clock affects the alarm.
Howdy
[Background: When you first launch Chandler, Chandler sets its
default timezone to be your system timezone. The only way to change
that default timezone is by changing the dropdown in the calendar:
In particular, if you change your system timezone, Chandler doesn't
change].
If you set an alarm, it's set in Chandler's current default
timezone. This is true even if you haven't enabled timezones (i.e.
we don't create the alarm with a “floating” timezone).
If you change Chandler's default timezone, the alarm time isn’t
converted to the new timezone.
While double-checking at this, I noticed a detail view bug: The
alarm doesn't display in the new default timezone ... i.e. if you
set it for 3PM while in America/New_York, then change the default
to America/Los_Angeles, then it still says 3PM (even though it’s
going to fire at noon in your new timezone).
--Grant
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
