I believe this is a problem with Audacity and not Keyman. However, I am hoping that community might help me understand or figure out the (likely) problem so that I can better provide a bug report. I already opened a bug report early last year and it seems 3 versions of Audacity later, no fix. I’m turning to the community here who may have more experiences with the same/similar behavior and what the root cause was (and how to fix), so that I might get some movement on their end.
OS: Windows 10 (builds 1607, 1703, and 1709)
Keyman version: 9.0.528 (and previous two updates) - I have Pro, but installed the Free version on another computer and encountered the same behavior
Keyman keyboards: all
Audacity versions: 2.2.1; 2.1.3; 2.1.2
After installing an updated version of Audacity, nowhere in its GUI interface does it recognize that the Keyman keyboard is enabled. The regular, standard Windows keymapping is used. I originally noticed this with the SIL IPA keyboard but installed several other keyboards and found none of them work. Installing the older 2.1.1 version of Audacity immediately recognizes Keyman (no reinstallation necessary).
This indicates that something changed in Audacity and not Keyman. I looked through the code for Audacity, but it is a reasonably large project and written in C which is pain for someone jumping into new code without any support documents.
What type of change could cause a program to no longer recognize Keyman in Windows 10? Let me know if I can provide additional information that might help!