Summary: | Korganizer: copy/paste of recurring items functions improperly | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Dotan Cohen <kde-2011.08> |
Component: | recurrence | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | lemma, smartins, tuju |
Priority: | NOR | Keywords: | triaged |
Version: | 3.5 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Dotan Cohen
2008-05-12 19:17:24 UTC
I can't reproduce the original bug on trunk r865573 any longer although there's some minor issues with copied/moved events which I'll file separately. While trying to reproduce in KOrganizer 4.1.0 I have discovered that the Edit -> Paste function is _always_ disabled. There seems to be no way to paste a copied event. So, this bug cannot be triaged until this issue is taken care of. See bug #172425. I confirm, if you copy-paste a recurring event you'll end up with two recurring events. I think the "only this item"/"all occurrences" popup should be shown. I agree with Sergio, the user should be asked. SVN commit 1091138 by smartins: Make cut and copy work properly for recurring incidences. Now the user is prompted which occurrences he wants to cut/copy. Added the "WhichOccurrences" enum so the caller code doesn't have to compare incidence pointers in order to know what the user chose (readability++). Fixes kolab/issue4101 kolab/issue4125 CCBUG: 162007 MERGE: trunk M +104 -13 calendarview.cpp M +21 -3 calendarview.h M +11 -6 koagenda.cpp M +1 -0 koeventeditor.cpp M +13 -0 koglobals.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1091138 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. |