Bugzilla – Bug 10986
Pandora: Stations can only be renamed using upper-case letters
Last modified: 2009-09-08 09:12:41 UTC
Not sure why this is. When using search, I suppose this makes sense, since search may not be case-sensitive. But on Pandora (and maybe other places), I can't use any lower-case letters when renaming a station. Solution would be to use a larger character set that includes lower-case letters.
WEB UI is able to rename using Mixed case This looks to be a player UI issue with only upper case
Please explain why this is now invalid. In the player UI, it's upper-case only. It's a bug.
Player UI text input mode does not allow you to use lower-case letters. It's always been that way. Ask Dean.
There should be two text entry modes: one for search that does only upper case, and one for entering names/text to be saved that allows mixed case.
the up/down/knob functions for INPUT::Text seems to use only the charsRef, but it looks like the number keys are using numberLettersMixed so you'd get mixed case by using the number keys. The charsets to be used can be determined by setting the charsRef and numberLettersRef when entering INPUT::Text mode. Sadly, only able to suggest. Cannot test or replicate. I don't immediately see the entry point for renaming in the Pandora Plugin.
So KDF you are saying that right now the up/down never uses this NumberLettersMixed function that would allow lower case? So the first order of business probably is to make that extended character set available to the knob navigation.
I'm saying that it's possible to change the set. Input.Text includes a selection of arrays. All of the entry points I looked over were using 'UPPER'. I cannot see the specific entry point for Pandora (there isn't much in the plugin and the XML Browser doesn't make it obvious what function leads into editing the stream name). It should be a case of modifying: 'charsRef' => 'UPPER', 'numberLetterRef' => 'UPPER', In the appropriate case to remove those, as @bothChars is default for charsRef and @numberLettersMixed is default for numberLetterRef. I can't be more specific without knowing the entry point in the code.
It would be the text input from XMLBrowser.
Thanks Andy, that's what I expected. However, the code mentions INPUT.Text only the $item->{type} eq 'search'. I couldn't be sure this was used when editting the station name. I suppose it would therefore need a way to know the difference unless entering mixed case is not considered confusing when used in a case insensitive search.
Yeah all text input areas are type='search'.
Moving 7.4 bugs to 8.0.