Bug 8698 - Knob reference in SB2/3 firmware
: Knob reference in SB2/3 firmware
Status: CLOSED FIXED
Product: SB Boom
Classification: Unclassified
Component: Setup
: unspecified
: All All
: -- normal (vote)
: 7.1
Assigned To: Felix Mueller
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-10 09:34 UTC by Jim McAtee
Modified: 2008-12-15 12:37 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim McAtee 2008-07-10 09:34:13 UTC
I just saw this error message on my SB2:

> Can't connect to wireless network
> Left to go back, press center knob to try again. ->

Don't know if this reference 'migrated' from the Transporter or Boom firmware.
Comment 1 Felix Mueller 2008-07-11 00:40:18 UTC
Good catch. Seems like some player specific strings slipped into the common strings file.
Comment 2 Felix Mueller 2008-07-11 00:45:08 UTC
Ok, I looked through the common strings file and it seems that eight strings (all error messages) refer to knob. I am going to copy them to the TR specific strings file and revert them in the common strings file to say 'press right' instead of 'center knob'.

BTW: Boom specific strings file is fine as in there 'knob' already got replaced by 'wheel' for this eight strings.
Comment 3 Felix Mueller 2008-07-11 02:51:09 UTC
Fixed in rev 4499, will show in SB fw 99, TR fw 47

I also fixed some missing translations.
Comment 4 Chris Owens 2008-07-30 15:29:50 UTC
This bug has now been fixed in the 7.1 release version of SqueezeCenter!  Please download the new version from http://www.slimdevices.com 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.
Comment 5 James Richardson 2008-12-15 12:37:27 UTC
This bug has been fixed in the 7.3.0 release version 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.