[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date

[bugzilla_noreply at kde.org]

https://bugs.kde.org/show_bug.cgi?id=345565

gjditchfield at acm.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |RESOLVED
      Latest Commit|                            |https://invent.kde.org/fram
                   |                            |eworks/kcalendarcore/commit
                   |                            |/dc7b1865c3bff04d0173505335
                   |                            |da22cefa3b5f5f
         Resolution|---                         |FIXED

--- Comment #6 from gjditchfield at acm.org ---
Git commit dc7b1865c3bff04d0173505335da22cefa3b5f5f by Glen Ditchfield.
Committed on 10/06/2020 at 15:17.
Pushed by winterz into branch 'master'.

Fix serialization of recurring to-do's start date

KCalendarCore uses Todo::Private::mDtRecurrence to hold the start date
and time of the next uncompleted occurrance of a recurring Todo, and
deserializes it from the X-KDE-LIBKCAL-DTRECURRENCE property of iCalendar
files.  However, ICalFormatImpl::writeTodo() serializes dtDue() into that
property, not dtStart().

When KOrganizer creates a new recurring to-do, it serializes the to-do,
then deserializes it to populate the To-Do List view, so the view shows
an incorrect start date (and an incorrect due date, which is calculated
from the start date).
Related: bug 345498

M  +1    -0    autotests/CMakeLists.txt
A  +83   -0    autotests/testdateserialization.cpp     [License: LGPL(v3.0+)]
A  +19   -0    autotests/testdateserialization.h     [License: LGPL(v3.0+)]
M  +2    -3    src/icalformat_p.cpp

https://invent.kde.org/frameworks/kcalendarcore/commit/dc7b1865c3bff04d0173505335da22cefa3b5f5f

-- 
You are receiving this mail because:
You are the assignee for the bug.