Bug 14675 – Alarm clock: Can't set every hour in 24 hour mode.

Bug 14675 - Alarm clock: Can't set every hour in 24 hour mode.

Summary:

Alarm clock: Can't set every hour in 24 hour mode.

Status:	VERIFIED FIXED

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

Importance:	P1 normal (vote)
Target Milestone:	7.4.1
Assigned To:	Ben Klaas

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-10-08 12:03 UTC by Caleb Crome
Modified:	2010-05-27 14:46 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 Caleb Crome 2009-10-08 12:03:28 UTC

http://forums.slimdevices.com/showthread.php?t=69428

Set time mode to 24 hour mode.  Customer was unable to set hour to 06.  I tried it myself and I couldn't set to 05.

Comment 1 Oppfinnar Jocke 2009-10-10 02:32:39 UTC

For me, 24-hour clock, I cannot set the alarm time to 05.

Comment 2 Oppfinnar Jocke 2009-10-10 02:35:03 UTC

(In reply to comment #1)
> For me, 24-hour clock, I cannot set the alarm time to 05.

That was for an existing alarm. If I create a new alarm, I cannot set that to 06.
Sure enough... existing alarm, cannot Set Time to 05. Add Alarm, cannot set alarm to 06.

Comment 3 SVN Bot 2009-10-12 14:18:31 UTC

 == Auto-comment from SVN commit #7847 to the jive repo by bklaas ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7847 ==

Fixed Bug: 14675
Description: fixed problem with setting alarm in 24h mode

Comment 4 Ross Levine 2009-10-13 16:56:29 UTC

Verified to be working in r7848

Comment 5 VolkerOth 2009-10-15 10:05:38 UTC

Only loosely related, but currently the 24h setting is not taken into account in the MySqueezeBox.com web interface for the Radio. While I can set alarms for my SB Classic in 24h mode via the MySqueezeBox.com, only 12h AM/PM mode is available for the radio.

Comment 6 Chris Owens 2010-05-27 14:46:47 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.