AUTOPILOT GLIDESLOPE HOLD loophole is leaving it on by itself

There is no event that turns on the AUTOPILOT GLIDESLOPE HOLD and this makes
sense. But I found a loophole that can leave it on by itself and had to write
custom code to turn it back off. 1. If you turn on the default APR event. 2.
Click the NAV event. This will leave the AUTOPILOT GLIDESLOPE HOLD enabled
all by itself… And I have lights that get left on in return telling you
that the glideslope is armed when this is not possible with the approach mode
disabled. So hope you can fix this. Here is my logic that also will help to
explain the exact condition that is needed to turn it back off.

(A:AUTOPILOT NAV1 LOCK,Bool) 0 ==
(A:AUTOPILOT APPROACH HOLD,Bool) 0 == and 
(A:AUTOPILOT GLIDESLOPE HOLD,bool) 1 == and 
if{ (>K:AP_APR_HOLD_OFF) }

Or Should we be using the Localizer hold event AP_LOC_HOLD for the NAV mode
button and not the AP_NAV1_HOLD as this will now also capture a VOR and a
localizer???

Hello @Flysimware I was able to reproduce the problem and it was added to our
issue tracking system. Your workaround seems fine, AP_LOC_HOLD is an approach
mode so I don’t think that’s what you want to map to your NAV button. Regards,
Sylvain