Open tschulte opened 7 years ago
I don't know if anything Plover can do could fix this behavior.
Just to confirm:
Yes, the regular keyboard does work perfectly. I will check tomorrow, if the keyboard layout indicator changes when the VM gets the focus.
When the VM is active, at least the keyboard indicator on Windows does not change. Currently I don't have anything installed on the Windows Host. After I have installed python, I can try to debug what's happening.
Classification: Bug
Reproducibility: Always
Plover running on Windows Host uses wrong keyboard layout on Linux Guest
Relates to #656. I am running a VMWare Linuxmint VM on my Windows 10 Host. Both OS are configured to use the same keyboard layout (NEO2 in my case -- but the issue is the same with QWERTZ). Plover is running on the Windows Host with an ErgoDox connected using TXBolt protocol over COM3. On the Windows host everything is OK. Independent on the used keyboard layout the output is correct. But on the Linux VM I have to switch to QWERTY for plover to work correctly. If Linux is configured to QWERTZ instead, SO*EPB results in "yone" instead of "zone" (QWERTZ only differs in Z and Y for A-Z).
Steps to Reproduce
Expected Results
Actual Results
Version
Plover version 3.1.0.
Installer downloaded from Github.
Notes
Workaround: Use QWERTY layout in the VM
Configuration
OS: Host: Windows 10 Enterprise
Guest: Linux linuxmint 4.4.0-64-generic