This is the problem:
Let's say that my playlist consists of:

song 1
song 2
song 3
song 4
song 5

Then let's say that I have selected "default" or as the order of play.
Now, let's say that I'm listening to song 1, and I want to change something in the tag of song 4. I go and change something, and I leave the song selected. The bug (feature?) now comes into view: instead of song 2, Foobar starts playing song 4.
AFAIK, skipping from song 1 to song 2 definitely isn't in the spirit of the "default" play order. I have also noticed that this happens in the "random" order of play.
It would be great if, in some future version, this is fixed.

thanks!

Uncheck Playback/Follow Cursor. And the playlist will be played in the order you have choosen.

Not a bug.

Please do play around with your copy of Foobar a lot more... the 'Follow cursor' feature is just one of many nifty ones. Don't blame anyone if you crash anything though .

I guess that this "follow cursor" feature has been added in v0.7.1?

Wrong. It was already in v0.586, the first release I used. And was with no doubt already in previous releases too.

I have unchecked "follow cursor" but it still plays the tracks in the currently selected playlist. I want to select a track in i.e. "Rock" Playlist and then switch to "Trance" playlist and the song is finished it should change to the next track in my "Rock" playlist.

You will have to wait until that functionality is implemented. (and it will most likely break the current API.)

What does that mean? "Break the current API"

There is one global playlist used for the active display and for playing. The playlist switcher clears it and fills it up whenever you switch playlists.

However it is done, separating the visible playlist from the playing one will break any components that use the current playlist manipulation and callback services, which means they will have to be rewritten.

Not that I don't want this feature, but I expect that it will mean a lot of work for some component authors. I'm not sure that Peter would leave in the old interfaces, as older components might misbehave if they only have access to the visible playlist, or to the playing list.


Meh, this will probably turn out okay, or something.