Bug 6463 – On use of 'Forget Player' settings window loads main server UI

Bug 6463 - On use of 'Forget Player' settings window loads main server UI

Summary:

On use of 'Forget Player' settings window loads main server UI

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Web Interface
Version:	7.0
Platform:	PC Windows XP

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-12-26 11:03 UTC by Dan Evans
Modified:	2008-12-18 11:12 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 Dan Evans 2007-12-26 11:03:54 UTC

If you go into Settings > Player > Basic Settings and click "Forget Player" ... the settings window suddenly loads the normal SqueezeCenter UI.  It should not do this.

Instead, it should revert to the next player in the list.  Or, if there are not other players, it should display a message stating something like: "there are not players connected to this server at the moment."

Comment 1 Michael Herger 2007-12-27 00:47:44 UTC

Good point. I assum this is particularly annoying in the new Default skin.

Comment 2 Blackketter Dean 2007-12-27 11:36:16 UTC

I saw this myself.  Then it started doing an infinite and fast reload.

Comment 3 Michael Herger 2007-12-27 11:49:30 UTC

Dean - is this a reload issue similar to the one I tried to fix today? That's a good pointer: the settings window would have to let the main window know about the removed player.

Comment 4 Michael Herger 2007-12-28 09:04:38 UTC

change 15680 - feel free to re-open if needed

Comment 5 Chris Owens 2008-03-07 09:04:30 UTC

This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.