Bugzilla – Bug 9131
Default date format in DateTime screensaver is too long for Boom
Last modified: 2009-09-08 09:19:34 UTC
By default the datetime screensaver uses the long date format of WWWW, MMMM DD, YYYY. On days like today, this is too long for Boom - Wednesday, August 13, 2008. It causes the blinking Alarm/Snooze indicator to be covered so you can only see a few pixels. The quick fix would be to simply change the default to something shorter. I imagine quite a few people would like to be able to see what day it is (Monday, Wednesday) etc, so I think this should be included, although Mon, Wed would be fine. Does anyone really need the year? Assigning to Michael after discussion on campfire.
Created attachment 3799 [details] Make Boom use the short date format by default
Dean - I wonder whether we should make the DateTime screensaver use per player settings instead of global date/time formats. The above patch does enforce the short date format for Boom by default. This can be overridden in the DateTime screensaver settings. But then those settings are used on the other players too.
I do wonder if people will object to losing what day it is from the display. The difference between Sun and Mon can be a crucial one when you're half asleep and considering the snooze...
change 22586 - make DateTime screensaver settings per player - migrate existing settings to client prefs - add localized smaller long date formats to be used on Boom (use short format where localized version is unknown) - use smaller format for screensaver on Boom, instead of SC default as on other players Feel free to re-open if you don't like this change. Max - the new default value does display something like "WED, AUG 13, 2008" on Boom. If you can distinguish "MON" from "SUN", then you should be fine ;-)
Verified fixed in SqueezeCenter 7.2-22900
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.