Leap-year bug
<tirade>
You would think that programmers would have figured out leap years by now for God's sake! Especially the smart ones that are supposed to work at Apple. Hmmmm. Can't we learn these lessons and stop repeating the same bugs over and over again?!!
</tirade>
This bug appears in iCal v3.0.1. I want to warn others about this so they are not bitten by it.
Summary: When an all-day event that repeats annually is scheduled across February 28, the end date will not the same each year.
Details:
All-day events are scheduled by choosing "from" and "to" dates. In my case, during 2007, I scheduled an all-day event with a "from" date of 02/26/2007 and a "to" date of 03/01/2007. I also configured this event to repeat "Every year".
When this event appears in 2008, its "from" date appears as 02/26/2008 and its "to" date appears as 02/29/2008 (instead of the desired 03/01/2008).
It appears that iCal actually internally stores the number of days an event was originally scheduled to last, not the actual "to" date for each year. This results in anually-repeating multi-day events that span 02/28 not having a correct "to" date if the original event was scheduled for a year having a different number of days in February than the current year.
You would think that programmers would have figured out leap years by now for God's sake! Especially the smart ones that are supposed to work at Apple. Hmmmm. Can't we learn these lessons and stop repeating the same bugs over and over again?!!
</tirade>
This bug appears in iCal v3.0.1. I want to warn others about this so they are not bitten by it.
Summary: When an all-day event that repeats annually is scheduled across February 28, the end date will not the same each year.
Details:
All-day events are scheduled by choosing "from" and "to" dates. In my case, during 2007, I scheduled an all-day event with a "from" date of 02/26/2007 and a "to" date of 03/01/2007. I also configured this event to repeat "Every year".
When this event appears in 2008, its "from" date appears as 02/26/2008 and its "to" date appears as 02/29/2008 (instead of the desired 03/01/2008).
It appears that iCal actually internally stores the number of days an event was originally scheduled to last, not the actual "to" date for each year. This results in anually-repeating multi-day events that span 02/28 not having a correct "to" date if the original event was scheduled for a year having a different number of days in February than the current year.
24" Intel iMac, Mac OS X (10.5.1)