by proteus » Sun Nov 05, 2023 7:36 pm
To satisfy the original request...
Yes, as the OP, I think this is exactly it.
Separately from the request
Good question, does adding to a playlist which is shuffled mean 1)
appending (in a shuffled order), 2) random
merging, or 3)
appending followed by reshuffling the whole list 4)
unshuffle existing list, append, shuffle all.
I'd say 4), but whatever keeps the internals (a the poster says for un-shuffle) as simple as possible while being consistent with the UI is the best answer.
The advantage of 4) is it also addresses the original issue too, the case where the original list is empty (possibly just deleted)
Edit: The shuffle state button should have three states: none, track, album (this changes none of the above). Then all those extra drop down menu 'play shuffled' items can be removed. If they are not removed then those menu items have to set the Shuffle button state, which would be confusing. IMHO much easier to implement and use if they are removed. As a general rule never set the same state from two places.
[quote]To satisfy the original request...[/quote]
Yes, as the OP, I think this is exactly it.
[quote]Separately from the request [/quote]
Good question, does adding to a playlist which is shuffled mean 1) [i]appending[/i] (in a shuffled order), 2) random [i]merging[/i], or 3) [i]appending followed by reshuffling[/i] the whole list 4) [i]unshuffle existing list, append, shuffle all[/i].
I'd say 4), but whatever keeps the internals (a the poster says for un-shuffle) as simple as possible while being consistent with the UI is the best answer.
The advantage of 4) is it also addresses the original issue too, the case where the original list is empty (possibly just deleted)
[b]Edit:[/b] The shuffle state button should have three states: none, track, album (this changes none of the above). Then all those extra drop down menu 'play shuffled' items can be removed. If they are not removed then those menu items have to set the Shuffle button state, which would be confusing. IMHO much easier to implement and use if they are removed. As a general rule never set the same state from two places.