Re: Incredibly odd problem with the NVDA modifier key
Christopher-Mark Gilland <clgilland07@...>
I'd be more than happy to do that, if someone can
walk me through the steps.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 8:44 PM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
That's what I meant.
I have no idea why you and a number of people
have this experience while a lot of users don't. Perhaps sending
relevant information from the log to developers might be the best way to
proceed. I don't know enough about getting information from the log nor
where to send it to discuss the matter further but someone else probably will
provide information.
Gene
----- Original Message -----
Sent: Friday, June 09, 2017 6:53 PM
Subject: Re: [nvda] Incredibly odd problem with the NVDA modifier
key
Gene,
Thank you for advocating for me on this so I
didn't have to again repeat myself. That is incredibly appreciated, and no. I
do not mean that sarcastically either. Really, I do thank you.
Yeah, it's the weirdest thing I've seen!
And just to answer your question, Gene, I'm using the standard American
English language with country region set to United States. I presume that is
what you meant.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
----- Original Message -----
Sent: Friday, June 09, 2017 3:14
AM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
Did you read the entire message? It says
that many machines of many different users were tried. It says that
both Windows 7 and Windows 10 were tried. It says that JAWS was tried
and the problem didn't exist. It is clear that the problem didn't
exist before installing 17.2. The message says:
Ever since updating to NVDA 2017.2, my numpad
insert key has completely stopped working as the NVDA
modifier.
It might be relevant to verify which version of
English the computers are set for and to try running 17.1 again but almost
every condition you asked about has been tested for, including running
without add ons.
Gene
----- Original Message -----
Sent: Friday, June 09, 2017 2:02 AM
Subject: Re: [nvda] Incredibly odd problem with the NVDA
modifier key
Hi I cannot duplicate this problem in Windows 7 with UK
English with either laptop or desktop set up with or without
capslock set as nvda key.
Suggestions. Something to do with
maybe Windows 10 if this is in use on all machines Oddity in then add on
or other software running blocking that key combination from
working. Only way to prove its nvda is to go back to an old version
and report back, but from what you say that might not be ideal
either.
I wonder what language is set on the machine, could it be
mapping that key before nvda gets to it? Brian
bglists@... Sent
via blueyonder. Please address personal email to:- briang1@..., putting
'Brian Gaff' in the display name field. ----- Original Message -----
From: "Christopher-Mark Gilland" <clgilland07@...> To:
<nvda@nvda.groups.io> Sent:
Friday, June 09, 2017 12:11 AM Subject: [nvda] Incredibly odd problem
with the NVDA modifier key
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.
What
gives!
Chris.
|
|
Hi Chris, Please email me off list. I would love to hear what you are thinking. David Moore Sent from Mail for Windows 10
toggle quoted messageShow quoted text
From: Christopher-Mark GillandSent: Friday, June 9, 2017 8:14 PM To: nvda@nvda.groups.ioSubject: Re: [nvda] Apple WWDC Keynote They are, but... there are other things, accessibility not withstanding that're making me reconsider some things. That's kind of off topic though, so I'll let it rest. --- Christopher Gilland Co-founder of Genuine Safe Haven Ministries ----- Original Message ----- Sent: Friday, June 09, 2017 5:38 PM Subject: Re: [nvda] Apple WWDC Keynote Correct me if I’m wrong but aren’t apple products and apps accessible? From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Christopher-Mark Gilland Sent: Thursday, June 08, 2017 6:41 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Apple WWDC Keynote No kidding. I used to be quite an Apple fanatic, but I'm rapidly seeing the light. --- Christopher Gilland Co-founder of Genuine Safe Haven Ministries ----- Original Message ----- Sent: Tuesday, June 06, 2017 6:25 AM Subject: Re: [nvda] Apple WWDC Keynote I think as an accessability issue to those not into apple its a staring case of apple centric ism in my view. They really need to get themselves sorted. Brian
bglists@... Sent via blueyonder. Please address personal email to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Alexander Masic" <list@...> To: <nvda@nvda.groups.io> Sent: Tuesday, June 06, 2017 4:51 AM Subject: Re: [nvda] Apple WWDC Keynote
> Hi. I'M not believe this is something wich belong to this list, however i > will reply anyway. > > You are only able to watch WWDC in PC by using EDGE. If you dont't have > Edge, you must follow it on other platforms. I know... The keynot have > already been, however you can stil watch it, and there is also other > stuff, for instans accessibility sesion wich still havebn't been and > intresteed for us. > > > > > Den 2017-06-05 kl. 18:54, skrev Lino Morales: >> Does anyone know how to watch the keynote with Edge using NVDA? Thanks. >> >> >> > > > >
|
|
Re: Incredibly odd problem with the NVDA modifier key
That's what I meant.
I have no idea why you and a number of people have
this experience while a lot of users don't. Perhaps sending relevant
information from the log to developers might be the best way to proceed. I
don't know enough about getting information from the log nor where to send it to
discuss the matter further but someone else probably will provide
information.
Gene
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 6:53 PM
Subject: Re: [nvda] Incredibly odd problem with the NVDA modifier
key
Gene,
Thank you for advocating for me on this so I didn't
have to again repeat myself. That is incredibly appreciated, and no. I do not
mean that sarcastically either. Really, I do thank you.
Yeah, it's the weirdest thing I've seen! And
just to answer your question, Gene, I'm using the standard American English
language with country region set to United States. I presume that is what you
meant.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
----- Original Message -----
Sent: Friday, June 09, 2017 3:14 AM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
Did you read the entire message? It says
that many machines of many different users were tried. It says that both
Windows 7 and Windows 10 were tried. It says that JAWS was tried and the
problem didn't exist. It is clear that the problem didn't exist before
installing 17.2. The message says:
Ever since updating to NVDA 2017.2, my numpad
insert key has completely stopped working as the NVDA
modifier.
It might be relevant to verify which version of
English the computers are set for and to try running 17.1 again but almost
every condition you asked about has been tested for, including running without
add ons.
Gene
----- Original Message -----
Sent: Friday, June 09, 2017 2:02 AM
Subject: Re: [nvda] Incredibly odd problem with the NVDA modifier
key
Hi I cannot duplicate this problem in Windows 7 with UK English
with either laptop or desktop set up with or without capslock set as
nvda key.
Suggestions. Something to do with maybe Windows 10
if this is in use on all machines Oddity in then add on or other software
running blocking that key combination from working. Only way to
prove its nvda is to go back to an old version and report back, but from
what you say that might not be ideal either.
I wonder what language is
set on the machine, could it be mapping that key before nvda gets to
it? Brian
bglists@... Sent
via blueyonder. Please address personal email to:- briang1@..., putting
'Brian Gaff' in the display name field. ----- Original Message -----
From: "Christopher-Mark Gilland" <clgilland07@...> To:
<nvda@nvda.groups.io> Sent:
Friday, June 09, 2017 12:11 AM Subject: [nvda] Incredibly odd problem with
the NVDA modifier key
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.
What gives!
Chris.
|
|
Could someone post the link to the next snapshot?
toggle quoted messageShow quoted text
On 6/9/17, Rosemarie Chavarria <knitqueen2007@gmail.com> wrote: Wow, that's gonna be neat!
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Lino Morales Sent: Friday, June 9, 2017 11:49 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Sapi 5 mobile add-on
Unless you'd like to run the next snapshot of NVDA. It will be included in NVDA 2017.3.
On 6/9/2017 1:58 PM, Joseph Norton wrote:
Hi:
It’s already installed in Windows 10 if you’re using US English. It’s just that NVDA doesn’t recognize it at this time.
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: David Mehler <mailto:dave.mehler@gmail.com> Sent: Friday, June 9, 2017 12:31 PM To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> Subject: Re: [nvda] Sapi 5 mobile add-on
Hello,
How do you get the mark voice mobile?
Thanks.
Dave.
On 6/9/17, Joseph Norton <mailto:joseph.norton@gmail.com> <joseph.norton@gmail.com> wrote:
Ah: That’s great. Both the Mark and Richard voices are fairly lively sounding and will make excellent alternatives. Not as responsive as eSpeak, but, they do add more choices. Thanks! Sent from Mail for Windows 10 From: Joseph Lee Sent: Friday, June 9, 2017 9:35 AM To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> Subject: Re: Sapi 5 mobile add-onRE: [nvda] Using Outlook Hi, There will come a day when you don’t have to visit that website nor install that add-on to use that synthesizer with NVDA. Cheers, Joseph From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Norton Sent: Thursday, June 8, 2017 9:24 PM To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> Subject: Sapi 5 mobile add-onRE: [nvda] Using Outlook Hi list: I found an add-on on the page called “Jeff’s NVDA Add-on Page” that allows NVDA to be used with the SAPI 5 mobile voices, of which there are 2 really perky ones, Mark in the US English category and Richard in the US Canada category. Was this written by NV Access. It says it was, but, it doesn't seem to be on the regular NVDA add-ons page, and, if it was written by NV Access, I would have thought it would be right there. This would seem to be a useful add-on to be readily available, but, maybe it's too bugy or something. Or, maybe I'm looking in the wrong place on the main NV Access add-ons pages. Any thoughts? Thanks! Sent from Mail for Windows 10
-- Lenron Brown Cell: 985-271-2832 Skype: ron.brown762
|
|
Re: NVDA Plugin Development Help!
Hi, This is something that requires deep hacks from plugins. I’ll forward your question to the development mailing list in hopes of getting an answer for you. Cheers, Joseph
toggle quoted messageShow quoted text
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of James Jenkins Sent: Friday, June 9, 2017 2:30 PM To: nvda@nvda.groups.io Subject: [nvda] NVDA Plugin Development Help! Hello everyone
I am still very new to NVDA but so far I have loved it. I have been looking at writing a plugin for NVDA that would enhance web browser navigation capabilities. I want to have the plugin be capable of navigating to other HTML tags other than the default ones that are supported (such as links, headings, landmarks, ect). For instance, the plugin would be capable of navigating to the next <section> or <hr> tag. I guess I should first ask if this is even possible? I've gone over a lot of the documentation for writing plugins as well as several of the .py files found on Github (especially the browseMode.py file and virtualBuffers folder). The closes thing I have found would be to add another QuickNav but I feel certain that this would not fully accomplish what I want. Am I on the right track? What do I need to do or learn to make this plugin a reality? Any help would be greatly apprecaited!
|
|
Re: Beware Jarte 6.1 folks
Christopher-Mark Gilland <clgilland07@...>
OK. Will have a look.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 8:15 PM
Subject: Re: [nvda] Beware Jarte 6.1
folks
http://www.jarte.com/jarte_plus.html
may be the answer you're looking for.
Antony.
On Friday 09 June
2017 20:05:06 Christopher-Mark Gilland wrote:
> You know... I'm so
glad this discussion has come up, as I was curious. > What're the main
differences in the Plus version vs. the free version? --- > Christopher
Gilland > Co-founder of Genuine Safe Haven Ministries
-- I
conclude that there are two ways of constructing a software design: One way
is to make it so simple that there are _obviously_ no deficiencies, and
the other way is to make it so complicated that there are no _obvious_
deficiencies.
- C A R
Hoare
Please reply to the
list;
please *don't* CC me.
|
|
Re: Beware Jarte 6.1 folks
toggle quoted messageShow quoted text
On Friday 09 June 2017 20:05:06 Christopher-Mark Gilland wrote: You know... I'm so glad this discussion has come up, as I was curious. What're the main differences in the Plus version vs. the free version? --- Christopher Gilland Co-founder of Genuine Safe Haven Ministries
-- I conclude that there are two ways of constructing a software design: One way is to make it so simple that there are _obviously_ no deficiencies, and the other way is to make it so complicated that there are no _obvious_ deficiencies.
- C A R Hoare
Please reply to the list; please *don't* CC me.
|
|
NVDA Plugin Development Help!
Hello everyone
I am still very new to NVDA but so far I have loved it. I have been looking at writing a plugin for NVDA that would enhance web browser navigation capabilities. I want to have the plugin be capable of navigating to other HTML tags other than the default ones that are supported (such as links, headings, landmarks, ect). For instance, the plugin would be capable of navigating to the next <section> or <hr> tag. I guess I should first ask if this is even possible? I've gone over a lot of the documentation for writing plugins as well as several of the .py files found on Github (especially the browseMode.py file and virtualBuffers folder). The closes thing I have found would be to add another QuickNav but I feel certain that this would not fully accomplish what I want. Am I on the right track? What do I need to do or learn to make this plugin a reality? Any help would be greatly apprecaited!
|
|
Christopher-Mark Gilland <clgilland07@...>
They are, but... there are other things,
accessibility not withstanding that're making me reconsider some things. That's
kind of off topic though, so I'll let it rest.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 5:38 PM
Subject: Re: [nvda] Apple WWDC
Keynote
Correct
me if I’m wrong but aren’t apple products and apps
accessible?
From: nvda@nvda.groups.io
[mailto:nvda@nvda.groups.io] On Behalf Of Christopher-Mark
Gilland Sent: Thursday, June 08, 2017 6:41 PM To: nvda@nvda.groups.io Subject:
Re: [nvda] Apple WWDC Keynote
No kidding. I used
to be quite an Apple fanatic, but I'm rapidly seeing the
light.
--- Christopher Gilland Co-founder of Genuine Safe
Haven Ministries
----- Original
Message -----
Sent: Tuesday, June
06, 2017 6:25 AM
Subject: Re: [nvda] Apple
WWDC Keynote
I think as an accessability
issue to those not into apple its a staring case of apple centric ism in
my view. They really need to get themselves
sorted. Brian
bglists@... Sent
via blueyonder. Please address personal email to:- briang1@..., putting
'Brian Gaff' in the display name field. ----- Original Message -----
From: "Alexander Masic" <list@...> To: <nvda@nvda.groups.io> Sent:
Tuesday, June 06, 2017 4:51 AM Subject: Re: [nvda] Apple WWDC
Keynote
> Hi. I'M not believe this is something wich belong to
this list, however i > will reply anyway. > > You are
only able to watch WWDC in PC by using EDGE. If you dont't have >
Edge, you must follow it on other platforms. I know... The keynot have
> already been, however you can stil watch it, and there is also
other > stuff, for instans accessibility sesion wich still havebn't
been and > intresteed for us. > > > > >
Den 2017-06-05 kl. 18:54, skrev Lino Morales: >> Does anyone know
how to watch the keynote with Edge using NVDA?
Thanks. >> >> >> > > > >
|
|
Re: Beware Jarte 6.1 folks
Christopher-Mark Gilland <clgilland07@...>
You know... I'm so glad this discussion has come
up, as I was curious. What're the main differences in the Plus version vs. the
free version?
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 6:07 AM
Subject: Re: [nvda] Beware Jarte 6.1
folks
I have Jarte plus and had no problem installing the latest
update on my windows 7 machine.
-----Original Message-----
From: Pauline Smith Sent: Friday, June 09, 2017 9:51 AM To: nvda@nvda.groups.io Subject: Re:
[nvda] Beware Jarte 6.1 folks
Good Morning,
Thanks for the
warning regarding the latest version of Jarte. For now, I will use the
older version.
Pauline
On 6/9/2017 2:47 AM, Brian's
Mail list account wrote: > I just tried to install it on my Windows 7
box and it claims it cannot > move a file during the install then
cannot continue any further. If you > force it then it cannot find a
file to run. > I've gone back to version 5.4 > >
Brian > > bglists@... >
Sent via blueyonder. > Please address personal email to:- > briang1@..., putting
'Brian Gaff' > in the display name
field. > > > >
|
|
Re: Incredibly odd problem with the NVDA modifier key
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
toggle quoted messageShow quoted text
----- 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
|
|
Re: Incredibly odd problem with the NVDA modifier key
Christopher-Mark Gilland <clgilland07@...>
About half the systems had JFW, so even with
systems which JFW's never ever touched, I'm seeing it.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 6:49 AM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
My thought was that since it's a bunch of different hardware and
different versions of Windows, BUT, it's something no-one else seems to have
reproduced, it could be some software running on those machines.
You mentioned trying Jaws. Do you have Jaws on all those
machines? Could you set Jaws NOT to run or run any of its helpers on
startup, reboot and see if that makes a difference? If Jaws is loading
something, even a non-speaking driver, in the background before NVDA, it might
be stealing the Insert key.
Jaws can also be funny about having the right display and audio drivers -
sometimes the standard "Microsoft" drivers just won't cut it and will cause
strange behaviour. Though, since the hardware is different, it's less
likely to be that specifically on all of them at once, but still potentially
could be Jaws in the background.
--
Quentin
Christensen Training and Support Manager
|
|
Re: Incredibly odd problem with the NVDA modifier key
Christopher-Mark Gilland <clgilland07@...>
Hi Antony.
Thanks for your suggestion.
Yes, I did indeed try, and anything 2017.1 or older
works just fine, regardless if it's a portable or not.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 6:49 AM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
Have you tried a portable copy of 2017.1 (or earlier) to see if
the problem then goes away?
This would help pin down whether the
problem is with 2017.2 specifically, or something else on your
machine.
Antony.
On Thursday 08 June 2017 19:11:41
Christopher-Mark Gilland 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. > > What gives! > >
Chris.
-- "I estimate there's a world market for about five
computers."
- Thomas J Watson, Chairman of
IBM
Please reply to the
list;
please *don't* CC me.
|
|
Re: Incredibly odd problem with the NVDA modifier key
Christopher-Mark Gilland <clgilland07@...>
Definitely no keylogger. I ran all security checks
etc, and all looks blimmish free. No Keyloggers, no adware, no malware, no
viruses, no trogens, nothing.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 6:37 AM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
Please, check if no KeyLogger or KeyTrapper is present on the
machines... It is the first time I hear such an error so easily reproduced
by you and not affecting the generality of users...
-----
Original Message ----- From: "Christopher-Mark Gilland" <clgilland07@...> To:
<nvda@nvda.groups.io> Sent:
Friday, June 09, 2017 12:11 AM Subject: [nvda] Incredibly odd problem with
the NVDA modifier key
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.
What
gives!
Chris.
|
|
Re: Does anyone know if NVDA works with the BlueStacks Android emulator?
You can use the emulator, but you would need to use Google Talkback inside it. NVDA won't read these screens, but you can install it fairly well with NVDA.
toggle quoted messageShow quoted text
On 6/9/17, Sharni-Lee Ward <sharni-lee.ward@hotmail.com> wrote: I'm asking because my mum and sister are playing this awesome app-based game that I could only play on PC with this emulator installed. I know Google things are pretty accessible but I'm not sure about this and I'd love to know if anyone else has tried something like this. I'd ask if the app I want this emulator for is accessible enough for me to play but if the emulator isn't, the app won't be, so I'll start there.
|
|
Does anyone know if NVDA works with the BlueStacks Android emulator?
I'm asking because my mum and sister are playing this awesome app-based game that I could only play on PC with this emulator installed. I know Google things are pretty accessible but I'm not sure about this and I'd love to know if anyone else has tried something like this. I'd ask if the app I want this emulator for is accessible enough for me to play but if the emulator isn't, the app won't be, so I'll start there.
|
|
Re: Incredibly odd problem with the NVDA modifier key
Christopher-Mark Gilland <clgilland07@...>
Brian,
You have a point there, but I already did try an
older version, and it works just fine.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 3:21 AM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
Yes, but the thing is that its not showing up here. And I think
what is needed is to uninstall and reinstall the old version just to be
sure its nvda as nobody in the thread seems to be having any more luck
than I am.
Brian
bglists@... Sent
via blueyonder. Please address personal email to:- briang1@..., putting
'Brian Gaff' in the display name field. ----- Original Message -----
From: "Gene" <gsasner@...> To: <nvda@nvda.groups.io> Sent: Friday,
June 09, 2017 8:14 AM Subject: Re: [nvda] Incredibly odd problem with the
NVDA modifier key
Did you read the entire message? It says
that many machines of many different users were tried. It says that
both Windows 7 and Windows 10 were tried. It says that JAWS was
tried and the problem didn't exist. It is clear that the problem
didn't exist before installing 17.2. The message says: Ever since
updating to NVDA 2017.2, my numpad insert key has completely stopped
working as the NVDA modifier.
It might be relevant to verify which
version of English the computers are set for and to try running 17.1 again
but almost every condition you asked about has been tested for, including
running without add ons.
Gene ----- Original Message
-----
From: Brian's Mail list account Sent: Friday, June 09, 2017
2:02 AM To: nvda@nvda.groups.io Subject: Re:
[nvda] Incredibly odd problem with the NVDA modifier key
Hi I
cannot duplicate this problem in Windows 7 with UK English with
either laptop or desktop set up with or without capslock set as nvda
key.
Suggestions. Something to do with maybe Windows 10 if
this is in use on all machines Oddity in then add on or other software
running blocking that key combination from working. Only way to
prove its nvda is to go back to an old version and report back, but from
what you say that might not be ideal either.
I wonder what language is
set on the machine, could it be mapping that key before nvda gets to
it? Brian
bglists@... Sent
via blueyonder. Please address personal email to:- briang1@..., putting
'Brian Gaff' in the display name field. ----- Original Message -----
From: "Christopher-Mark Gilland" <clgilland07@...> To:
<nvda@nvda.groups.io> Sent:
Friday, June 09, 2017 12:11 AM Subject: [nvda] Incredibly odd problem with
the NVDA modifier key
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.
What
gives!
Chris.
|
|
Re: Incredibly odd problem with the NVDA modifier key
Christopher-Mark Gilland <clgilland07@...>
Gene,
Thank you for advocating for me on this so I didn't
have to again repeat myself. That is incredibly appreciated, and no. I do not
mean that sarcastically either. Really, I do thank you.
Yeah, it's the weirdest thing I've seen! And
just to answer your question, Gene, I'm using the standard American English
language with country region set to United States. I presume that is what you
meant.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 3:14 AM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
Did you read the entire message? It says
that many machines of many different users were tried. It says that both
Windows 7 and Windows 10 were tried. It says that JAWS was tried and the
problem didn't exist. It is clear that the problem didn't exist before
installing 17.2. The message says:
Ever since updating to NVDA 2017.2, my numpad
insert key has completely stopped working as the NVDA
modifier.
It might be relevant to verify which version of
English the computers are set for and to try running 17.1 again but almost
every condition you asked about has been tested for, including running without
add ons.
Gene
----- Original Message -----
Sent: Friday, June 09, 2017 2:02 AM
Subject: Re: [nvda] Incredibly odd problem with the NVDA modifier
key
Hi I cannot duplicate this problem in Windows 7 with UK English
with either laptop or desktop set up with or without capslock set as
nvda key.
Suggestions. Something to do with maybe Windows 10
if this is in use on all machines Oddity in then add on or other software
running blocking that key combination from working. Only way to
prove its nvda is to go back to an old version and report back, but from
what you say that might not be ideal either.
I wonder what language is
set on the machine, could it be mapping that key before nvda gets to
it? Brian
bglists@... Sent
via blueyonder. Please address personal email to:- briang1@..., putting
'Brian Gaff' in the display name field. ----- Original Message -----
From: "Christopher-Mark Gilland" <clgilland07@...> To:
<nvda@nvda.groups.io> Sent:
Friday, June 09, 2017 12:11 AM Subject: [nvda] Incredibly odd problem with
the NVDA modifier key
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.
What gives!
Chris.
|
|
Re: Incredibly odd problem with the NVDA modifier key
Christopher-Mark Gilland <clgilland07@...>
I actually did try an older version, and in doing
so, the caps lock and numpad insert both work beautifully.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 3:02 AM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
Hi I cannot duplicate this problem in Windows 7 with UK English
with either laptop or desktop set up with or without capslock set as
nvda key.
Suggestions. Something to do with maybe Windows 10
if this is in use on all machines Oddity in then add on or other software
running blocking that key combination from working. Only way to
prove its nvda is to go back to an old version and report back, but from
what you say that might not be ideal either.
I wonder what language is
set on the machine, could it be mapping that key before nvda gets to
it? Brian
bglists@... Sent
via blueyonder. Please address personal email to:- briang1@..., putting
'Brian Gaff' in the display name field. ----- Original Message -----
From: "Christopher-Mark Gilland" <clgilland07@...> To:
<nvda@nvda.groups.io> Sent:
Friday, June 09, 2017 12:11 AM Subject: [nvda] Incredibly odd problem with
the NVDA modifier key
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.
What
gives!
Chris.
|
|
Re: Incredibly odd problem with the NVDA modifier key
Christopher-Mark Gilland <clgilland07@...>
No. They are set correctly on US American English
standard 101.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, June 09, 2017 2:06 AM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
Keyboard language settings?
Only thing that comes to mind.
Jacob Kruger
Blind Biker
Skype: BlindZA
"Resistance is futile, but, acceptance is versatile..."
On 2017-06-09 02:45, Quentin Christensen
wrote:
I knew you would know the difference, I'm just running out of
ideas to check :)
I'll keep thinking on it and check with Mick and Jamie.
|
|