Bugzilla – Bug 7414
Selecting favorites by typing numbers should be enabled again
Last modified: 2012-04-23 01:48:06 UTC
Until the 'New Squeezenetwork' was introduced at the end of February 2008, it was possible to select any favorite radio station by: 1) pressing the 'Favorites' key on the remote, 2) pressing the desired station's number (even two digit favorites would work) and 3) confirming by pressing the 'Play' Button. Since the Squeezenetwork upgrade however, this very nice feature seems to not be available anymore. I do notice that pressing 'Favorites' followed by a number does perform some kind of selection, but the one that is made doesn't seem to make sense at all. pressing 'Favorites', '7', 'Play' for instance plays Favorite Station #28. Trying to access Station #8 or #9 jumps to Favorite #50, the last one on my current Favorites list. And typing in two-digit numbers mostly results in the first number being ignored completely. As I am totally blind, I am unfortunately unable to tell if my Squeezebox displays any kind of error message. I do know however that exactly because of my disability, this direct selection of any Favorite from my list came in very useful. In the current version, I have to scroll from station to station, always trying to remember to push the 'up' or 'down' key the right amount of times, which becomes annoying if you have 50 or more favorite stations in your list. I'd therefore appreciate if you could bring back the 'Select by number' feature for the Squezenetwork Favorite List. It by the way seems to work just fine in the 'Podcast' area. Best Regards and thanks a lot!
This is actually a bug with the new SC7 favorites system, since it now uses XMLBrowser instead of INPUT.Choice. In this mode, the number keys will select based on the initial letters in the item rather than their numeric position in the menu.
Andy - both the old favorites and XMLBrowser use INPUT.Choice The difference is that XMLBrowser sets isSorted in gotOMPL - this means that the number scroll tries jumps to the relavent letter rather than using the numbering. I actually think this is wrong as its very unlikely that all opml lists are sorted. So it could be considered as a bug in XMLBrowser?
I don't know. Dean, what would you guess the UI should do when pressing the number keys in an OPML listing?
Well, even the feature of jumping to the favorite that begins with the letter pressed on the remote does not seem to work in my case. For example: If I press Number 7, I get Station #28, which is "Spirit Edge" - so this might work, as 7 probably represents letters p, q, r and s. If, however, I push number 8 (I expect this to represent letters T, U and V, my SB plays Favorite #50, which is KAPA FM. If I press Number 3, the SB plays "His Channel", not "DRS1" or "DRS4" which I would expect if it selected according to the initial letters of the saved stations. I would really appreciate if we could find a way of going back to the "numbers select numbers" system. I mean: Every TV Remote seems to work that way :-)
If the list isn't sorted, then entering numbers should jump to that index in the list. If the list is sorted, then the number buttons should jump to the first item that starts with A after pressing 2, B after pressing 2 a second time, etc. Like keys on a phone.
Dean - so you want the xmlbrowser opml code to look at the list and decide whether it is sorted or not and hence choose the appropriate mechanism? I suspect will confuse users as it means the operation for the favorites menu will be dependant on the content. Perhaps we should have an additional opml parameter to specify whether the list should be considered as sorted? I note that at present opml is considerd as sorted and rss as unsorted..
I suggest that a "sorted" attribute be available that can indicate positively whether a list is sorted or unsorted. For lists that don't include that attribute, then a quick walk through the list can easily detect if it's sorted or not.
*** Bug 7534 has been marked as a duplicate of this bug. ***
Fixed in change 7.0.1 change 18511.
(In reply to comment #9) > Fixed in change 7.0.1 change 18511. > When will the fix be implemented? Charlie Berkey
It's done, is it not working for you?
It's still not working over here. I connect my SB to Squeezenetwork. On Squeezenetwork's web page, build 18687 is announced. Pressing numbers in my "Favorites" List still shows the weird behaviour I initially described :-(
Sorry if I wasn't clear, this bug is fixed in 7.0.1 and SN test, not on production SN yet.
Ah OK. It makes me wonder though what the 18687-like number can tell me. Are there different build numbers for Test and Stable SN?
The code is all in the same repository so the version numbers don't really tell you whether or not a particular fix is included.
Working well. Thanks! Charlie Berkey
Verified fixed in 7.0.1 - 19325
This bug has recently been fixed in the latest release of SqueezeCenter 7.0.1 Please try that version, if you still see the error, then reopen this bug. To download this version, please navigate to: http://www.slimdevices.com/su_downloads.html
Reduce number of active targets for SC
Hi, I just got a Squeezebox Radio and and am sad to report that I found the described bug still present. In fact: As far as I observed, pressing "Favorites" key activates the correct menu, but whatever numbers I press after that, no action at all seems to be taken. The only way to find a station is to scroll through it. Do you think it's possible to make the "Favorites By Number" feature work on all Squeeze Boxes, even the new ones? Tested with MySqueezebox.com and Squeezebox Server 7.6.1. Thanks, René
No sign of this bug being viewed at all. Well, let's see if I can change this by other properties besides setting the reopen tag. Here's the deal: I'd REALLY love to hear from the developers why the Radio performs so much differently in that situation! Sadly enough, Im getting rather annoyed at the lack of a response. PLEASE, STOP IGNORING! I think the previous comments describe fairly well what my problem is, so I'm not going to re-describe it now. If, however, that is what you need, let me know.