Bug 13099 – Settings is no longer the last item in home

Bug 13099 - Settings is no longer the last item in home

Summary:

Settings is no longer the last item in home

Status:	CLOSED FIXED

Product:	SB Radio
Classification:	Unclassified
Component:	Menus
Version:	Include FW version in comment
Platform:	PC All

Importance:	P1 normal (vote)
Target Milestone:	7.4.0
Assigned To:	James Richardson

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-07-28 13:08 UTC by James Richardson
Modified:	2010-05-27 14:46 UTC (History)
CC List:	2 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 James Richardson 2009-07-28 13:08:03 UTC

r6826 Settings is now ALPHA sorting above Slacker & Sounds & Effects.

Settings should always be the last item in the Home Menu, just as Advanced should always be the last item in the Settings Menu

Comment 1 Wadzinski Tom 2009-07-29 14:34:37 UTC

I believe this has been fixed among various recent commits.

Comment 2 James Richardson 2009-08-11 09:20:33 UTC

MP r6943 has this issue.  Since we are going to do another MP firmware release, can we get the MP branch fixed so settings is the last menu item?

Comment 3 Wadzinski Tom 2009-08-11 19:37:15 UTC

Please try with the latest FW r7020. Since MP users don't use the regular menus, this would not be a issue for MP.

Comment 4 James Richardson 2009-10-05 14:31:10 UTC

This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

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 Chris Owens 2010-05-27 14:46:49 UTC

These bugs have all been marked resolved and belong to a component which is being removed.  Therefore they have been moved to the most applicable of the new components.