Yet ANOTHER bug in a gauge of mine solved ..LOLIf you program XML gauges, and rely on stack operations (like the "d" and "r" commands), note that ALL events take a value from the stack, even events that logically don't require a value (and simply read but ignore the read value). Which might not be what you expect; that is: I didn't :-)Example:(>K:TOGGLE_TAXI_LIGHTS)by itself works perfectly and gives the same result as 1 (>K:TOGGLE_TAXI_LIGHTS)or100 (>K:TOGGLE_TAXI_LIGHTS)However,3 (>K:TOGGLE_TAXI_LIGHTS) (>G:Var1)DOESNOT set Var1 to 3, but to the previous value on the stack.3 100 (>K:TOGGLE_TAXI_LIGHTS) (>G:Var1)DOES set Var1 to 3.Cheers, Rob

Now you've lost me! :-lolregardsEd

http://forums.avsim.net/user_files/115553.jpgAMD Athlon 64 3500+, 1024Mb PC3200 DDR, 300Gb HD 128Mb DDR Nvidia 6600GT PCI Express, Audigy 2 ZS

>3 100 (>K:TOGGLE_TAXI_LIGHTS) (>G:Var1)>DOES set Var1 to 3.Er, why not simply put the value for G:Var1 in front of the actual call, e.g.:(>K:TOGGLE_TAXI_LIGHTS) 3 (>G:Var1)???

Hi Bill,Yes, of course ...But it was just an example to illustrate my point :-)Rob