Reply to thread

Message

<blockquote data-quote="joz" data-source="post: 516349" data-attributes="member: 70244">Well I personally feel that it's no optimal solution cause you are increasing cache size with all those extra, not per se needed, images.The progressbar should be used what it's made for, not work around it by defining your own image for each percentage.That's just how I feel, so I would say no to that but others might disagree. The import idea I had I do not feel so strongly about, but I do about using progressbars like they were meant to and not recreate the wheel.The progressbars are already working for me so there's no need for any extra variables for those progressbars, it just needs a percentage as integer. Besides that every skin has it's own progressbar images and so it would feel more like part of the skin.What you could do to still have 1 file for gauges and have the user control what kind is displayed (progressbar or gauge) is having couple dummy controls or something (or have the gauges and progressbars have an unique ID) so we have something to work with in the skin with Control.IsVisible(). Or you just turn off the controls that should not be visible, by ID</blockquote>

[QUOTE="joz, post: 516349, member: 70244"] Well I personally feel that it's no optimal solution cause you are increasing cache size with all those extra, not per se needed, images. The progressbar should be used what it's made for, not work around it by defining your own image for each percentage. That's just how I feel, so I would say no to that but others might disagree. The import idea I had I do not feel so strongly about, but I do about using progressbars like they were meant to and not recreate the wheel. The progressbars are already working for me so there's no need for any extra variables for those progressbars, it just needs a percentage as integer. Besides that every skin has it's own progressbar images and so it would feel more like part of the skin. What you could do to still have 1 file for gauges and have the user control what kind is displayed (progressbar or gauge) is having couple dummy controls or something (or have the gauges and progressbars have an unique ID) so we have something to work with in the skin with Control.IsVisible(). Or you just turn off the controls that should not be visible, by ID [/QUOTE]

Verification