Changed behavior of 'Stop After Current', when "Reset stop-after-current when stopping" is not enabled Options

[Robertina]

With activated option "Stop After Current" foobar 0.9.6.8 exactly does what the option's name says.

With earlier versions of foobar2000 with Columns UI the cursor does NOT move to the next track in the playlist but remains on the file of which playing has been finished.

Is there a possibility to return to that former behavior with Columns UI?

I am listening with foobar to podcasts which I am deleting apart after hearing. Now for each file I have to move the cursor one position in the playlist back to delete the file I have heard completely.

I remember that this topic has been discussed before but till yet only DUI users have been affected. That's why I am posting my question in the "third party plugins / CUI"-forum. As well I have read foobar's change log: "Fixed weird behaviors of the 'stop after current' option."

Robertina.

foobar2000 v0.9.6.8, CUI v0.3.7.3

[Marijn van der Z...]

A (late) big thanks from me too. Case, you're awesome.

I also think the old behavior made much more sense. I'm using stop after/on current for rating and cleaning up my collection. I play a song till the end and after that I decide what to do with it. Now it is possible for me to rate a song and then play the next one, using only keyboard shortcuts.

An annoying thing the Case's component fixes has to do with autoplaylists in combination with shuffled playback. I use an autoplaylist with unrated songs and like to shuffle through it whil rating the songs. When I rate the previous song or song before that, the song leaves the playlist, which changes the playback order! This is annoying if I already heard the 'next' one or two songs, but obviously isn't relevant when I haven't.

I'm not sure if people can follow that last part, but the important part is that I'm unhappy with Foobar's default behavior and happy with Case's component