THE NEXT KEY MAPPING PROBLEM: There is no way to map command-rightArrow (host) to control-rightArrow (guest). First, mapping generally Command (host) to Control (guest) should work, but it does not. The guest OS still interprets the keypress as if the default settings were in place (i.e. windowsKey-rightArrow, where Windows is the guest OS). The next problem is there is no way to enter a 'rightArrow' into the key mapping box. Pressing rightArrow in the box has no effect. So the key cannot be mapped specifically using this tool.
Worse, whenever by habit the user presses command-rightArrow (or leftArrow), the guest OS fails to provide the expected behavior, **and** the guest OS thinks the default key was pressed (for Windows as guest, the windowsKey), and 'sticks' with that key on, so that the following keypresses by the user are interpreted by the guest OS as being a two-key press, even though the user is only pressing one key.
I have logged any number of problem reports about this and related keyboard issues since launch and have heard nothing back from Parallels. If you're considering the upgrade you should be aware that this problem makes Parallels Desktop 4.0 almost impossible to use if you type a lot of text.
Worse, whenever by habit the user presses command-rightArrow (or leftArrow), the guest OS fails to provide the expected behavior, **and** the guest OS thinks the default key was pressed (for Windows as guest, the windowsKey), and 'sticks' with that key on, so that the following keypresses by the user are interpreted by the guest OS as being a two-key press, even though the user is only pressing one key.
I have logged any number of problem reports about this and related keyboard issues since launch and have heard nothing back from Parallels. If you're considering the upgrade you should be aware that this problem makes Parallels Desktop 4.0 almost impossible to use if you type a lot of text.