'precondition'
[&MeasureScript1:GetColor('cur_rgb')] is an RGB value, which changes frequently.
[&MeasureScript2:GetColor('cur_rgb')] is an RGB value, which changes frequently.
'want'
1. If "Measure_RGB1 OR Measure_RGB2" Is Above 200, Skin hide "METER_A"
2. If "Both Measure_RGB1 and Measure_RGB2" is Below, Skin show "METER_A"
The new-hotness IfCondition pretty much replaces the old-and-busted IfAbove/IfBelow/IfEqual options.
(Test) && (Test) : AND (Test) || (Test) : OR
I think I understand your "rules" correctly...
1) Don't use !Execute with actions, it has long been deprecated, and is not needed.
2) !Redraw by itself does absolutely nothing. Always use it with !UpdateMeter. You really don't need the [!UpdateMeter METER_A][!Redraw] bit at all in this case, the meter will be hidden or shown during this skin update anyway.
jsmorley wrote: ↑February 14th, 2020, 4:22 pmYou really don't need the [!UpdateMeter METER_A][!Redraw] bit at all in this case, the meter will be hidden or shown on the next skin update anyway.
In fact in such cases !UpdateMeter indeed doesn't make too much sens, but !Redraw does. When a meter is hidden / shown a redraw of the skin can help, to get the skin showing / hiding the meter immediately.
balala wrote: ↑February 14th, 2020, 5:04 pm
In fact in such cases !UpdateMeter indeed doesn't make too much sens, but !Redraw does. When a meter is hidden / shown a redraw of the skin can help, to get the skin showing / hiding the meter immediately.
You are right... However, I'm not sure either is needed in this case. When the conditions change that trigger the hiding or showing of the meter, the skin will be redrawn in any case at the end of that same update cycle. Not one Update later, but right then.
The new-hotness IfCondition pretty much replaces the old-and-busted IfAbove/IfBelow/IfEqual options.
(Test) && (Test) : AND (Test) || (Test) : OR
I think I understand your "rules" correctly...
1) Don't use !Execute with actions, it has long been deprecated, and is not needed.
2) !Redraw by itself does absolutely nothing. Always use it with !UpdateMeter. You really don't need the [!UpdateMeter METER_A][!Redraw] bit at all in this case, the meter will be hidden or shown on the next skin update anyway.
It is perfect! Works fine.
I will not use '!Execute' now.
I also understood [!UpdateMeter METER_A][!Redraw]. I make a lot of applications, I don't know much about the basics.
Thank you for always helping with both the difficult and the basics.
jsmorley wrote: ↑February 14th, 2020, 5:06 pm
You are right... However, I'm not sure either is needed in this case. When the conditions change that trigger the hiding or showing of the meter, the skin will be redrawn in any case at the end of that same update cycle. Not one Update later, but right then.
Yep, true! In this case it really makes not too much sense.