Bug 13956 - Message UI on ip3k players needs work
: Message UI on ip3k players needs work
Status: CLOSED FIXED
Product: SB 2/3
Classification: Unclassified
Component: UI
: 127
: PC Windows XP
: P1 normal (vote)
: 7.4.0
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-10 14:38 UTC by Ross Levine
Modified: 2009-10-05 14:34 UTC (History)
6 users (show)

See Also:
Category: ---


Attachments
image of UI (389.41 KB, image/jpeg)
2009-09-10 14:39 UTC, Ross Levine
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Levine 2009-09-10 14:38:37 UTC
When first connecting a 7.3 SB3 to SN it displays Messages(1)Messages(0). James had to explain to me what this was all about it was so confusing.
Comment 1 Ross Levine 2009-09-10 14:39:02 UTC
Created attachment 5826 [details]
image of UI
Comment 2 SVN Bot 2009-09-17 06:41:28 UTC
 == Auto-comment from SVN commit #28549 to the slim repo by andy ==
 == https://svn.slimdevices.com/slim?view=revision&revision=28549 ==

Fixed bug 13956, fix string call for messages text
Comment 3 James Richardson 2009-09-24 10:44:33 UTC
I'm still seeing this when attaching a "fresh" IP3K device to test.sn
Comment 4 SVN Bot 2009-09-24 14:01:01 UTC
 == Auto-comment from SVN commit #28635 to the slim repo by andy ==
 == https://svn.slimdevices.com/slim?view=revision&revision=28635 ==

Fixed bug 13956, remove extra EN string that got added by mistake
Comment 5 James Richardson 2009-10-05 14:34:12 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

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