Bug 8489 – Boom firmware should reference the "knob" and not the "wheel" ["wheel" not the "knob"]

Bug 8489 - Boom firmware should reference the "knob" and not the "wheel" ["wheel" not the "knob"]

Summary:

Boom firmware should reference the "knob" and not the "wheel" ["wheel" not th...

Status:	CLOSED FIXED

Product:	SB Boom
Classification:	Unclassified
Component:	Setup
Version:	unspecified
Platform:	All MacOS X 10.5

Importance:	-- critical (vote)
Target Milestone:	7.3
Assigned To:	Felix Mueller

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-06-18 22:27 UTC by Jim Carlton
Modified:	2008-12-15 12:40 UTC (History)
CC List:	3 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jim Carlton 2008-06-18 22:27:15 UTC

The QSG calls it a "wheel" while the firmware calls it a "knob".  Please change the firmware to match the QSG.

Comment 1 Felix Mueller 2008-06-25 03:49:02 UTC

I need translations for wheel in all languages for this

Comment 2 Felix Mueller 2008-06-25 09:18:40 UTC

Changed english word 'knob' to 'wheel'.

This is in fw 17 (r4410)

Comment 3 Mickey Gee 2008-07-18 13:37:08 UTC

The error string "Left to go back, press center knob to try again." still has that evil k word in it. Firmware 18.

Comment 4 Felix Mueller 2008-07-21 01:05:52 UTC

Fixed in rev 4548. Will be in fw 19.

Thanks, Mickey, for spotting this.

Comment 5 James Richardson 2008-10-13 09:40:05 UTC

Robin has determined that Wheel should be re-labeled to Knob.

Comment 6 Felix Mueller 2008-10-17 06:59:17 UTC

Done in rev 5013, will be in SBB fw 37

Comment 7 James Richardson 2008-12-11 13:45:16 UTC

Verified fixed in
Boom r40

Comment 8 James Richardson 2008-12-15 12:40:29 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.