Issue with undoing unsuccessful copy/paste actions #1748

New issue

Closed

opened 2013-08-03 15:08:19 +00:00 by rlx · 2 comments

rlx commented

2013-08-03 15:08:19 +00:00

Owner

Only the successful parts of the action should be undone/redone.

(Currently, undoing a paste of item X into a list with item X will remove item X.)

Can the copy/paste callback manipulate the history to achieve this?

Alternatively, can we filter the items on the client before making the API call?

Only the successful parts of the action should be undone/redone. (Currently, undoing a paste of item X into a list with item X will remove item X.) Can the copy/paste callback manipulate the history to achieve this? Alternatively, can we filter the items on the client before making the API call?

rlx added the

frontend

label 2013-08-03 15:08:19 +00:00

rlx added this to the 13.04 milestone 2013-08-03 15:08:19 +00:00

rlx self-assigned this 2013-08-03 15:08:19 +00:00

rlx added the

normal

defect

labels 2013-08-03 15:08:19 +00:00

rlx commented

2013-08-04 10:13:48 +00:00

Author

Owner

Undoing a partially successful move is more complicated, as items that did not exist in the target list have to be moved back, while items that did exist have to be copied back.

Undoing clip copy/paste is difficult too, as one adds by clip properties, but removes by ID.

Undoing a partially successful move is more complicated, as items that did not exist in the target list have to be moved back, while items that did exist have to be copied back. Undoing clip copy/paste is difficult too, as one adds by clip properties, but removes by ID.

rlx commented

2013-08-04 11:28:37 +00:00

Author

Owner

Fixed. Clip copy/paste should be filed as a separate issue.

rlx added the

fixed

label 2013-08-04 11:28:37 +00:00

rlx closed this issue

2013-08-04 11:28:37 +00:00