| Summary: | monthly To-do given incorrect start and due dates | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kcalendarcore | Reporter: | gjditchfield |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bberberov+kde, karsten.defreese, mikael79, simonandric5 |
| Priority: | NOR | ||
| Version: | 5.71.0 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/frameworks/kcalendarcore/commit/dc7b1865c3bff04d0173505335da22cefa3b5f5f | Version Fixed In: | |
| Sentry Crash Report: | |||
|
Description
gjditchfield
2015-03-25 02:32:11 UTC
Using openSUSE Tumbleweed; Korganizer version is 5.4.1. Slightly different behavior now. The start date and end date are the same. Still an issue. I can confirm this issue with KOrganizer 5.3 KDE Applications 16.08.2 OpenSUSE leap 42.2 also for other frequencies of recurrence. When setting up a non-recurring to-do, everything seems to work as expected - I can set start dates, due dates and reminders without the different settings influencing each other. However if the to-do is set to recurring, response to the settings is erratic. An example: - I set up a to-do, starting the next day (at a specific time), and due one day later. A reminder is set at 15min before due time. - the to-do is shown correctly in the to-do list view, and also more detailed via the 'show' context menu entry - when I add a weekly recurrence, start and due dates are mysteriously moved by two days in the to-do list view, while via the 'show' context menu only the due date is shifted, and only by one day.. In other cases I've also seen the reminder being changed in addition, recurrence setting being greyed out, or also an error messages when trying to save the modified task (something like 'only allocated resources are allowed to make changes', I can't reproduce this right now). The behavior does seem independent of the calendar type I select - local personal calendar vs. CalDAV Problem still exists in Korganizer 5.4.3 still an issue with Korganizer 5.12.3 (I'm using Tumbleweed) It appears that the problems can be worked around under specific conditions: - have start & due dates on the same day (e.g. via different times) - save the to-do before entering the recurrence 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 345565 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 *** Bug 376170 has been marked as a duplicate of this bug. *** |