Bugzilla – Bug 652
Jump To Next (Or Previous) Track When Removing From Now Playing Via Remote
Last modified: 2008-12-15 11:57:09 UTC
Modify the Player UI to jump to the next track when deleting tracks in Now Playing. Currently, a track can be removed from Now Playing with the remote by scrolling to the track and pressing the ADD button. What is rather bothersome about the process is the "pointer" (for lack of a better word) moves back to the beginning of the Now Playing list instead of moving to the next track in the list. This becomes very frustrating when the number of tracks in Now Playing is large and you have to rescroll past all the "keeper" tracks to get back to the point you were at prior to removing the offending track.
trying this with the recent cvs, I dont see the problem. however, I also can't seem to get the player to remove the song from the playlist at all. it seems browseplaylistindex is always undef.
Created attachment 198 [details] display next after removing a track nevermind. found the problem, and this is a simple patch to move the pointer to the next song after removing a track.
Created attachment 200 [details] keep up with current playing, but also skip when deleting last patch broke the now playing tracking of curent song. this version should allow that to work, but also just to next track for diaplay if we're deleting playlist items.
committed to cvs 18/11/04
Using the 12/18 5.4.1 nightly. Maybe I am crazy but behavior appears to be unchanged. Can someone confirm? Using the player client, add a number of tracks to Now Playing. Navigate to Now Playing. Take note of the first track in the playlist. Scroll to the middle of the playlist and press "+" to remove the track currently displayed. At this point the track will be removed and client UI will jump back to the first track in Now Playing instead of moving to the next track. This requires re-navigation to the point of deletion to continue removing undesired tracks from Now Playing.
this didn't make it into the 5.4.x branch, but it does exist in the main trunk. did it work fine for you before 5.4.1 branched off? I'll try merging this into the trunk and see about getting it committed.
This is the first update I've done since the official 5.4.0 release. When/if you get it committed I will update again to confirm behavior. Thanks.
it should be in today's build of 5.4.1
Confirmed functional in 12/23 nightly 5.4.1.
This bug has been fixed in the latest release of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.