Bug 9626 - Choose player list is not always populated during SetupWelcome
: Choose player list is not always populated during SetupWelcome
Status: CLOSED FIXED
Product: SB Desktop
Classification: Unclassified
Component: UI
: unspecified
: PC Other
: -- normal (vote)
: 7.3
Assigned To: Ben Klaas
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-01 19:57 UTC by Ben Klaas
Modified: 2009-09-08 09:21 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments
working Choose Player screen with desktop squeezeplay r3044 (67.15 KB, image/png)
2008-10-01 19:57 UTC, Ben Klaas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Klaas 2008-10-01 19:57:10 UTC
Created attachment 4090 [details]
working Choose Player screen with desktop squeezeplay r3044

Dean (r3044) and Remco (Sep 28/29 builds) have both reported this on desktop squeezeplay. Going through setup gets the user to "Choose Player" with one item "Setup Squeezebox" and none of their SqueezePlayers.

I have not seen the issue on my system (see attached)

Tom, I'm assigning this one your way to start...could be it should come back to me, but we can discuss tomorrow
Comment 1 Ben Klaas 2008-10-01 19:59:18 UTC
forgot to add, I was using the r3044 Squeezeplay.dmg from downloads.slimdevices.com
Comment 2 James Richardson 2008-10-30 11:03:56 UTC
Richard states there should be a "spiny" during the player population phase.
Comment 3 Wadzinski Tom 2008-11-06 06:32:36 UTC
I think we talked about Ben picking this up.
Comment 4 Ben Klaas 2008-11-14 12:48:01 UTC
added 5 second popup during setup only, r3377
popup hides immediately after scan completes

needs a better string for the popup in 7.3.1. For now poached a fully translated "Searching..." string from SqueezeCenter.
Comment 5 James Richardson 2008-12-15 12:08:03 UTC
This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

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