In the case of the EFIS Range selector, L:EFIS_Range_Sel is updated with a value ranging from 0 to 6. (2) But in the case of latching switches (including multi-position rotary switches like the EFIS Range selector in post #7), the "foreign gauge" updates the associated LVar with the present location of the switch.
FOKKER 100 DIGITAL AVIATION FSX UPDATE
So it is indeed unnecessary for me to similarly update the _pressed var with my LUA code, as I am not planning to display the EFIS and AFCAS once my hardware replaces it. In such cases the writing is carried out in the mouse section of the xml code, as we have seen, and serves only to change the visual status of the gauge (by toggling the bitmaps). (1) In the case of momentary switches (like the AP1 button and the AP disengage bar in post # 1 of this thread), the "foreign gauge" does not write to the associated _ pressed var after it has acted upon the command and parameter transmitted by L:XMLIF_mouse_cmd and L:XMLIF_mouse_flag. With the tool I checked the LVar set dynamically in an FS session, as you suggested, and I find that: I installed LocalVarsLogger- it is indeed a powerful and beautifully crafted tool, and several LVars became visible that I had not seen with other similar tools.some of these LVars hadn't even appeared in the XML gauge code! Thank you!
But having all questions about FS2020 in one forum becomes a bit messy. Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this.