Cmd key often misses, and always if too fast
Posted: Wed Jan 29, 2020 10:19 pm
I write a lot of text in Word 4 using OS 9.2 under SheepShaver, and I tend to work fast and use keyboard shortcuts a lot.
The Cmd (Apple, Command) key frequently "misses". That is, the application will think I'm typing the letter without the Cmd key pressed. Thus, I might type Cmd-f and quickly start typing what I expect will go into the Find dialog box, and when I look at the screen, I see the text 'f' has been added, along with what I was searching for, in my text window. This means I have to slow down and keep checking to make sure the Cmd key has indeed been engaged; and of course Save (Cmd-s), copy/paste and other functions sometimes don't work and instead I get extraneous junk in the files I'm writing.
This happens on two different laptops and my iMac; it's definitely not a physical problem with my Cmd key. And it doesn't happen to be in OS X, e.g. when using Word 2016. It's been happening randomly in SheepShaver since I installed vesion 2.4 in 2014.
Today, after upgrading to SheepShaver 2.5 on my iMac, I discovered a reproducible problem, and I think it might have to do with the Cmd key being "pressed" very fast, triggering the same problem. I use TypeIt4Me to expand sequences quickly and type phrases and editorial instructions that I use over and over, and this has worked fine for years.
But using the new SheepShaver now, every time I type a sequence that has such expansions, I get simply:
v
which I think maybe means TypeIt4Me is copying the sequence I want, then sending out a Cmd-v to paste it in, and because of this SheepShaver bug, Word thinks it's seeing a v rather than Cmd-v and just adds a v. I can't be sure but it's the only explanation I have for the 'v' appearing in place of the string I want.
Does anyone know of a way to ensure the Cmd key is always picked up, and/or why this problem appears in SheepShaver 2.5 and not in the 2014 version (2.4) I was using before (while the random Cmd problem appears in both versions).
Thanks for anyone's insights, as always.
The Cmd (Apple, Command) key frequently "misses". That is, the application will think I'm typing the letter without the Cmd key pressed. Thus, I might type Cmd-f and quickly start typing what I expect will go into the Find dialog box, and when I look at the screen, I see the text 'f' has been added, along with what I was searching for, in my text window. This means I have to slow down and keep checking to make sure the Cmd key has indeed been engaged; and of course Save (Cmd-s), copy/paste and other functions sometimes don't work and instead I get extraneous junk in the files I'm writing.
This happens on two different laptops and my iMac; it's definitely not a physical problem with my Cmd key. And it doesn't happen to be in OS X, e.g. when using Word 2016. It's been happening randomly in SheepShaver since I installed vesion 2.4 in 2014.
Today, after upgrading to SheepShaver 2.5 on my iMac, I discovered a reproducible problem, and I think it might have to do with the Cmd key being "pressed" very fast, triggering the same problem. I use TypeIt4Me to expand sequences quickly and type phrases and editorial instructions that I use over and over, and this has worked fine for years.
But using the new SheepShaver now, every time I type a sequence that has such expansions, I get simply:
v
which I think maybe means TypeIt4Me is copying the sequence I want, then sending out a Cmd-v to paste it in, and because of this SheepShaver bug, Word thinks it's seeing a v rather than Cmd-v and just adds a v. I can't be sure but it's the only explanation I have for the 'v' appearing in place of the string I want.
Does anyone know of a way to ensure the Cmd key is always picked up, and/or why this problem appears in SheepShaver 2.5 and not in the 2014 version (2.4) I was using before (while the random Cmd problem appears in both versions).
Thanks for anyone's insights, as always.