QA to investigate and assign

Matt, could you make a ruling for us on whether this is the behavior we should have?

I think at the very least we should have an alarm indicator in the clock screensaver.  It's clearly needed, whether or not it satisfies this bug entirely.

Also keep in mind we will be adding a lot of new functionality to now playing screensavers post-7.4.

Assigning to Noah.  We'll need reference screens for this (Noah is on vacation for the next week).

The directive, Noah, is to have an alarm indicator (off/on states - leave it to you whether the "off" state needs to be indicated or not) on all clock screensavers for Squeezeplay.

The fix assigned to Noah is for bug 12798 - the fact there is no alarm indication on screensavers.

This bug is about the fact there is no TIME displayed in Now Playing - which is essential in the bedside alarm clock use case. Once the alarm starts and you stay in bed for a while, what you want to know first is rarely the current song artwork but more often what time it is (i.e. did you stay in bed too long).

The current design is as follows:

The alarm will have an indicator icon when active inside the status bar.  No icon will appear when off.

A clock to indicate current time (ie 12:34pm) will also be present on all remote skins.

A count-down timer will be present under the respective settings menu (alarm, etc.)

Fred, Are you listening to music as you fall asleep?  I am trying to understand the exact use case.  Also what device are you using?  The bug does not state the particular device for reference.

A clock should be present on all remote Now Playing templates with a status bar.

Sorry I was unclear.

The use case is:
Go to bed, set the alarm time, sleep. Alarm triggers, music starts playing, Fred finally wakes up after a (long) while and looks at the screen: it shows now playing (or a screen saver, the default being "now playing" since music plays): there is no time shown. Time is at this point a very valuable information for me to evaluate how urgent it is for me to start moving (i.e. evaluate how long the "little  while longer in bed"  was).

The only way to know time is to have a clock screen saver running, but then changing the volume (or stopping the alarm if it was on by mistake) requires more clicks and navigation than what the typical bedside alarm clock would require.

An "alarm clock now playing" screensaver with LARGE, easy to hit time display, snooze, stop and volume buttons would be the ideal UI, IMHO.

Note the bug was filed under the product but moved to SqueezePlay, so I am not sure how safe it is to mention here. I am beta testing it. Starts with F.

this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.

Ben- the assets and guidelines are in place.  Reassigning over to you...please pitch it back if you do not have what you need.

Fred, I'm not sure this bug is valid any more with the addition of the alarm window popup added for Bug 12800. Can you comment?

If this is Fab4 only ('sokay to talk about now!), this bug can be reopened and retargetted for 8.0/P1, as 8.0 is the SBTouch release.

Ben, you are right, this is now "invalid" or "fixed", depending on how you look at it.

Yes this was about Fab4. Santa did not send me some Baby hardware :(

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.