Configuration: latest Parallels 9 build from 10/16/13, Mountain Lion 10.8.5.
Modifier keys CTRL and SHIFT don't consistently work when the modifier key is kept pressed for more than one combination, as outlined in this thread. For example, CTRL+SHIFT+RIGHT-ARROW to highlight a word, then leaving shift pressed and pressing down arrow to highlight an entire line it is as if shift were no longer pressed and the cursor just goes down a line.
I followed all suggestions in KB article 113932, removing any such shortcuts from Mission Control and I have Parallels system shortcuts preferences set to Always (which should mean always sent to the VM guest, never to the Mac OS host). Still doesn't work. I have tried all of the possible settings, none of them work.
Please, this combination of P9 and Mountain Lion is ridiculous. I want Windows to work like it has worked for 20 years.
Between this issue and the sound popping issue I have already posted about, I see these issues as problems for people going back months and I see no effort on Parallel's part to fix them. Not in the latest build, not in KB articles. Please.
Modifier keys CTRL and SHIFT don't consistently work when the modifier key is kept pressed for more than one combination, as outlined in this thread. For example, CTRL+SHIFT+RIGHT-ARROW to highlight a word, then leaving shift pressed and pressing down arrow to highlight an entire line it is as if shift were no longer pressed and the cursor just goes down a line.
I followed all suggestions in KB article 113932, removing any such shortcuts from Mission Control and I have Parallels system shortcuts preferences set to Always (which should mean always sent to the VM guest, never to the Mac OS host). Still doesn't work. I have tried all of the possible settings, none of them work.
Please, this combination of P9 and Mountain Lion is ridiculous. I want Windows to work like it has worked for 20 years.
Between this issue and the sound popping issue I have already posted about, I see these issues as problems for people going back months and I see no effort on Parallel's part to fix them. Not in the latest build, not in KB articles. Please.