Bugzilla – Bug 1113
number keys on remote select wrong playlist items
Last modified: 2011-11-06 23:24:24 UTC
When this happened I had only one album in the active playlist with the track number matching the playlist item number. Trying to select a playlist item (track) via the number keys on the remote gives strange results: button selected pl item 1 1 2 2 3 3 4 5 4 6 5 8 6 9 7 10 8 11 9 12 I experimented a bit and it seems the bug triggers when switching a playlist from shuffled playlist to sorted playlist and/or vice versa via the button on the remote. The screwed-up button mapping given above is not constant, a given button might either select playlist item x or item (x+1). It's the same for shuffled and sorted mode but in shuffle mode I don't mind as much :) Maybe something does not get restored corrctly when un-shuffling a pl?
This may be behaving as designed (but we should discuss if the designed behavior should change). The idea is that for unsorted lists (like playlists) the numbers jump you proportionally (i.e. 1 takes you the beginning, 0 to the end and 5 to the middle.) Lists less than 10 long will jump to the item number (i.e. 4 will take you to the fourth item). Sorted lists jump alphabetically, (i.e. pressing 3 takes you to the first item starting with D, press it again to go to E.) Is this consistent with what you are seeing?
Yes, that's the way it behaves, AFAICS. I'd just assumed the number keys would work like on a regular CD player, selecting tracks / playlist items. The current behaviour is very practical for large playlists, confusing for small ones. Maybe the display on the sb could be changed to show "Jumping to 'A'" / "Jumping to 50%" / "Jumping to track 4" for a short time (on line 1), so the user knows what it is doing or should be doing.
Dean doesn't work here any more :)
Unassigned bugs cannot have a priority.