There were times where input was "inhibited" either bc the host wasn't able to accept input, or if the cursor wasn't positioned at a 2/
-
-
Replying to @stuartmarks @mwichary
location that could accept input. In those cases key click would be disabled, so you could INSTANTLY tell your input was being ignored. 3/
1 reply 0 retweets 1 like -
Replying to @stuartmarks @mwichary
Some models allowed you to enable or disable key click as a preference. If input was inhibited, it would TOGGLE key click. 4/
1 reply 0 retweets 1 like -
Replying to @stuartmarks @mwichary
So if you were clicking away happily and then your keyboard went dead, you knew something was wrong. Or, if you were typing silently, 5/
1 reply 0 retweets 1 like -
Replying to @stuartmarks @mwichary
and suddenly your keyboard started clicking, you knew something was wrong. Example: the system had crashed. 6/
1 reply 0 retweets 1 like -
Replying to @stuartmarks @mwichary
I really missed this feature after moving to different systems. More than once I was typing a lot that ended up being ignored because 7/
1 reply 0 retweets 1 like -
Replying to @stuartmarks @mwichary
other systems lacked this feature. Not sure this trivia is worth putting in the book, but I thought you'd enjoy it! 8/x
1 reply 0 retweets 2 likes -
Replying to @stuartmarks
Aaaah, interesting. I didn’t know about this. What came before, I think, was actual physical locking of the keyboards.
1 reply 0 retweets 0 likes -
Replying to @mwichary @stuartmarks
Which was, I guess, more annoying and painful.
1 reply 0 retweets 0 likes -
Replying to @mwichary
A physically locking keyboard! I don't think I ever used one of those. But it does sound quite annoying.
1 reply 0 retweets 1 like
I heard you could actually get hurt if the keyboard did it unexpectedly in the middle of you typing furiously.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.