by Barry4679 » Fri Mar 08, 2019 8:08 pm
Ludek wrote: ↑Fri Mar 08, 2019 3:32 am
we are not planning a general undo for all, but we might enhance our current Undo in toast messages after some actions.
[snip]
What do you think?
It suppose that it would be OK have an undo after some of the manual update functions, like track rating etc. ... But I think that an undo after some whole database batch functions would be even more attractive.
Examples:
- sync GPM library to MM ... maybe I didn't understand that your default setting will overwrite all my track metadata with whatever tags Google have on their tracks
- or sync GPM library to MM, including "new" tracks, and I didn't realise how much crap was in my GPM library, and now my MM database is polluted with many things that I didn't expect, and that I don't want, and have trouble identifying them amongst all my own tracks
- or I experimented with something, and now wish I had not done that thing; like auto-tag, or track levelling
Could you take a db snapshot prior to these batch functions, and offer a whole-db undo function?
I suppose that it could get confusing if the person had done a batch function which also modified the actual tracks in way that is impractical to restore.
But the menu for the batch functions, which you could undo, could be marked as being undo-able?
[quote=Ludek post_id=456483 time=1552033932 user_id=7319]
we are not planning a general undo for all, but we might enhance our current Undo in toast messages after some actions.
[snip]
What do you think?
[/quote]
It suppose that it would be OK have an undo after some of the manual update functions, like track rating etc. ... But I think that an undo after some whole database batch functions would be even more attractive.
Examples:
[list]sync GPM library to MM ... maybe I didn't understand that your default setting will overwrite all my track metadata with whatever tags Google have on their tracks[/list]
[list]or sync GPM library to MM, including "new" tracks, and I didn't realise how much crap was in my GPM library, and now my MM database is polluted with many things that I didn't expect, and that I don't want, and have trouble identifying them amongst all my own tracks [/list]
[list]or I experimented with something, and now wish I had not done that thing; like auto-tag, or track levelling[/list]
Could you take a db snapshot prior to these batch functions, and offer a whole-db undo function?
I suppose that it could get confusing if the person had done a batch function which also modified the actual tracks in way that is impractical to restore.
But the menu for the batch functions, which you could undo, could be marked as being undo-able?