The Unbearable Persistence of Shuffle

I got sandbagged again today. In the morning I listened to a Shuffled jazz playlist and in the afternoon I tried to listen to some Mahler. We all know what happened. A shuffled symphony doesn’t make much sense.

I’ve gone through several iterations on how to address this.

Iteration #1 - Turn Shuffle off when a queue finishes. That is, the message “Go find something to play” is displayed… Problem is that, I suppose some people want Shuffle on all the time.

Iteration #2 - Have a switch that tells how one wants Shuffle to work. That is, whether it should persist until turned off or whether it should be turned off when the queue is ended. Problem is that, another switch is a kludge and a blight on society.

Iteration #3 - So simple. When a queue is started save the state of the Shuffle. When the queue ends, restore that state. If Shuffle was on to begin the queue, it will be set to on when queue ends and if off then it will be set to off.

This way everyone will be happy, but more importantly I will be happy.

This probably affects only those who listen to a mix of classical and something else, but still…

I am guessing the queue is a C++ object, so a new variable and a line of code in both the Constructor and Destructor. Give me the source and I’ll code it for you. :smirk:

2 Likes