Reply to thread

Message

<blockquote data-quote="joz" data-source="post: 516353" data-attributes="member: 70244">I can't see the interference but I'm no MP plugin programmer either so I don't know what I'm talking about <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> I'm kinda stubborn on this bit, how come I have done the progressbars as I wanted them (using type progressbar) now, which works beatifuly, cannot be done? It's already working! Or are you experiencing problems with the part that decides whether a gauge or progressbar should be shown?Or do you want to be using just one control for both?If the last one is the case keep in mind skinners will have to leave room for stuff cause the images of the gauges have other dimensions than the images for progressbars, especially in height (which is valuable real estate on wide screen tvsets)You are correct about caching, subdirs are excluded. There unfortunately is no way around this.</blockquote>

[QUOTE="joz, post: 516353, member: 70244"] I can't see the interference but I'm no MP plugin programmer either so I don't know what I'm talking about :) I'm kinda stubborn on this bit, how come I have done the progressbars as I wanted them (using type progressbar) now, which works beatifuly, cannot be done? It's already working! Or are you experiencing problems with the part that decides whether a gauge or progressbar should be shown? Or do you want to be using just one control for both? If the last one is the case keep in mind skinners will have to leave room for stuff cause the images of the gauges have other dimensions than the images for progressbars, especially in height (which is valuable real estate on wide screen tvsets) You are correct about caching, subdirs are excluded. There unfortunately is no way around this. [/QUOTE]

Verification