Bug 12440 - Handle text/menu cases coming from SN/SC - currently no scroll support....
: Handle text/menu cases coming from SN/SC - currently no scroll support....
Status: CLOSED FIXED
Product: SB Radio
Classification: Unclassified
Component: Menus
: Include FW version in comment
: PC Other
: -- normal (vote)
: 7.4.0
Assigned To: Wadzinski Tom
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-18 10:32 UTC by Wadzinski Tom
Modified: 2010-05-27 14:46 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wadzinski Tom 2009-06-18 10:32:44 UTC
the scrollable menu/textarea functionality doesn't work for SlimBrowse served item (only for SimpleMenus). There are very few of these menus, and only one that I know of (SB_ACCOUNT_INFO -see below).  The quick fix is to make sure that the translations for that string fit without pushing the menu items off screen


SB_ACCOUNT_INFO
	EN	Your Squeezebox account allows you to access Internet music, add apps to your Squeezebox, and stream music from your computer to your Squeezebox.

When the translations come in for this, retest this screen (put the strings into the SkinTestApplet).
Comment 1 Wadzinski Tom 2009-07-02 07:09:21 UTC
added support in SlimBrowse for header widget (by converting such menus to SimpleMenus).
Comment 2 James Richardson 2009-10-05 14:26:53 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.
Comment 3 Chris Owens 2010-05-27 14:46:00 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.