StephenB17
Bit poster
Hi all.
I was wondering if anyone here has seen this issue yet?
The latest release of the Android client seems to have a key mapping issue. It does appears to fix an issue mapping the Tab key that's existed for a while (as stated in the release notes), but in my experience it seems to have broken the mapping for the '=' key, which now behaves like return.
The issue seems to be isolated to using this latest release of the Android Parallels Client. Has anyone else here seen this?
If there's a hack or workaround to tweak the key mappings in the Parallels Client, I would really like to know what it is!
Background:
We're running the Android Parallels Client on a number of Chromebooks. Most of these users are number crunchers, using Excel, so the Tab and '=' keys are important to them.
Many thanks,
Steve
I was wondering if anyone here has seen this issue yet?
The latest release of the Android client seems to have a key mapping issue. It does appears to fix an issue mapping the Tab key that's existed for a while (as stated in the release notes), but in my experience it seems to have broken the mapping for the '=' key, which now behaves like return.
The issue seems to be isolated to using this latest release of the Android Parallels Client. Has anyone else here seen this?
If there's a hack or workaround to tweak the key mappings in the Parallels Client, I would really like to know what it is!
Background:
We're running the Android Parallels Client on a number of Chromebooks. Most of these users are number crunchers, using Excel, so the Tab and '=' keys are important to them.
Many thanks,
Steve