Keyboard based entry in GNS530/430 does not function (C172 Analog)

ISSUE DESCRIPTION

Description of the issue:
When entering a flight plan with either the GNS530 or 430 in the analog/basic 172, clicking on the keyboard icon to activate keyboard-based entry does not activate.

If applicable, which aircraft is experiencing this issue:
Analog/Basic Cessna 172

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes/Yes

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Load into the analog/basic Cessna 172.
  2. Click FPL button on either the 530 or 430.
  3. Push in the right inner knob to activate cursor.
  4. Turn inner right knob right once to bring up waypoint entry window.
  5. Attempt to click the keyboard icon to activate keyboard entry.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:
In this case, only a mouse.

[PC Only] Are you using Developer Mode or have you made any changes to it?
No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use?
RTX 4070

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.
N/A

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

In addition the GNS 530/430 units in the C172 analog cannot be popped out using right ALT and mouse click. I have filed a separate bug on this.

I’m thinking both of these bugs are related and something is preventing keyboard mouse interaction with the GNS 530/430 devices.