Bug 13177 - Switching from SN to SC when no music is playing does not require error screen
: Switching from SN to SC when no music is playing does not require error screen
Status: RESOLVED DUPLICATE of bug 13116
Product: SB Radio
Classification: Unclassified
Component: Menus
: Include FW version in comment
: PC Other
: P1 normal (vote)
: 7.4.0
Assigned To: Wadzinski Tom
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-31 16:07 UTC by Dan Evans
Modified: 2010-05-27 14:45 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2009-07-31 16:07:03 UTC
Testing r6865.

2 versions of the same bug:

1. If Baby is sitting idle-- either directly after setup or long after-- and you select "My Music" and then a server, you get an error stating:

"You have made a selection that will connect to a different library, which will stop the music.  [choice] switch to <servername>"

This error is unnecessary if no music is being played.  If you wanted to be more careful, you could say it's unnecessary if no music is being played and the current playlist is empty.

2. If you shut off the SB Server Baby was connected to and try selecting "Pandora" the same error comes up, but the choices are, "[choice] switch to mySqueezebox.com?  or reconnect to sb server?"

I wasn't playing music at this time so this should not come up.  If no music is currently playing, make this an automatic choice?
Comment 1 James Richardson 2009-07-31 21:20:42 UTC
Tom: Your thoughts on this?  I noticed it too, but was unable to reproduce it like Dan has above.

I saw an error where attempting to connect to an App via SC required me to connect to SN first...IMHO similar but I could be wrong.
Comment 2 Weldon Matt 2009-08-01 14:51:54 UTC
Only caveat to this is that if there is anything in the "current playlist", it disappears whenever you switch from SC to SN or vice versa.  Something to consider.
Comment 3 Wadzinski Tom 2009-08-03 12:08:13 UTC

*** This bug has been marked as a duplicate of bug 13116 ***
Comment 4 Chris Owens 2010-05-27 14:45:53 UTC
These bugs have all been marked resolved and belong to a component which is being removed.  Therefore they have been moved to the most applicable of the new components.