[REQ] Save Control for Auto Playlist Editor
Posted: Tue Nov 28, 2023 11:03 pm
Hi,
A minor UI request.
The editor for Auto Playlists has a "Discard" option at top represented by a cross, but there is no equivalent "Save" option that could be represented by a tick. In the absence of a specific "Save" option the user is invited to make the assumption that clicking away from the editor will automatically save the configured playlist.
This is fine if it does allways work like that, but one time I found that the auto playlist editor did not save the setup and I nearly synced 12,000 songs into MMA because the editor had abandoned the constraints that I had selected. I have since invoked and checked the editor and the auto playlist several times and the configuration for that playlist has now stuck (at least until next time I check it), but I would have been happier if I could have explicitly told MM5 to save the configuration that I had just established.
Letting configuration saves happen by inference might be seen as a convenience, but the only people who can be confident of that behaviour are the dialog programmers. The moment something unexpected happens, your users will be losing confidence in the product.
So, I suggest that you make available a Save control in the Auto Playlist. As a more general suggestion, you might consider making all necessary controls explicit.
Thanks
Matt
A minor UI request.
The editor for Auto Playlists has a "Discard" option at top represented by a cross, but there is no equivalent "Save" option that could be represented by a tick. In the absence of a specific "Save" option the user is invited to make the assumption that clicking away from the editor will automatically save the configured playlist.
This is fine if it does allways work like that, but one time I found that the auto playlist editor did not save the setup and I nearly synced 12,000 songs into MMA because the editor had abandoned the constraints that I had selected. I have since invoked and checked the editor and the auto playlist several times and the configuration for that playlist has now stuck (at least until next time I check it), but I would have been happier if I could have explicitly told MM5 to save the configuration that I had just established.
Letting configuration saves happen by inference might be seen as a convenience, but the only people who can be confident of that behaviour are the dialog programmers. The moment something unexpected happens, your users will be losing confidence in the product.
So, I suggest that you make available a Save control in the Auto Playlist. As a more general suggestion, you might consider making all necessary controls explicit.
Thanks
Matt