Version: (using KDE KDE 3.5.1) Installed from: Slackware Packages OS: Linux Imagine an event is created which recurs on a single day of week (e.g. a class which recurs on every Wednesday at 12:00). When this event is moved to another day (e.g. Thursday 10:00) by dragging the event to the appropriate date and choosing to move 'All ocurrences', the recurrence options do not change. So you end up with an event whose start date is next Thursday 10:00 but which is set to recur on all Wednesdays just like before moving the events. This is rather counterintuitive. I think much better behavior would be to automatically modify a weekly event when it is moved so that moving it to e.g. Thursday would also make all recurrences happen on Thursdays.
Am Sonntag, 12. März 2006 09:32 schrieb Micha
Yes, I agree with your remarks. How about at least issuing a warning if the moved event uses recurrence, e.g. 'The event you are moving uses recurrence. Moving this event to another date can result in unexpected changes to future recurrence dates. Would you like to adjust recurrence settings now? [Adjust recurrence] [Don't adjust recurrence] [Cancel moving]'
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list.
The same issue of the recurrence not being updated appears in the event editor dialog when you use the date combo box to select a new date for a recurring event... Cheers, Rienhold
*** Bug 54074 has been marked as a duplicate of this bug. ***
I have a class scheduled twice a week and encountered this bug when trying to reschedule one of the days to a different day and time. The behavior that seems intuitive to me is that after clicking on "Only future items", all future recurrences on that one day alone would be rescheduled and have the time changed, i.e. all future Mondays would be reschuled to the new time on Tuesdays while the Wednesdays stay on Wednesdays at their original time.
*** Bug 147443 has been marked as a duplicate of this bug. ***
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.