Bug 13042 – Status bar - icon padding revised from 6px to 10px

Bug 13042 - Status bar - icon padding revised from 6px to 10px

Summary:

Status bar - icon padding revised from 6px to 10px

Status:	CLOSED FIXED

Product:	SB Radio
Classification:	Unclassified
Component:	Menus
Version:	Include FW version in comment
Platform:	PC Windows Vista

Importance:	P3 minor (vote)
Target Milestone:	7.4.0
Assigned To:	Ben Klaas

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-07-24 14:00 UTC by ndijulio
Modified:	2010-05-27 14:45 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Guideline - status bar correct alignment (31.09 KB, image/png) 2009-07-24 14:00 UTC, ndijulio	Details
screenshot with 10px padding (48.78 KB, image/png) 2009-07-24 14:33 UTC, Ben Klaas	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description ndijulio 2009-07-24 14:00:23 UTC

Created attachment 5516 [details]
Guideline - status bar correct alignment

Spacing between icons should be 10px apart (in addition to neg. area around asset).  The Controller will remain with 6px due to space constraints.

Comment 1 Ben Klaas 2009-07-24 14:33:03 UTC

Created attachment 5517 [details]
screenshot with 10px padding

reopen this if it looks bad

(note I got the clock finally centered too...woot!)

Comment 2 James Richardson 2009-10-05 14:26:11 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:45:52 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.