Bug 10176 – "when playing" screensaver setting on web interface list two "Now Playing" items

Bug 10176 - "when playing" screensaver setting on web interface list two "Now Playing" items

Summary:

"when playing" screensaver setting on web interface list two "Now Playing" items

Status:	RESOLVED FIXED

Product:	MySqueezebox.com
Classification:	Unclassified
Component:	Web UI
Version:	Prod
Platform:	PC Windows Vista

Importance:	-- normal (vote)
Target Milestone:	---
Assigned To:	Michael Herger

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-11-30 02:50 UTC by Nigel Birch
Modified:	2009-01-08 14:25 UTC (History)
CC List:	0 users

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 Nigel Birch 2008-11-30 02:50:59 UTC

On SqueezeNetwork, under Players > Settings > Display, for thr "Screensaver when playing" settings, there are two "Now Playing" items listed.  I'm guessing that one is "Now Playing" and the other is "Jump To Now Playing"?

For the other two Now Playing settings, there's only one Now Playing item listed.

Should there be two Now Playing items listed for "when playing"?

Should there be a Now Playing item listed at all for "when stopped" and "when off" (for me, SqueezeCentre does't list Now Playing items for these two)?

Thanks.

Comment 1 Michael Herger 2008-11-30 06:21:46 UTC

change 5185 - fix the screensaver label. This will be in the next SN update. Thanks!

Comment 2 James Richardson 2008-12-15 12:17:28 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.

Comment 3 Nigel Birch 2008-12-15 15:15:23 UTC

Looks good - thanks.

Comment 4 Nigel Birch 2009-01-08 14:22:14 UTC

I'm still seeing this after the comment 1 check-in.  I saw it about a week ago when I was on a v7.3.1-ish SVN check-out.  Is there any debugging I can enable to help track down the cause of the behaviour I'm seeing?  Thanks.

Comment 5 Nigel Birch 2009-01-08 14:25:18 UTC

Whoops - wrong bug.  Sorry.