Date   

Re: Sapi 5 mobile add-onRE: [nvda] Using Outlook

Steve Nutt
 

Hi,

 

They are not SAPI 5, they are Windows Platform voices.

 

All the best


Steve

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Norton
Sent: 09 June 2017 05:24
To: 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


Re: W10 creators update

Steve Nutt
 

Eh?

 

You can do all the ways you used to do.  You can press Windows-D then F4.  You can switch off by just pressing the power button if you have it programmed.  There are loads of ways to do it.

 

All the best

 

Steve

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of slery
Sent: 09 June 2017 05:32
To: nvda@nvda.groups.io
Subject: Re: [nvda] W10 creators update

 

I get to the shut down button every day using the keyboard. Press windows key, tab (this takes you to the navigation pane) and arrow down till you get the right button.

 

I find it very annoying that so many things now take you multiple steps to do when the used to be one or two steps.

 

Cindy

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of The Gamages
Sent: Friday, June 02, 2017 10:46 AM
To: nvda@nvda.groups.io
Subject: [nvda] W10 creators update

 

I have been looking at the content of the new creators update for W 10, it seems, as always, there is little to make our lives easier as blind and visually impaired.  Three D pictures and gaming, plus “improved” edge browser.

It would be better if theyconcentrated on things that have gone wrong so far, one such is the innability of getting to the power button with the keyboard, I don’t thinl this is only me as others have reported it on freelists, it’s stil there and accessigble with the mouse, but the keyboard? no, I can close down with alt f4 of course, but that’s not the point.

After all that, do you think this is going to be yet another of those updates  which will install whether we like it or not? it seems likely if we have automatic updates set.  I don’t want it at any price, it will do nothing to make my life easier, indeed, it may even make it harder and more complicated.

What is your opinion on the subject? I know Microsoft intend to ask if we want to do anything with our settings, but we should have the option of refusing this update, it’s the thing that I don’t like about W10, it seems to want to do things to our machines whether we want it or not, I state as an example that my Wife’s photos were put into completely different folders without her permission when she got the anniversary update, I suppose she must have clicked to say she wanted it, but she can’t remember doing any such thing.

O K rant over, comments please!!!

 

Jim.


Re: Incredibly odd problem with the NVDA modifier key

Steve Nutt
 

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.

 

What gives!

 

Chris.



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Beware Jarte 6.1 folks

Sharni-Lee Ward
 

That's odd. I installed Jarte 6.1 a while ago and had no issues
accessing my files afterward. It's been working just fine.

On 9/06/2017 4:47 PM, 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.



Where are the add-ons hiding?

Ann Byrne <annakb@...>
 

What is the address for the addons page???

Thanks,


Re: Changing the name of say all command

Steve Nutt
 

Hi,

It's based on what JAWS calls it I believe. Window-Eyes called it Read To End, and Supernova calls it Read From Here.

All the best

Steve

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Andre Fisher
Sent: 08 June 2017 13:02
To: nvda@nvda.groups.io
Subject: Re: [nvda] Changing the name of say all command

Hi.

Read to end would be more ideal. However, I think this is based on the tradition of the screen reader.

On 6/8/17, Gene <gsasner@...> wrote:
Say all is not a proper description of the NVDA key down arrow command.
That command doesn't say all unless you start at the beginning of a
document. It starts to speak or read, from your current position in
the document. Also, say all sounds like an adjustment in screen echo.
The name should be changed to something like read to end, or speak to
end. I don't use a Braille display so I don't know if the command would be used there.
If not, speak to end would be best.

Gene


Silly question but I'll ask anyway!

Brian's Mail list account
 

I see the latest snap is merge master into Next, how is it then that when you do this you don't end up with the original sound effects back in next.
I prefer them myself over the new ones any day.
The new ones make me think of some old Atari arcade games from the80s! Sorry if someone hear is the author.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.


Re: NVDA 2017.2 RC1 and Edge, a navigation problem

Brian's Mail list account
 

Hi have you installed the latest full release version?
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Sakina" <sakina.gable@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 09, 2017 12:18 PM
Subject: Re: [nvda] NVDA 2017.2 RC1 and Edge, a navigation problem


Dear Felix

I get the same reply as Quentin from Microsoft edge that it is trying but I
have better things to do and try again.

With best wishes and regard alwayss

Sakina



_____

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin
Christensen
Sent: Friday, May 26, 2017 8:17 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2017.2 RC1 and Edge, a navigation problem



Hi Felix,



Can you advise whether you experienced the same thing with earlier versions
of NVDA or whether this is new in the RC build?



I just tried and what seems to happen is I can tab around, but as soon as I
press H or 1 or other keys, NVDA stops reading, and then shortly after, the
page reloads. I can repeat that a couple of times before Edge gives me a
message saying: "


This page is having a problem loading


We tried to load this page for you a few times, but there is still a problem
with this site. We know you have better things to do than to watch this page
reload over and over again so try coming back to this page later."



That seems to behave exactly the same way using NVDA 2017.1 and NVDA
2017.2rc1



I see you've reported it and Jamie is on to reporting it to Microsoft:
https://github.com/nvaccess/nvda/issues/7206



Regards



Quentin.



On Wed, May 24, 2017 at 11:44 PM, Felix G. <constantlyvariable@...>
wrote:

Hello,

could someone please advise on what I might be doing wrong, or where I may
be expecting the wrong outcome, in the following scenario?

With Edge I go to www.heise.de. I know from Firefox and Chrome experience
that there are lots of headings, but when I then press h nothing happens,
and afterwards navigation with the arrow keys stops working. I am reluctant
to assume a bug as I assume heading navigation has been tested extensively
for this RC. Any ideas what might be going on?

Kind regards,

Felix







--

Quentin Christensen
Training and Support Manager



Basic Training for NVDA & Microsoft Word with NVDA E-Books now available:
http://www.nvaccess.org/shop/



Ph <tel:%2B61%207%203149%203306> +61 7 3149 3306

<http://www.nvaccess.org/> www.nvaccess.org
Facebook: <http://www.facebook.com/NVAccess>
http://www.facebook.com/NVAccess
Twitter: @NVAccess






Re: Sapi 5 mobile add-onRE: [nvda] Using Outlook

Brian's Mail list account
 

I'm seeing this email lots of times.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 09, 2017 2:35 PM
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] On Behalf Of Joseph Norton
Sent: Thursday, June 8, 2017 9:24 PM
To: 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 <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10


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] On Behalf Of Joseph Norton
Sent: Thursday, June 8, 2017 9:24 PM
To: 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


Re: NVDA 2017.2 RC1 and Edge, a navigation problem

Sakina
 

Dear Felix

I get the same reply as Quentin from Microsoft edge  that it is trying but I have better things to do and try again.

With best wishes and regard alwayss  

Sakina

 


From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Friday, May 26, 2017 8:17 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2017.2 RC1 and Edge, a navigation problem

 

Hi Felix,

 

Can you advise whether you experienced the same thing with earlier versions of NVDA or whether this is new in the RC build?

 

I just tried and what seems to happen is I can tab around, but as soon as I press H or 1 or other keys, NVDA stops reading, and then shortly after, the page reloads.  I can repeat that a couple of times before Edge gives me a message saying: "

This page is having a problem loading

We tried to load this page for you a few times, but there is still a problem with this site. We know you have better things to do than to watch this page reload over and over again so try coming back to this page later."

 

That seems to behave exactly the same way using NVDA 2017.1 and NVDA 2017.2rc1

 

I see you've reported it and Jamie is on to reporting it to Microsoft: https://github.com/nvaccess/nvda/issues/7206

 

Regards

 

Quentin.

 

On Wed, May 24, 2017 at 11:44 PM, Felix G. <constantlyvariable@...> wrote:

Hello,

could someone please advise on what I might be doing wrong, or where I may be expecting the wrong outcome, in the following scenario?

With Edge I go to www.heise.de. I know from Firefox and Chrome experience that there are lots of headings, but when I then press h nothing happens, and afterwards navigation with the arrow keys stops working. I am reluctant to assume a bug as I assume heading navigation has been tested extensively for this RC. Any ideas what might be going on?

Kind regards,

Felix



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Virus-free. www.avast.com


Re: Incredibly odd problem with the NVDA modifier key

Quentin Christensen
 

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.

On Fri, Jun 9, 2017 at 8:37 PM, Rui Fontes <rui.fontes@...> wrote:
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.












--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Incredibly odd problem with the NVDA modifier key

Antony Stone
 

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

Rui Fontes
 

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: Beware Jarte 6.1 folks

Peter Beasley
 

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: Beware Jarte 6.1 folks

Pauline Smith <paulinesmithh@...>
 

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

Jacob Kruger
 

Gene, etc., 2017.2 works just fine here on my windows 10 64 bit creators update machine, both in installed and portable versions, with the numpad insert key doing it's job as well.


So, really don't think it's a general NVDA issue.


Stay well


Jacob Kruger
Blind Biker
Skype: BlindZA
"Resistance is futile, but, acceptance is versatile..."
On 2017-06-09 09:28, Gene wrote:

Just running it as a portable is probably sufficient.  Running the new version as a portable is reported to have the same problem.  Or even just using the continue running option instead of installing it or creating a portable version should be sufficient.  I haven't seen this discussed anywhere, but as far as I can tell by doing so, using the continue running option runs NVDA as though it were a portable copy but since it is running from the installer and no files have been extracted, no settings are saved. 
 
Gene
----- Original Message -----
Sent: Friday, June 09, 2017 2: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: Changing the name of say all command

anthony borg
 

Thanks quentin, for the explanation.

 

Best regards

 

Anthony

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: 09 June 2017 01:13
To: nvda@nvda.groups.io
Subject: Re: [nvda] Changing the name of say all command

 

Hi Anthony,

 

The command to read to end (called "Say All", even though it reads from the current point onwards, as the thread is talking about), is NVDA+down arrow if you use desktop layout, and NVDA+a in Laptop layout.

 

Regards

 

Quentin.

 

On Fri, Jun 9, 2017 at 12:20 AM, anthony borg <anthonyborg001@...> wrote:

Hi gene what is the command to speak to end? Or read to end?

Thanks in advance

Anthony

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Andre Fisher
Sent: 08 June 2017 14:02
To: nvda@nvda.groups.io
Subject: Re: [nvda] Changing the name of say all command

Hi.

Read to end would be more ideal. However, I think this is based on the tradition of the screen reader.

On 6/8/17, Gene <gsasner@...> wrote:
> Say all is not a proper description of the NVDA key down arrow command.
> That command doesn't say all unless you start at the beginning of a
> document.  It starts to speak or read, from your current position in
> the document.  Also, say all sounds like an adjustment in screen echo.
> The name should be changed to something like read to end, or speak to
> end.  I don't use a Braille display so I don't know if the command would be used there.
> If not, speak to end would be best.
>
> Gene
>







 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Incredibly odd problem with the NVDA modifier key

Gene
 

Just running it as a portable is probably sufficient.  Running the new version as a portable is reported to have the same problem.  Or even just using the continue running option instead of installing it or creating a portable version should be sufficient.  I haven't seen this discussed anywhere, but as far as I can tell by doing so, using the continue running option runs NVDA as though it were a portable copy but since it is running from the installer and no files have been extracted, no settings are saved. 
 
Gene

----- Original Message -----
Sent: Friday, June 09, 2017 2: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: query

Gene
 

I should clarify that for general use, I don't know if it makes a difference if you use the laptop or desktop layout.  I haven't used the laptop layout so I can't compare them in general.  I have looked at some of the commands used in object navigation and in screen review.  I consider the desktop layout to be far superior in organization of those commands.  That's why I recommended the desktop layout. 
 
Gene

----- Original Message -----
Sent: Friday, June 09, 2017 2:20 AM
Subject: Re: [nvda] query

Hi gene

 

Sorry  first of all that I couldn’t reply to your email yesterday, I really appreciated your support and the instructions you have sent me.

 

Many thanks once again for your help,

 

Best regards

 

Anthony

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: 08 June 2017 19:46
To: nvda@nvda.groups.io
Subject: Re: [nvda] query

 

Since it has a numpad, it would be much better to use the desktop layout.  You were trying to use a laptop layout command for read current line. The desktop layout command is NVDA key up arrow.  Since you have a numpad, you will likely want to use the numpad insert in many cases for the NVDA key. 

But there are times when it is much easier and more pleasant to use the capslock as an NVDA key.  If you do, the command would be caps lock up arrow for speak current line. 

 

To enable the caps lock as an NVDA key do the following:

Open the keyboard settings dialog with the command control NVDA key k.  Since you don't have the capslock set as an NVDA key yet, use either insert.

Then tab to a check box that says use caps lock as NVDA key or similar wording.  Check it with the space bar. 

Then tab to and activate the ok button.

Now, you can have the current line spoken by holding the caps lock key and whild doing so press up arrow.  If a command is awkward or unpleasant using whatever insert you want to use, you can use the caps lock.  You can still use either insert but now you can use the caps lock as well, if you prefer.

 

Gene

----- Origianal Message ------

 

From: anthony borg

Sent: Thursday, June 08, 2017 9:36 AM

Subject: Re: [nvda] query

 

Hi gene

 

Yes my laptop has a numpad, the reason why I’m asking so many questions is because I just started to learn how to use the NVDA.

 

And I’m pretty sure that all of you have more experience than I have.

 

Best regards

 

Anthony

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: 08 June 2017 11:37
To: nvda@nvda.groups.io
Subject: Re: [nvda] query

 

NVDA down arrow is read to end.  Does the laptop have a numpad?  The only reason to use the laptop layout is if the laptop doesn't have a numpad. 

 

If it were me, I'd probably buy a USB numpad and use the desktop layout.  I don't like laptop layouts in any screen-reader. 

 

I don't know where or how your are looking at commands but you appear to somehow be looking at them incorrectly.  Are you using the quick key reference in help>  In that reference, commands are given as desktop layout, then on the next line laptop, then touch gesture, if any. 

 

Gene

----- Original Message -----

From: anthony borg

Sent: Thursday, June 08, 2017 4:11 AM

Subject: Re: [nvda] query

 

Hi gene

 

Many thanks for your prompt reply, yes I guess as you said I have to change to laptop mode, 

 

To read the current line I use the NVDA key plus down arrow as you explained, but it keeps reading the whole page as well.

 

I hope you will be able to understand what I mean.

 

Best regards

 

Anthony  

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene New Zealand
Sent: 08 June 2017 10:26
To: nvda@nvda.groups.io
Subject: Re: [nvda] query

 

hi

 

how are you driving nvda on the computer and is your keyboard layout set to desktop or laptop? the default if i remember is desktop and can be changed under the keyboard settings in NVDA.

 

Are you arrowing down line by line with the down arrow key? or do you want it to read the current line? it is the nvda key + up arrow key to read the current line with a desktop.

 

I am also guessing in the document formatting section of nvda you have the following checked. for example line numbers checked. Uncheck it then tab down to the ok button then press the enter key. NVDA might have to be restarted for it to take affect. Then try it again.

 

Gene nz

 

 

On 8/06/2017 8:01 PM, anthony borg wrote:

Hello all

 

Can somebody explain to me, what I should do to read a current line because according to the guide, I should press NVDA plus control plus the fullstop,but it didn’t work.

 

The second question is, what should I do to stop the NVDA to read the number of each line in an email or document?

 

Thanks in advance

 

Anthony     

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Edward Green
Sent: 07 June 2017 21:52
To: nvda@nvda.groups.io
Subject: query

 

Hi Devin,


Go to the NVDA menu with NVDA+N, go into Preferences, and choose Punctuation/Symbol pronunciation.

 

You can stop it saying “Carriage return” in there.

 

Cheers,

 

Ed

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Devin Prater
Sent: 07 June 2017 15:24
To: nvda@nvda.groups.io
Subject: Re: [nvda] Carriage return

 

I’m talking about using right arrow. Carriage return just sounds really wordy and I’m not sure new users would know what it means. No, I guess Blank wouldn’t be best, but new line would be great.

 

Devin Prater
Assistive Technology Instructor in training, JAWS certified.

 

From: Gene
Sent: Wednesday, June 7, 2017 9:21 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Carriage return

 

What are you describing?  If I down arrow through a document in any application, a blank line is announced as blank.  If I move character by character, a carriage return is announced as carriage return.  I suppose this could be shortened to return but I don't have any feelings about that one way or another.  But there should certainly be a distinction of this type when moving by character.  Saying blank is inaccurate when moving by character but it isn't blank.  It’s a formatting character.

 

Are you saying that in the Windows e-mail app, when moving by down arrowing blank lines aren't indicated with the word blank? 

 

Gene

----- Original Message -----

 

From: Devin Prater

Sent: Wednesday, June 07, 2017 8:41 AM

Subject: [nvda] Carriage return

 

Hi all. Coming from Linux and Mac, I was a little surprised to find that, at least in the Windows 10 mail app, NVDA shows a new line as carriage return. Is this necessary now? Shouldn’t this be changed to something more understandable, like new line, or even blank?

 

Devin Prater
Assistive Technology Instructor in training, JAWS certified.

 

 

 

--

Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.

81441 - 81460 of 101169