Definitely makes sense, even if I'm not sure if the skin will run in a more efficient way. But this definitely shortens the code, make it much easier to be followed by users.Since the skin works the way I had it pictured, it kept ringing in my head something you mentioned previously... since that skin has around 30 "Buttons", In your opinion, would it make sense to use MeterStyle ...?
would it reduce the amount of coding to make it run in a more efficient way... ?
or at least make it lighter...?
To do it, you should have to remove from all similar meters the common options, should have to create a [SomeStyle] section and include there all previously removed options. Finally you should have to add a MeterStyle=SomeStyle option to all meters from which you've removed the options.
For instance remove the following options from the [MeterMenuElement1] - [MeterMenuElement17] and the [MeterMenuElement21] - [MeterMenuElement32] meters (see the options to be removed in the bellow posted piece of code). Add the following [ButtonStyle] (obviously you can use any name you want, this is just an example) section to your code (I usually prefer to add it to the beginning of the code, before the first measure, but this is just a matter of personal preference, there is nothing which makes this mandatory):
Code:
[ButtonStyle]Padding=10,5,15,5FontColor=#FontColorPassive#SolidColor=0,0,0,0FontSize=10FontFace=Segoe UIStringStyle=NormalStringAlign=LEFTAntiAlias=1DynamicVariables=1Did you succeed in getting it working this way?
Just note that this procedure can reduce dramatically the length of the code, especially that in your code there are many similarly built meters.
Statistics: Posted by balala — Yesterday, 4:40 pm
