Bug 12131 - "Problem Connecting" screen needs "Choose Different Network" option
: "Problem Connecting" screen needs "Choose Different Network" option
Status: RESOLVED DUPLICATE of bug 13186
Product: SqueezePlay
Classification: Unclassified
Component: Networking
: unspecified
: PC Other
: P1 normal (vote)
: 7.4.0
Assigned To: Wadzinski Tom
: SLT
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-21 14:02 UTC by Weldon Matt
Modified: 2009-09-08 09:18 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Weldon Matt 2009-05-21 14:02:03 UTC
The "Problem Connecting" screen that appears when there are issues connecting to your network needs an option to "Choose Different Network."  That option should take you to the ETHERNET/WIRELESS choice first (then to the network screen if "wireless" is chosen), in case the user would rather connect via ethernet at this point.

Currently the options are "Go Back" and "Try Again."  "Go back" is close to useless, since there is already a "back" button.
Comment 1 Blackketter Dean 2009-07-22 09:17:58 UTC
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code.  Feel free to move it back if it's specific to the single original product.
Comment 2 Wadzinski Tom 2009-07-27 07:52:40 UTC
string added - r6785, non-string work not yet done.
Comment 3 Weldon Matt 2009-07-27 15:40:54 UTC
If the screen that displays in this case is actually a network connection issue, then we should use the cases/copy provided in bug 12435.

In cases of SC connection problems, we need a NEW string:

"Connection Problem

We can't connect to [library name]. Make sure your computer is turned on and connected to your local network, and that Squeezebox Server is currently running."

Try Again >
Choose Different Library >"
Comment 4 Wadzinski Tom 2009-07-27 19:30:44 UTC
added string for comment #3 in r6803. non-string work still todo
Comment 5 Wadzinski Tom 2009-08-17 10:07:14 UTC
fixed with 13186

*** This bug has been marked as a duplicate of bug 13186 ***