0000133: Undo function - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0000133	MMW v4	Main Panel/Toolbars/Menus	public	2003-02-24 18:59	2006-08-03 15:29

Reporter	rusty	Assigned To
Priority	high	Severity	feature	Reproducibility	always
Status	confirmed	Resolution	open

Summary	0000133: Undo function
Description	An undo function to undo any editing changes would be extremely useful. Definitely useful, but a correct implementation would probably require quite a long time. In order of priority, we'd want to be able to undo the following: 1) File operations (delete) 2) Property changes (exact file structure or new values will only be overwritten by the old ones & tags are overwritten depending on config settings) 3) File operations (rename / move) 4) copy/move/re-order among playlists 5) Add to database ... and probably much more. I think that 1), 2) and possibly 3) are far more important than anything else.
Additional Information	If we support multiple undo operations, then we'll want to modify the functionality of Playlist Sorting so that it is consistent with Now Playing sorting as described in issue 0001273.
Tags	No tags attached.

Fixed in build

jiri 2006-07-26 19:36 administrator ~0007618	I agree that this would be a nice feature, but I see its implementation as _very_ problematic, particularly because undoing some operation would require a lot of storage, complex implementation, etc., e.g.: 1) If Recycle Bin isn't enabled on given drive, MM would either emulate it or it wouldn't be possible to Undo the operation (i.e. a hole in the implementation). 3) Probably most problematic in case move or copy operation overwrites other files, we would have to backup their whole content!

rusty 2006-07-26 20:30 administrator ~0007622	I think that the limitation you describe is an acceptable one. i.e. in the event that the Recycle Bin doesn't contain all the backup files then: 'MediaMonkey is unable to undo the previous operation because the deleted files are not contained in the recycle bin [OK]'. I suggest that what might make sense is for you to indicate which functions should be undoable. Then we could have the 'Undo' function be accessible via Edit \| Undo X , and only those functions that we agree on would be listed as X. For instance you might say that it's technically impossible to Undo Auto-Organize, so there would be no such function available. In this manner the user would know that Undo is available, but it would be clear from the menu whether the last function done is undoable.

rusty 2006-08-03 15:16 administrator ~0007658	Per IM discussion, this functionality would be very complex and requires a lot of effort to implement fully. Better to defer than implement a partial solution.