Bug 12106 - Screensaver Bkgrounds should be unique
: Screensaver Bkgrounds should be unique
Status: RESOLVED WORKSFORME
Product: SB Touch
Classification: Unclassified
Component: UI
: unspecified
: All Other
: -- minor (vote)
: 8.0.0
Assigned To: ndijulio
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-19 16:16 UTC by ndijulio
Modified: 2009-09-08 09:27 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 ndijulio 2009-05-19 16:16:19 UTC
Proposal: screensavers should not share the same background as default or wallpaper set by user during normal navigation through menus.  In the absence of a unique wallpaper the default should be black RGB 0,0,0.

This proposal would apply to all devices.
Comment 1 Blackketter Dean 2009-05-19 21:18:42 UTC
Of course, they should work as designed.  Is there a specific case where this is happening where it shouldn't?
Comment 2 ndijulio 2009-05-20 10:21:59 UTC
The current case is the Now Playing screen transition from IR to screensaver.  If the the wallpaper remains identical there is no information that you have entered a different "mode."
Comment 3 Weldon Matt 2009-05-20 11:05:24 UTC
Playing Devil's advocate here for a second: if the modes aren't any different for the moment, why do we need to change the wallpaper?  Why do we need to arbitrarily make a visual change here, other than the fact that internally we know we've triggered the "screensaver?"
Comment 4 Blackketter Dean 2009-05-20 11:22:35 UTC
I guess you are talking about the Now Playing "screensaver", which is kind of special.  In this case we definitely do not want to change the wallpaper.

Screensavers like clocks, slideshows, etc. should be designed to either use their own wallpapers or be prepared to use the user-chosen one.