Bug 46711 - yearly recurring events doesn't handle leap years
Summary: yearly recurring events doesn't handle leap years
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 3.1-beta
Platform: Compiled Sources Linux
: NOR critical
Target Milestone: ---
Assignee: Cornelius Schumacher
URL:
Keywords:
: 46086 47645 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-08-21 00:03 UTC by Jens Dagerbo
Modified: 2004-04-11 15:03 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Dagerbo 2002-08-20 23:53:48 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           korganizer
Version:           3.1beta1 (using KDE 3.0.7 1 beta1))
Severity:          normal
Installed from:    compiled sources
Compiler:          gcc version 2.95.3 20010315 (release)
OS:                Linux (i686) release 2.4.19-pre10-gentoo-r3
OS/Compiler notes: 

Create an event with no time associated for a day past february 28th mark it as recurring yearly and look for it on a leap year -> the date is one day short.

Apparently KOrganizer simply counts the days starting from Jan 1 but this is hardly what the user expects nor wishes.

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
Comment 1 Stephan Kulow 2002-09-25 22:35:41 UTC
korganizer can't hardly ship this way. all my birth days won't work. 
Comment 2 Stephan Kulow 2002-09-25 22:38:27 UTC
*** Bug 46086 has been marked as a duplicate of this bug. ***
Comment 3 Cornelius Schumacher 2002-09-29 19:34:51 UTC
Fixes in CVS. 
Comment 4 Cornelius Schumacher 2002-09-30 01:50:54 UTC
*** Bug 47645 has been marked as a duplicate of this bug. ***
Comment 5 hectorito 2003-09-08 15:51:37 UTC
Still in Korganizer 3.1.1 (using KDE 3.1.2) 
 
And if you create the event in a leap year it will be one date long in all non leap years. 
 
I have just congratulate a friend (born in the leap year 1980) one date late :-( 
Comment 6 Reinhold Kainhofer 2003-09-08 16:44:21 UTC
That's why korganizer has two different types of yearly recurrences:  
 
-) "Recur in the month of ..." means the recurrence is always on the same date 
(e.g. Sept 8, be it the 251-th or the 252-th day of the year) 
 
-) "Recur on this day" means the event recurs on the same day of the year 
(e.g. on the 251-th day of the year, which is usually Sept 8, but in leap 
years it's Sept 7). This is the button that is checked by default (which it 
shouldn't be imo). 
 
I admit the wording doesn't make that clear. I'm planning to improve the 
recurrence setting for KDE 3.2 anyway, and then I'll also try to find a better 
wording. E.g. if the event starts on Sept 8, why should we let the user choose 
to have it recur in March??? It's better to move the event to march if you 
want it to recur there.  
 
So the two options then will be: 
  ( ) recur on September 8 
  ( ) recur on the 251-th day of the year 
 
For monthly recurrences it will then be: 
  ( ) recur on the 8th day of the month 
  ( ) recur on the 2nd monday of the month 
  ( ) recur on the 4th last monday of the month 
If the start date of the event is changed, the recurrence is updates 
accordingly. 
 
Reinhold 
Comment 7 Hans Gerd Evertz 2004-04-11 15:03:37 UTC
This leap-year bug (DEFAULT of counting days of year
instead of keeping the calendar date for annually recurring events,
especially birthdays) is, in my opinion, absolutely catastrophic for use
of korganizer. This is a failure in one of the most basic features of a calendar program ! 
Such a bug removes all trust in the program...
I stopped using korganizer (angrily because of all the time invested)
when this problem occured (and a similar problem with daylight savings time)!
The only reason I'm coming back is the lack of decent other programs.
PLEASE, PLEASE, resolve such critical issues quickly. They are much more
important than all the fancy display-stuff.
Thank you !