Summary | Changing time of recurring events via drag/drop broken |
Queue | Kronolith |
Queue Version | Git master |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | mrubinsk (at) horde (dot) org |
Requester | mrubinsk (at) horde (dot) org |
Created | 04/12/2011 (5200 days ago) |
Due | |
Updated | 05/06/2011 (5176 days ago) |
Assigned | 04/29/2011 (5183 days ago) |
Resolved | 05/06/2011 (5176 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
Bug: 9880Fix creating exceptions by drag/drop in month view1 files changed, 1 insertions(+), 1 deletions(-)
http://git.horde.org/horde-git/-/commit/cea4c8db70730f6d7c8163a8c2eebdef46d5fe8c
State ⇒ Assigned
Taken from Jan Schneider
Bug: 9880Fix drag/drop editing of recurring events.If a recurring event occurence is moved or the time span is changed
via drag/drop
it is now automatically added as an exception to the recurring event.
2 files changed, 99 insertions(+), 17 deletions(-)
http://git.horde.org/horde-git/-/commit/24e4771f380dabb49ade6d5eb31d4aebc2033083
enter times separately, not by dragging the entire event.
Create weekly recurring event.
Relocate one of the recurrences other than the first one by
dragging it to a later time.
This causes the entire series to disappear other then the one just edited.
seems to work fine for me.
Create weekly recurring event
Edit, for example, the third occurence byvdraggin the end time to later.
This happens because we are keeping all the *original* event's data -
like the original st time - and changing the part that changed...in
this example, making the event span a week or more.
to work fine for me.
State ⇒ Assigned
think automatically creating an exception would be the expectation here.
even smarter.
Priority ⇒ 2. Medium
Patch ⇒ No
State ⇒ Feedback
Milestone ⇒
Assigned to Michael Rubinsky
Assigned to Jan Schneider
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Changing time of recurring events via drag/drop broken
Queue ⇒ Kronolith
by using drag/drop corrupts the recurring event data. This happens
because the updateEvent call is made with the new times of the
*current* instance of the recurring event, but the data stored for a
recurring event should be the date/time of the original instance.
Not sure the best way to handle this UI-wise. The choices I see are:
(1) Automatically assume that the current instance should be edited,
and add it as an exception.
(2) Assume the entire series is being edited, and adjust the original
entry (probably not the best idea, as this would probably NOT be what
the user intended).
(3) Disable drag/drop editing of recurring events.
Thoughts?