Bug 5787 – Block clock screensaver is too low contrast

Bug 5787 - Block clock screensaver is too low contrast

Summary:

Block clock screensaver is too low contrast

Status:	CLOSED FIXED

Product:	SB Controller
Classification:	Unclassified
Component:	Screensavers
Version:	unspecified
Platform:	Macintosh Other

Importance:	P2 normal (vote)
Target Milestone:	7.1
Assigned To:	ndijulio

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-10-13 16:11 UTC by Blackketter Dean
Modified:	2008-12-15 12:37 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Clock Reference Artwork (1.11 KB, image/png) 2007-11-07 19:21 UTC, ndijulio	Details
Block Clock Artwork [inc. contrast] (5.54 KB, application/octet-stream) 2007-11-07 19:21 UTC, ndijulio	Details
View All 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 Blackketter Dean 2007-10-13 16:11:38 UTC

Because of the narrow viewing angle, the grey on black colors of the block screensaver are too low contrast to see from most angles.  Let's find another color for the numbers that's more visible.

Comment 1 ndijulio 2007-11-07 19:21:18 UTC

Created attachment 2382 [details]
Clock Reference Artwork

Comment 2 ndijulio 2007-11-07 19:21:57 UTC

Created attachment 2383 [details]
Block Clock Artwork [inc. contrast]

Comment 3 Ben Klaas 2007-11-08 13:29:17 UTC

checked in r843

Comment 4 Chris Owens 2008-07-30 15:31:42 UTC

This bug has now been fixed in the 7.1 release version of SqueezeCenter!  Please download the new version from http://www.slimdevices.com 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.

Comment 5 James Richardson 2008-12-15 12:37:49 UTC

This bug has been fixed in the 7.3.0 release version 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.