Transponder keypad input is very sticky
-
This has been an issue for a long time (since the plane's been out), sometimes it's better, sometimes worse.
When trying to enter the flight number into the ATC part of the transponder, the alphanumeric keypad behaves very erratically. Sometimes, it eats clicks (I was reminded of that by the UNS-1 keyboard issue). At other times, it will advance while trying to get to a certain letter, e.g., trying to enter a "C" results in "A1..." because the input advanced between input events. Sometimes, the input simply refuses to advance at all so if you need to enter something like "K4", it stops dead on the "K" and requires entering another key and clearing it again to get to the next position.
-
I am not able to replicate this with our latest internal build, so the improvements to the UNS-1 button press logic may have had the welcome side effect of improving the transponder button logic too.
Please do let us know if the transponder button logic is better/worse/the same in the upcoming v0.2.2 and we can go from there.
Mark - Just Flight
Just Flight Development Assistant
-
I am not able to replicate this with our latest internal build, so the improvements to the UNS-1 button press logic may have had the welcome side effect of improving the transponder button logic too.
Please do let us know if the transponder button logic is better/worse/the same in the upcoming v0.2.2 and we can go from there.
Mark - Just Flight
@Mark I gave it a quick try, with an attempt to enter "CRX0332" (a few letters far back on their keys and repeating numbers).
The behaviour with getting to a letter appears to have improved, I had no issues over several attempts. However, attempting the numeric part frequently got stuck at "03" with the cursor refusing to progress past the "3" no matter how long I waited. It's not a solid reproduction though, sometimes it consistently progresses after blinking twice.
It feels a bit like a timing issue somewhere in that logic sometimes not getting the clue.
-
Thank you for reporting back. I have been able to replicate this once with v0.2.2, but it does seem quite temperamental as I haven't been able to reproduce it since.
I have logged this on our internal bugs tracker for us to investigate this further though, and we'll aim to include an improvement to this logic in a future update to the 146.
Mark - Just Flight
