Questions:
Nice panel by the way Bill. To which aircraft does it belong?
- Are you only referring to the changing textures in this case?
- Does this panel/gauge use with backlight-ing that dynamically in/decreases in light-intensity when turned on/off?
- Is it possible to automate these boring tasks in any way, with macro's of some sort?
This is the annunciator sub-panel for the Avanti P180.
Each "light" requires two polygons; one for the unlighted text, the other for the lighted text (Additive mode, Self-Illumination)
They are controlled by <Visibility> conditions, so 50 of them require 100 unique entries in the modeldef.xml file.
Since the only difference between them is the custom L:variable used for <Visibility> control, and the <PartInfo> name, it is indeed possible to copy/paste each set and simply change the names of the <PartInfo> and (L:var)...
...which while relatively fast, is still boring and tedious!
This panel has a "Systems Test" knob that selects the specific system to test, and requires a knob "pull" to make the selector active, which is why the extra test conditions in the <Code> section.
Code:
<!-- ANNUNCIATOR LIGHTS VISIBILITY -->
<PartInfo>
<Name>Avt_L_FIRE_LIGHT_OFF</Name>
<Visibility>
<Parameter>
<Code>
(L:Avt_SysTest_SEL,enum) 0 !=
(L:Avt_SysTest_PULL, bool) ! or
(L:Avt_L_FIRE_LIGHT,bool) ! and
</Code>
</Parameter>
</Visibility>
</PartInfo>
<PartInfo>
<Name>Avt_L_FIRE_LIGHT_ON</Name>
<Visibility>
<Parameter>
<Code>
(L:Avt_SysTest_SEL,enum) 0 ==
(L:Avt_SysTest_PULL, bool) and
(L:Avt_L_FIRE_LIGHT,bool) or
</Code>
</Parameter>
</Visibility>
</PartInfo>