Bug 2367 - settings -> alarm menu shows you incorrect options
: settings -> alarm menu shows you incorrect options
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Player UI
: 6.2.0
: All All
: P2 major (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-10-25 13:14 UTC by Kevin Pearsall
Modified: 2008-12-15 11:57 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Pearsall 2005-10-25 13:14:47 UTC
str:
- go to settings -> alarm
- turn on alarm by pressing right on the off prompt
- now everything in settings -> alarm says On (Press RIGHT to turn off) instead
of what it should say
Comment 1 Kevin Pearsall 2005-10-25 13:22:11 UTC
This was reported by a reseller, Darwin from Seattle Sunglass.  His e-mail stated:
-------------
Just updated a platinum SB2 firmware with the install of 6.2.
 
I noted some peculiar screen flickers at first but when going to Settings,
Alarm.  For the 5 submenus they all say On (press right to turn off)
 
Instead of the 1 of 5 being the time and so forth.
 
Known bug?
Comment 2 KDF 2005-10-25 13:45:01 UTC
Slim/Buttons/AlarmClock.pm, line 446.  change to:
	if ($client->prefGet("alarm", $weekDay) && $browseMenuChoices[$index] eq
"ALARM_OFF") {

Comment 3 KDF 2005-10-25 20:48:28 UTC
fix committed at change 4816
Comment 4 KDF 2005-10-25 20:54:22 UTC
oops...re-opening for consideration in 6.2.1
Comment 5 KDF 2005-10-25 21:03:18 UTC
right, 6.2.1 fixed at change 4817.
Comment 6 KDF 2005-10-25 23:36:20 UTC
*** Bug 2374 has been marked as a duplicate of this bug. ***
Comment 7 Kevin Pearsall 2005-10-26 17:09:13 UTC
wow that's hot stuff, thanks for nailing that one so fast, kevin!
Comment 8 James Richardson 2008-12-15 11:57:42 UTC
This bug has been fixed in the latest release 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.