Bug 13815 - Dropped icon on shutdown, low power, etc screens
: Dropped icon on shutdown, low power, etc screens
Status: CLOSED FIXED
Product: SB Radio
Classification: Unclassified
Component: UI Skin
: Include FW version in comment
: PC Windows XP
: P1 normal (vote)
: 7.4.0
Assigned To: Ben Klaas
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-02 07:46 UTC by Richard Titmuss
Modified: 2009-10-05 14:29 UTC (History)
3 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Titmuss 2009-09-02 07:46:26 UTC

    
Comment 1 SVN Bot 2009-09-08 16:10:20 UTC
 == Auto-comment from SVN commit #7464 to the jive repo by bklaas ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7464 ==

Fixed Bug: 13815 +1
Description: fixed padding for shutdown, low power, and restart screens
IMO there is an unnecessary amount of custom padding tweaks for these icon styles. There's two things that could help this situation:
1. all assets for the center icon have exactly the same dimensions (this is not the case)
2. there should be a trivial way of centering a widget on the screen, both horizontally and vertically
Comment 2 SVN Bot 2009-09-08 16:11:36 UTC
 == Auto-comment from SVN commit #7465 to the jive repo by bklaas ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7465 ==

Bug: 13815
Description: different popups to test icon placement of battery low/restart/shutdown
Comment 3 James Richardson 2009-10-05 14:29:24 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.