Respect time zones in ICS files about giggity HOT 5 CLOSED

I'll have to make some time to study this more accurately.. I did spend some time last year to make Giggity more useful with the remote conferences that come with our current "exciting" time, see 12f60c7. It mentions Pentabarf only because (IIRC) Pentabarf files have a single timezone in the header of the file.

Possibly what's missing is grabbing the timezone for an ICS file as long as there is just one. And I think the limited ICS parser of Giggity does parse timezone offsets if they're there, but not yet timezone strings (which is easier to do when there's a single timezone setting for the whole file, instead of having to re-initialise a timezone-aware parser for every time field you read).

Can you confirm that, other than there not being a GUI, the timezone awareness for Pentabarf files is sensible/usable to you?

from giggity.

I don't have pentabarf-style files for IETF.

Looking at MiniDebConf India (which is pentabarf style), the times are shown correctly, indicating a start of sessions at 06:30 in my local time zone (whereas the sessions started 11:00 Indian time which is +05:30). I can't verify that the green current-time indicator and notifications work (for lack of a current pentabarf conference), but things'd have to be quite odd for this not to work. Things adjust instantly when I switch around time zones on my phone settings (that is, after re-entering the event view; switching back after a TZ change moves me to the giggity main menu which is probably a good thing).

(In contrast, with the ICS calendar of IETF, changing local device time zones has no effect on the displayed start and end times, but the "current time" marker gets moved around, and is accurate relative to the slots when I select the conference time zone as my phone's time zone).

from giggity.

Brief correction from a recent observation from the ICS-based IETF calendar: The notification about imminent meetings does arrive at the right time: I see a "in 11 min" notification in the tray about an event that, in the block schedule, has long been switched to the salmon orange of past events.

from giggity.

Things adjust instantly when I switch around time zones on my phone settings (that is, after re-entering the event view; switching back after a TZ change moves me to the giggity main menu which is probably a good thing).

Heh, yeah that's my stop gap fix ac3aabc at work. Once timezone awareness is complete I might in fact be able to deal with tz changes a little more subtly again. :)

Thanks for the details on how the ICS is going wrong. Can't really get it fixed before the IETF week ends, but hopefully for future events.

from giggity.

a079f48 fixed timezone conversions I Believ.

from giggity.