Date
1 - 7 of 7
A weird one!
|
Roger Stewart
Good idea, but not the problem here. I'm using a hard wired keyboard. Anyhow, it didn't happen this morning and probably won't happen again until I win the Power Ball! :-)
toggle quoted message
Show quoted text
Roger On 2/6/2019 3:51 AM, Shaun Everiss wrote:
I have had windows do things with wireless keyboard. |
|
|
|
I have had windows do things with wireless keyboard.
toggle quoted message
Show quoted text
If its doing that a lot, then its probably your keyboard. It could be dirty but most like you have a dieing battery. Make sure you keep a spare wired keyboard and lots of power cells about. I have had users that have run out of batteries, have noticed things getting unstable, but never bothered about them, or added it to a todo list and forgot. So they need to get another computer and go out to the store to get a battery. Its like printer ink, actually buy your drums and ink before you run oout of them. On 6/02/2019 7:18 AM, Brian's Mail list account via Groups.Io wrote:
It thinks you have pressed a combination of keys. I've definitely seen this in Windows 7. It seems quite random and I suspect its a windows issue myself. It is very rare but can for example appear if something is taking longer than normal to boot up I found. |
|
|
|
Brian's Mail list account
It thinks you have pressed a combination of keys. I've definitely seen this in Windows 7. It seems quite random and I suspect its a windows issue myself. It is very rare but can for example appear if something is taking longer than normal to boot up I found.
toggle quoted message
Show quoted text
If anyone has any idea let us know Often looking at the nvda log shos that several keys are pressed when only one or two are really pressed. I'm almost sure this goes back a very long way and had a ticket but nobody could get it to happen to order. I found often in my case it was windows and control. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message -----
From: "Roger Stewart" <paganus2@...> To: "NVDA List" <nvda@groups.io> Sent: Tuesday, February 05, 2019 3:46 PM Subject: [nvda] A weird one! When I started my computer this morning I went to read my email and every key I pressed nvda kept saying "not in a table cell". I have no idea what that was about. I tried nvda key plus q to quit or restart nvda and it kept saying the same silly thing about table cells. Fortunately I have the Spydec P-View utility and I was able to find nvda.exe in the list of running apps and I was able to kill it from there. After I restarted nvda, everything was normal again! This is the first time I've ever had this happen in several years of using nvda. It was probably a one in a million glitch of some kind, but I'll watch and see if it ever happens again but I doubt it will. Any ideas on what might have happened? Just curious as I don't think this is a bug. |
|
|
|
Gene
My guess is that you had sticky keys, for some
reason. This appears to be rare now, it used to be rather common with
JAWS, but as far as I know, it either didn't happen or was very rare with
NVDA. Sticky keys means that, for some reason, keys are active whether you
are holding them or not. In your case, control and alt appear to have been
active. Since those are the keys for reading in tables when browse mode is
on, you probably heard the announcement because those keys were both on.
Unloading and running NVDA caused the keys to be unlocked. Also, if you
had tried pressing control perhaps twenty times fast and then alt twenty times
fast, while letting NVDA run, that might have solved the problem,
too.
Gene ----- Original Message -----
I was getting the table message in Thunderbird.
However, the nvda keys were not working at all and that was global. I was able
to hear the names of the running applications list so I could find and stop
nvda. There was no way to stop nvda except using P-View as I couldn't bring up
the shutdown dialogue or the nvda menu at all.
Roger
On 2/5/2019 10:28 AM, Gene wrote:
|
|
|
|
Roger Stewart
I was getting the table message in
Thunderbird. However, the nvda keys were not working at all and
that was global. I was able to hear the names of the running
applications list so I could find and stop nvda. There was no way
to stop nvda except using P-View as I couldn't bring up the
shutdown dialogue or the nvda menu at all.
Roger
On 2/5/2019 10:28 AM, Gene wrote:
|
|
|
|
Gene
Are you saying this happened everywhere or just in
certain places? that may be important in guessing what
occurred.
Gene ----- Original Message -----
From: Roger Stewart
Sent: Tuesday, February 05, 2019 9:46 AM
To: NVDA
List
Subject: [nvda] A weird one! every key I pressed nvda kept saying "not in a table cell". I have no idea what that was about. I tried nvda key plus q to quit or restart nvda and it kept saying the same silly thing about table cells. Fortunately I have the Spydec P-View utility and I was able to find nvda.exe in the list of running apps and I was able to kill it from there. After I restarted nvda, everything was normal again! This is the first time I've ever had this happen in several years of using nvda. It was probably a one in a million glitch of some kind, but I'll watch and see if it ever happens again but I doubt it will. Any ideas on what might have happened? Just curious as I don't think this is a bug. Roger |
|
|
|
Roger Stewart
When I started my computer this morning I went to read my email and every key I pressed nvda kept saying "not in a table cell". I have no idea what that was about. I tried nvda key plus q to quit or restart nvda and it kept saying the same silly thing about table cells. Fortunately I have the Spydec P-View utility and I was able to find nvda.exe in the list of running apps and I was able to kill it from there. After I restarted nvda, everything was normal again! This is the first time I've ever had this happen in several years of using nvda. It was probably a one in a million glitch of some kind, but I'll watch and see if it ever happens again but I doubt it will. Any ideas on what might have happened? Just curious as I don't think this is a bug.
Roger |
|
|