Bug 9589 – Time display on Now Playing (and elsewhere) doesn't respect timezone

Bug 9589 - Time display on Now Playing (and elsewhere) doesn't respect timezone

Summary:

Time display on Now Playing (and elsewhere) doesn't respect timezone

Status:	CLOSED FIXED

Product:	MySqueezebox.com
Classification:	Unclassified
Component:	Player UI
Version:	Prod
Platform:	Macintosh All

Importance:	P3 major (vote)
Target Milestone:	Falco
Assigned To:	Andy Grundman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-09-26 00:40 UTC by Michael Herger
Modified:	2008-12-15 12:24 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
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 Michael Herger 2008-09-26 00:40:25 UTC

Time is correctly displayed in DateTime screensaver

Comment 1 Michael Herger 2008-09-26 00:43:34 UTC

Additionally the time option for Now Playing isn't available in the SN web UI

Comment 2 Michael Herger 2008-09-26 01:30:01 UTC

change 23302 - respect timezone when displaying time in Now Playing mode; move occurences of the current time/date display to SN compatible $client->timeF() or $client->longDateF() to get rid of the "if ($::SLIMSERVICE)" clause

Comment 3 Michael Herger 2008-09-26 01:40:32 UTC

change 4623 - add CLOCK to the available options on SN web UI.

Andy - I checked these in to to SC 7.2.1 and SN/qa branch respectively. I'll let you decide whether they qualify for a hotfix or not. Thanks!

Comment 4 Chris Owens 2008-09-29 09:42:01 UTC

Qa to check today, then let Michael know to check it in to trunk.

Comment 5 Spies Steven 2008-10-13 14:18:08 UTC

Both changes work fine for me in test.sn.com and sc 7.2.1 23502 once it was brought to my attention that the now playing clock option is only available for boom.

Comment 6 Andy Grundman 2008-10-30 09:13:12 UTC

This is fixed right?

Comment 7 Ross Levine 2008-12-04 12:49:43 UTC

Verified in 7.3 - 24192.

Comment 8 James Richardson 2008-12-15 12:24:26 UTC

This bug has been fixed in the latest release of SqueezeNetwork!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.