Bug 5674 – Updated Classic Clock artwork

Bug 5674 - Updated Classic Clock artwork

Summary:

Updated Classic Clock artwork

Status:	CLOSED FIXED

Product:	SB Controller
Classification:	Unclassified
Component:	Screensavers
Version:	unspecified
Platform:	PC Windows XP

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-10-05 09:04 UTC by Richard Titmuss
Modified:	2008-12-15 12:37 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Reference artwork (58.89 KB, application/x-zip-compressed) 2007-10-05 09:05 UTC, Richard Titmuss	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 Richard Titmuss 2007-10-05 09:04:55 UTC

Comment 1 Richard Titmuss 2007-10-05 09:05:33 UTC

Created attachment 2215 [details]
Reference artwork

Comment 2 Richard Titmuss 2007-10-05 09:10:03 UTC

Noah said:

1. Classic Clock
artwork has been slightly modified for ease of programing.  i isolated the dots [12:34] so they can be independently positioned on the background.

Comment 3 Richard Titmuss 2007-10-05 14:38:38 UTC

*** Bug 5585 has been marked as a duplicate of this bug. ***

Comment 4 Chris Owens 2007-10-30 10:29:08 UTC

Ben to follow up with Lucas(?)

Comment 5 Ben Klaas 2007-11-01 14:03:54 UTC

Jive r795 should have these fixes.

Comment 6 Chris Owens 2008-07-30 15:28:33 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 7 James Richardson 2008-12-15 12:37:47 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.