Re: Libkcal Recurrence updates

Am Thursday 23 May 2002 22:44 schrieb David Jarvie:
> I have made some substantial revisions to the libkcal recurrence handling.
> The existing API is unchanged, but some new methods have been added. The
> notable changes are:
>
> -- endDate() calculates the recurrence end date as necessary. So its return
> value is valid whether the recurrence is configured with a duration or an
> end date.
>
> -- duration is now interpreted in terms of the number of occurrences of the
> event, not the number of time periods which repeat. So for example, a
> recurrence with a duration of 6 for a 3-times weekly recurrence will end
> after 2 weeks. Previously, it ended after 6 weeks. This change is to
> conform to RFC2445.
>
> -- Additional recurrence modes are now handled: Minutely, Hourly and
> YearlyPos. These are so far untested, but I expect to test them out soon
> and hopefully fix any bugs.
>
> -- There is a backwards compatibility mode (specified by compiling with
> -DLIBKCAL_BACK_COMPAT) which will interpret old-style KOrganizer-generated
> calendar files and convert them to the new format. The libkcal Makefile.am
> now includes this compile option.
>
> -- a number of bugs have been fixed.
nice.
I don't want to sound rude but it seems that libkcal is somewhat buggy. At 
least this is my impression. 
David could you fix Incidence::clone() as well? It seems to loose Categories 
(even if copied in the copy c'tor ) and Recurrence? If cloning you will loose 
your recurrence which is rather bad


thanks 
Holger
>
> Cornelius - I checked KOrganizer's code to see if any changes are needed,
> but couldn't spot any. You may like to check it out for yourself in case
> anything has been broken.

_______________________________________________
kde-pim mailing list
kde-pim@xxxxxxxxxxxx
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/