You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified that MXLCalendarManager does not take into account daylight saving time to determine an event start and end time. Here is an example.
Suppose you have an event starting Sunday March 23 2014 at 2.00 AM, ending at 3.00 AM and recurring each week until the end of the year. Now, in Italy, on Sunday 30 there will be the daylight saving time change exactly at 2.00 AM (because we are at +1 hour offset from GMT). So, the clock at 2.00AM must be set to 3.00 AM. The net effect on the previous event is that the event on Sunday 30 in Italy will start at 3.00 AM and will end at 4.00 AM due to daylight saving time. This will happen only on Sunday 30; on all of the other occurrences the event will start at 2.00 AM and will end at 3.00 AM (note that on Sunday October 26 2014, daylight saving time will change again in Italy, but since this time at 3.00 AM we set the clock at 2.00 AM, the event will occur from 2.00 AM to 3.00 AM).
You can verify this entering the previous event on any iCalendar compliant calendaring app, such as Calendar on Mac OS X Mavericks (just modify the event according to your country daylight saving time). So, a compliant calendaring app must handle event start/end times overlapping (fully or partially) daylight saving times. Timezones are strictly related, since each timezone can have an arbitrary daylight saving time (see the official database, available at http://www.iana.org/time-zones or, informally, http://www.worldtimezone.com/daylight.html)
The text was updated successfully, but these errors were encountered:
I have verified that MXLCalendarManager does not take into account daylight saving time to determine an event start and end time. Here is an example.
Suppose you have an event starting Sunday March 23 2014 at 2.00 AM, ending at 3.00 AM and recurring each week until the end of the year. Now, in Italy, on Sunday 30 there will be the daylight saving time change exactly at 2.00 AM (because we are at +1 hour offset from GMT). So, the clock at 2.00AM must be set to 3.00 AM. The net effect on the previous event is that the event on Sunday 30 in Italy will start at 3.00 AM and will end at 4.00 AM due to daylight saving time. This will happen only on Sunday 30; on all of the other occurrences the event will start at 2.00 AM and will end at 3.00 AM (note that on Sunday October 26 2014, daylight saving time will change again in Italy, but since this time at 3.00 AM we set the clock at 2.00 AM, the event will occur from 2.00 AM to 3.00 AM).
You can verify this entering the previous event on any iCalendar compliant calendaring app, such as Calendar on Mac OS X Mavericks (just modify the event according to your country daylight saving time). So, a compliant calendaring app must handle event start/end times overlapping (fully or partially) daylight saving times. Timezones are strictly related, since each timezone can have an arbitrary daylight saving time (see the official database, available at http://www.iana.org/time-zones or, informally, http://www.worldtimezone.com/daylight.html)
The text was updated successfully, but these errors were encountered: