Bug 54949 - Feature Request - Dissociating single occurences from a recurring event
Summary: Feature Request - Dissociating single occurences from a recurring event
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Cornelius Schumacher
URL:
Keywords:
: 38569 47265 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-02-21 03:44 UTC by Tim Bates
Modified: 2004-08-14 13:41 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Patch to implement the wish (17.81 KB, patch)
2004-07-29 11:06 UTC, Reinhold Kainhofer
Details
komessagebox-1.cpp (7.46 KB, text/x-c++src)
2004-07-30 17:57 UTC, Reinhold Kainhofer
Details
komessagebox-1.h (1.56 KB, text/x-chdr)
2004-07-30 17:57 UTC, Reinhold Kainhofer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Bates 2003-02-21 03:44:29 UTC
Version:            (using KDE KDE 3.1)
Installed from:    Debian testing/unstable Packages

This is related to bug 45757 in that it has to do with changing later occurences of a recurring event.

 I would like to see a menu option on the contect menu of recurring events labeled something like 'Detach this occurence'. Clicking this would do two things:

1) Add this date to the 'exceptions' list of the recurring event; effectively the same as deleting just this occurence.
2) Create a new event exactly the same as this one, except not recurring and occuring only on this date.

This would have the effect of detaching this occurence from the recurring event, so that just this one occurence can be changed without changing all the others, eg if this week a weekly meeting has been shifted to a different time, the user can just detach this occurence and shift it without affecting the regular occurence.
Comment 1 Reinhold Kainhofer 2003-08-01 14:57:03 UTC
*** Bug 38569 has been marked as a duplicate of this bug. ***
Comment 2 Reinhold Kainhofer 2003-08-01 15:24:36 UTC
*** Bug 47265 has been marked as a duplicate of this bug. ***
Comment 3 Kevin 2003-09-03 15:34:34 UTC
One of the two duplicates of this bug has a comment about how the icalendar
format doesn't allow for rescheduling directly and that it would have to create
a new entry.  I would suggest that the Event editor dialog box include a list of
'similar' entries (e.g., ones with the same name), or, even better, perhaps by
using the extension mechanism (e.g., you could create an X-RELATED, or
X-RESCHEDULED-FROM) you could add the information directly into the box.
Comment 4 Rafał Rzepecki 2004-06-07 08:48:38 UTC
Second that.

Another useful thing would be support for additional (extraneous) occurences of a recurring event. Currently one has to create a new copy of the event.

Also, I think that the extension approach makes the most sense.
Comment 5 Reinhold Kainhofer 2004-06-21 01:01:43 UTC
CVS commit by kainhofe: 

Implement moving recurring events in the agenda. After moving such an event, the user is asked if he wants to move all events of the recurring sequence, just this single event (the event is then dissociated from the sequence and turned into a separate event), or cancel. I also implemented moving only future events, but I haven't found a message box with four buttons yet, so there is no way to execute that code yet.
If you move such a recurring event, the recurrence data needs to be updated (for weekly, monthly, and yearly recurrences), which I try to do as intuitively as possible. Please tell me if you would expect some other behavior. E.g. if you have an event that recurs monthly on the first friday, and you move it two days earlier, it will recur on the first wednesday (unless that wednesday was already in the previous month, of course).
What might be a bit confusing is weekly recurrence: if you have an event that recurs weekly on say Mon, Tue and Fri, and you move one of the events two days earlier, the event will recur on Sat, Sun, and Wed.

I also adjust the recurrence end dates, but not the exception dates. Shall these also be adjusted?

Thanks for the bug report.
Cheers,
Reinhold

CCMAIL: 45757-done@bugs.kde.org, 54949@bugs.kde.org


  M +108 -28   koagenda.cpp   1.124
  M +190 -21   koagendaview.cpp   1.155
  M +4 -0      koagendaview.h   1.70



Comment 6 Reinhold Kainhofer 2004-07-29 11:06:09 UTC
Okay, I took the time to implement the two wishes if bugs reports 54949 and 
50712:
-) In the rmb popup menu of recurring events there are now "dissociate this 
occurrence" and "dissociate future occurrences" entries which implements 
54949
-) If you delete one item in a recurring sequence, you are now asked if you 
want to delete just this one recurrence, all future ones too, or the whole 
sequence. This implements 50712.

Unfortunately, kde is in feature freeze for KDE 3.3, so I cannot apply this 
now. But I will after kde 3.3 is released. Sadly, this means that the fixes 
will not be released before kde 4.0 (or 3.4) will come out :-(((

Cheers,
Reinhold

PS: Patches are against current CVS HEAD as of 28.7.2004. The same patch is 
also attached to 50712.


Created an attachment (id=6903)
Patch to implement the wish
Comment 7 Reinhold Kainhofer 2004-07-30 17:57:23 UTC
These two files are needed by my patch. I'll commit after the feature freeze.

Reinhold


Created an attachment (id=6929)
komessagebox-1.cpp

Created an attachment (id=6931)
komessagebox-1.h
Comment 8 Reinhold Kainhofer 2004-08-14 13:41:20 UTC
CVS commit by kainhofe: 

Add functionality to allow deleting only all future events of a recurring sequence.
Also add functionality to allow separating single items or all future items from a recurring sequence into it's own incidence.

CCMAIL: 54949-done@bugs.kde.org, 50712-done@bugs.kde.org


  A            komessagebox.cpp   1.1 [GPL (v2+) (+Qt exception)]
  A            komessagebox.h   1.1 [GPL (v2+) (+Qt exception)]
  M +1 -1      Makefile.am   1.276
  M +42 -8     calendarview.cpp   1.283
  M +2 -0      calendarview.h   1.137
  M +21 -15    koagenda.cpp   1.134
  M +25 -0     koagendaitem.cpp   1.67
  M +2 -0      koagendaitem.h   1.34
  M +20 -0     koeventpopupmenu.cpp   1.20
  M +5 -0      koeventpopupmenu.h   1.14
  M +4 -0      koeventview.cpp   1.23
  M +4 -0      koviewmanager.cpp   1.63
  M +6 -0      interfaces/korganizer/baseview.h   1.28