Christopher-Mark Gilland <clgilland07@...>
What do you mean the config file? I thought that
the only place to enable/disable was in keyboard settings:
NVDA+CTRL+K.
---
Christopher Gilland
Co-founder of Genuine Safe Haven
Ministries
----- Original Message -----
Sent: Friday, June 09, 2017 11:47
AM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
Hi,
I bet you have
got one of the inserts unchecked in the config file. I can’t reproduce
it here on three machines.
All the
best
Steve
From: nvda@nvda.groups.io
[mailto:nvda@nvda.groups.io] On Behalf Of Christopher-Mark
Gilland
Sent: 09 June 2017 01:32
To: nvda@nvda.groups.io
Subject:
Re: [nvda] Incredibly odd problem with the NVDA modifier
key
I'm aware of the
difference in the 6pack extended insert key, and the numpad insert key, and
yes, I am absolutely 100% sure.
I'd call you all's
tech support line, but I can't afford support right now; don't have the money.
This is driving me however to absolute drinking, which with the stress lately
I've been under in general, is the last thing I need to
do!
---
Christopher Gilland
Co-founder of Genuine Safe
Haven Ministries
----- Original
Message -----
Sent: Thursday, June 08,
2017 8:28 PM
Subject: Re: [nvda]
Incredibly odd problem with the NVDA modifier
key
Very odd, and you've definitely got "Use numpad insert as
an NVDA modifier key" checked? (There are two insert options - the
other is "use extended insert as an NVDA modifier key" - that's the insert
in the group of six keys with insert, delete, home, end, page up and page
down).
On Fri, Jun 9, 2017 at 10:22 AM, Christopher-Mark Gilland
<clgilland07@...> wrote:
If num lock is
on, yes, the 0 types perfectly, nope, all different type PC's, some
desktop, some laptop. Anything from HP, to Lonovo, Dell, a few Acers,
maybe one or two Asuses, etc. Someone said plug a wireless keyboard in,
and it'll work. Not the case. Tried that, and it didn't
help.
---
Christopher Gilland
Co-founder of Genuine
Safe Haven Ministries
----- Original
Message -----
Sent: Thursday, June
08, 2017 8:10 PM
Subject: Re: [nvda]
Incredibly odd problem with the NVDA modifier
key
If numlock is on, does the key type a 0? If it
was one keyboard on one computer, I'd suspect the key might have gone,
but you say it's happening on multiple computers? Are they all the
same type of computer and same type of keyboard?
On Fri, Jun 9, 2017 at 10:03 AM, Christopher-Mark
Gilland <clgilland07@...> wrote:
Absolutely
nothing. It works fine though if I use caps
lock.
---
Christopher Gilland
Co-founder of Genuine
Safe Haven Ministries
-----
Original Message -----
Sent: Thursday,
June 08, 2017 7:54 PM
Subject: Re: [nvda]
Incredibly odd problem with the NVDA modifier
key
Interesting, I haven't seen that. If you
press NVDA+1 to go into input help mode, what does NVDA report when
you then press the numpad insert key?
On Fri, Jun 9, 2017 at 9:11 AM, Christopher-Mark
Gilland <clgilland07@...> wrote:
OK, this
makes no sense, and I'm highly surprised that no one has seen it,
given the fact I've reproduced it on about 6 different computers
here, and have also had about 5 of my other friends reproduce it
as well.
Ever
since updating to NVDA 2017.2, my numpad insert key has completely
stopped working as the NVDA modifier.
I looked
in the keyboard preferences and both caps lock and numpad insert
are checked. I've unchecked and re, checked both checkboxes
individually as well as at the same time. I've restarted NVDA,
I've rebooted, I've unloaded all plugins and simply reinstalled
from a fresh copy with not a single addon running, and all default
stock settings.
I've
tried with both a portable copy, as well as a full
installation.
I've
converted a portable to a full install, as well as downloaded the
setup file and installed directly with no
success.
I even
used Revo to remove NVDA so that no traces of any app data were
behind. Then reinstalled. No good.
I've
tried this on Windows 7 Home, Windows 7 Pro, Windows 7 Ultimate,
all 3 of those, I've tried both with X86 as well as
X64.
I've
tried with Windows 10 Home, Windows 10 Pro, and even had a friend
who's a college student try with Windows 10 Education. All of
those were tested as well on both X86 and X64. This was reproduced
on every single one of those systems 100%
consistently.
Before
anyone asks the obvious, yes, num lock was disabled. I'm not that
far gone.
I looked
through the diag logs and saw nothing that indicated what the
problem was.
I checked
for an NVDA update and found nothing.
I
installed the snapshot next branch and had the same
problem.
I tested
with JAWS to be sure it wasn't something screwy in general going
on with my insert key, but in JFW, it works flawlessly, plus the
fact it's happenning on more than one
system...
I even
was so desperet, I tried with XP Pro, and that even was
reproducible.
--
Quentin
Christensen
Training and Support
Manager
--
Quentin
Christensen
Training and Support Manager
--
Quentin
Christensen
Training and Support Manager
|
