1. nvda@nvda.groups.io
   Date   
Re: Enhanced Touch Gestures 19.11 #addonrelease

Sarah k Alawami
 

Oh, come on! Not again. Just update and get it over with. Do yourself and us a favior as I'm beginign to get the inkling to ask the mods to block every question fo yourse as you are using outdated softwares, and I mean very updated. See you on the otherside if someone hacks your computer because of it. We will not and cannot help you, sorry bud.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.

to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 29 Nov 2019, at 0:43, zahra wrote:

hi joseph.
does it support my favorite version of nvda, (2017.2)?
God bless you!

On 11/29/19, Joseph Lee joseph.lee22590@... wrote:

Hi all,

Enhanced Touch Gestures 19.11 is now available. Apart from localization
updates, the biggest change is addition of input help mode messages for
additional touch commands that come with this add-on.

IMPORTANT: this version is the last version to be compatible with NVDA
2019.2.1 and earlier.

Cheers,

Joseph

--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali
Regular expression in the dictionary [Re: Expression régulière dans le dictionnaire]

Brian Vogel
 

On Fri, Nov 29, 2019 at 03:54 AM, Sylvain Machefert wrote:
Le manuel n'explique pas les expressions régulières mais ne donne pas un seul petit exemple.
Certes, expliquer les expressions régulières n'est pas le but de la documentation de NVDA, mais que dois-je mettre pour que "get" (g e t) et "set" (s e t) soient prononcés correctement en début de mot ? Respectivement "guette" et "sette".... très utile en programmation.
English Translation:

The handbook does not explain the regular expressions but does not give only one small example.  Admittedly, to explain the regular expressions is not the goal of the documentation of NVDA, but what must I put so that “get” (G E T) and “set” (SET) correctly marked at the beginning of word? Respectively “watches for” and “sette”…. very useful in programming.

----------------------------------------------------------------

While there are absolutely no language restrictions on the NVDA group, as a matter of practicality it is primarily an English language group.

To capture a character sequence that is at the beginning of a word, but that may or may not be the whole word, you can use the word boundary operator, \b, to anchor to a word boundary, generally white space in any amount, or a newline, preceding a word, then couple this with a wildcard for "word characters, \w, afterward occurring zero or more times.  So, to match anything starting with the characters "set" you would use:

                     \bset\w*

This would match the word "set" and the word "settings" in the first two sentences, but not "inset" in the third:

         I need to set the table.  How many place settings do we have?  The niche is inset by 5 inches.

There are myriad tutorials on Regular Expressions on the web, and quite a few tools for testing the regular expressions you create (though I do not believe a lot of them would be accessible because visual highlighting is what's used to indicate what is and is not matched).

This page gets into real detail about matching word boundaries, probably too much:  https://www.regular-expressions.info/wordboundaries.html

There are also a lot of cheat sheets out there for the most common kinds of matching. 
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Most of the change we think we see in life is due to truths being in and out of favor.

         ~ Robert Frost, The Black Cottage (1914)

 

 
Re: issue with extention confirmed

Kelly Sapergia
 

Hi,

I also updated the WinAmp add-on to version 1.2 the other day. I can get to
WinAmp just fine, but the playlist editor doesn't work well with NVDA
anymore. Moving through the list with Up and Down arrow doesn't say what
song you're on, and pressing NVDA+Tab won't read the information that way
either now. I ended up having to disable the add-on, and can now move
through the playlist just fine.

Hope this helps.

Yours Sincerely,
Kelly John Sapergia
Show Host and Production Director
The Global Voice Internet Radio
www.theglobalvoice.info

Personal Website: www.ksapergia.net
Business Site (KJS Productions): www.kjsproductions.com
Follow me on Twitter at: kjsapergia
Re: issue with extention confirmed

Howard Traxler
 

Where is that extention for winamp and how do I know if I have it loaded or running?  Further, how to get rid of it?  Thanks.
Howard

On 11/29/2019 6:29 AM, ken lawrence via Groups.Io wrote:

Hi listers I updated the extention for winamp the other day and as reported originally the extention made winamp invisible the NVDA can’t even read with insirt plus T that you are sitting on winamp. I had to disable the extention.  Just now after downloading a song and tagging in winamp for possible play on a radio show I decided to enable the add on and sure enough winamp vanished.  It is running but I can’t apparently even go to my context menu to view file information.  I can tag files but I have to guess what I’m focused on to do it.  Is anyone else having issues with winamp extention version 1.2? 

 

Sent from Mail for Windows 10

 
Re: issue with extention confirmed

Gene
 

Do you have a shortcut key for Winamp such as control alt p?  Try playing something, then activating the shortcut twice while the file is playing.  I have no idea if it will bring the program into focus but in Windows 7, doing that moves NVDA to Winamp while it is running.  But the focus problem doesn't exist in the first place and I can alt tab to it as well.
 
Gene

----- Original Message -----
Sent: Friday, November 29, 2019 6:47 AM
Subject: Re: [nvda] issue with extention confirmed

Hi Ken,

I cannot confirm your issue with Winamp as such.  However, there is a long standing issue that I have had since upgrading to Windows 10 and using Winamp. 

What happens is that if I click on an audio file in Windows Explorer Winamp will play but NVDA  won't focus on Winamp.  That is to say, NVDA will stay focused on the file in Windows Explorer that I have just clicked on.  If I then Press alt + tab and focus on Winamp and then release the keystroke, NVDA still will not focus on Winamp.  If I press insert + T to read the title bar after this second step, NVDA says 'explorer window.'  If I then press alt + tab to focus on Winamp again, this second time, focus stays on Winamp.

That is and has been happening for a few years, my big issue with Winamp.  If  I run Winamp from the desktop, this issue does not occur.


On 11/29/2019 7:29 AM, ken lawrence via Groups.Io wrote:

Hi listers I updated the extention for winamp the other day and as reported originally the extention made winamp invisible the NVDA can’t even read with insirt plus T that you are sitting on winamp. I had to disable the extention.  Just now after downloading a song and tagging in winamp for possible play on a radio show I decided to enable the add on and sure enough winamp vanished.  It is running but I can’t apparently even go to my context menu to view file information.  I can tag files but I have to guess what I’m focused on to do it.  Is anyone else having issues with winamp extention version 1.2? 

 

Sent from Mail for Windows 10

 


-- 
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"
Re: issue with extention confirmed

Ron Canazzi
 

Hi Ken,

I cannot confirm your issue with Winamp as such.  However, there is a long standing issue that I have had since upgrading to Windows 10 and using Winamp. 

What happens is that if I click on an audio file in Windows Explorer Winamp will play but NVDA  won't focus on Winamp.  That is to say, NVDA will stay focused on the file in Windows Explorer that I have just clicked on.  If I then Press alt + tab and focus on Winamp and then release the keystroke, NVDA still will not focus on Winamp.  If I press insert + T to read the title bar after this second step, NVDA says 'explorer window.'  If I then press alt + tab to focus on Winamp again, this second time, focus stays on Winamp.

That is and has been happening for a few years, my big issue with Winamp.  If  I run Winamp from the desktop, this issue does not occur.


On 11/29/2019 7:29 AM, ken lawrence via Groups.Io wrote:

Hi listers I updated the extention for winamp the other day and as reported originally the extention made winamp invisible the NVDA can’t even read with insirt plus T that you are sitting on winamp. I had to disable the extention.  Just now after downloading a song and tagging in winamp for possible play on a radio show I decided to enable the add on and sure enough winamp vanished.  It is running but I can’t apparently even go to my context menu to view file information.  I can tag files but I have to guess what I’m focused on to do it.  Is anyone else having issues with winamp extention version 1.2? 

 

Sent from Mail for Windows 10

 


-- 
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"
Re: issue with extention confirmed

Gene
 

Is the old one still compatible with the version of Winamp you are using?
 
Gene

----- Original Message -----
Sent: Friday, November 29, 2019 6:29 AM
Subject: [nvda] issue with extention confirmed

Hi listers I updated the extention for winamp the other day and as reported originally the extention made winamp invisible the NVDA can’t even read with insirt plus T that you are sitting on winamp. I had to disable the extention.  Just now after downloading a song and tagging in winamp for possible play on a radio show I decided to enable the add on and sure enough winamp vanished.  It is running but I can’t apparently even go to my context menu to view file information.  I can tag files but I have to guess what I’m focused on to do it.  Is anyone else having issues with winamp extention version 1.2? 

 

Sent from Mail for Windows 10

 
Re: issue with extention confirmed

Joseph Lee
 

Hi,

Does restarting NVDA help?

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of ken lawrence via Groups.Io
Sent: Friday, November 29, 2019 4:29 AM
To: nvda@nvda.groups.io
Subject: [nvda] issue with extention confirmed

 

Hi listers I updated the extention for winamp the other day and as reported originally the extention made winamp invisible the NVDA can’t even read with insirt plus T that you are sitting on winamp. I had to disable the extention.  Just now after downloading a song and tagging in winamp for possible play on a radio show I decided to enable the add on and sure enough winamp vanished.  It is running but I can’t apparently even go to my context menu to view file information.  I can tag files but I have to guess what I’m focused on to do it.  Is anyone else having issues with winamp extention version 1.2? 

 

Sent from Mail for Windows 10

 
issue with extention confirmed

ken lawrence
 

Hi listers I updated the extention for winamp the other day and as reported originally the extention made winamp invisible the NVDA can’t even read with insirt plus T that you are sitting on winamp. I had to disable the extention.  Just now after downloading a song and tagging in winamp for possible play on a radio show I decided to enable the add on and sure enough winamp vanished.  It is running but I can’t apparently even go to my context menu to view file information.  I can tag files but I have to guess what I’m focused on to do it.  Is anyone else having issues with winamp extention version 1.2? 

 

Sent from Mail for Windows 10

 
Re: Enhanced Touch Gestures 19.11 #addonrelease

Joseph Lee
 

Hi,
Enhanced Touch Gestures requires Windows 8.1 or 10 and NVDA 2018.2 or later. Next year, anything below 2019.3 will be dropped.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of molly the blind tech lover
Sent: Friday, November 29, 2019 1:54 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Enhanced Touch Gestures 19.11 #AddonRelease

Hi.
You will likely need to update your NVDA for the add-on to work.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of zahra
Sent: Friday, November 29, 2019 3:44 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Enhanced Touch Gestures 19.11 #AddonRelease

hi joseph.
does it support my favorite version of nvda, (2017.2)?
God bless you!

On 11/29/19, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi all,



Enhanced Touch Gestures 19.11 is now available. Apart from
localization updates, the biggest change is addition of input help
mode messages for additional touch commands that come with this add-on.



IMPORTANT: this version is the last version to be compatible with NVDA
2019.2.1 and earlier.

Cheers,

Joseph





--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali
Re: Enhanced Touch Gestures 19.11 #addonrelease

molly the blind tech lover
 

Hi.
You will likely need to update your NVDA for the add-on to work.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of zahra
Sent: Friday, November 29, 2019 3:44 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Enhanced Touch Gestures 19.11 #AddonRelease

hi joseph.
does it support my favorite version of nvda, (2017.2)?
God bless you!

On 11/29/19, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi all,



Enhanced Touch Gestures 19.11 is now available. Apart from
localization updates, the biggest change is addition of input help
mode messages for additional touch commands that come with this add-on.



IMPORTANT: this version is the last version to be compatible with NVDA
2019.2.1 and earlier.

Cheers,

Joseph





--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali
Regular expression in the dictionary [Re: Expression régulière dans le dictionnaire]

Sylvain Machefert
 

Bonjour,

Le manuel n'explique pas les expressions régulières mais ne donne pas un seul petit exemple.
Certes, expliquer les expressions régulières n'est pas le but de la documentation de NVDA, mais que dois-je mettre pour que "get" (g e t) et "set" (s e t) soient prononcés correctement en début de mot ? Respectivement "guette" et "sette".... très utile en programmation.

Merci


--
Sylvain Machefert
Re: Enhanced Touch Gestures 19.11 #addonrelease

zahra
 

hi joseph.
does it support my favorite version of nvda, (2017.2)?
God bless you!

On 11/29/19, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi all,



Enhanced Touch Gestures 19.11 is now available. Apart from localization
updates, the biggest change is addition of input help mode messages for
additional touch commands that come with this add-on.



IMPORTANT: this version is the last version to be compatible with NVDA
2019.2.1 and earlier.

Cheers,

Joseph




--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali
In-Process 29th November

Quentin Christensen
 

Hi everyone,

Firstly, Happy Thanksgiving to all our American friends!  

We've got a big In-Process for you this week:  https://www.nvaccess.org/post/in-process-29th-november/ 

It's choc-full of Information about NVDA 2019.3, a wrap-up of NVDACon, the #NoMouse challenge, and an in-depth look at how to advocate for software & web accessibility! 

Enjoy :)

Kind regards

Quentin.
--
Quentin Christensen
Training and Support Manager
Re: Windows 10 App Essentials 19.11.3 #addonrelease

Joseph Lee
 

Hi,

If so, I’m afraid that this is beyond my area. Let’s try one more step:

  1. Download NVDA 2019.2.1.
  2. Do not install – rather, create a portable copy somewhere you can remember.
  3. Start the portable copy.
  4. With the portable copy started, press NVDA+F1 to open log viewer.
  5. Copy and paste the log up to and including the words “NVDA initialized”.

 

Paste the log fragment as a reply to this email so Quentin and I can figure out exactly what is up. If Windows version line says “10.0.18363”, chances are that it is specific to the installed version; if it says “6.2.9200”, chances are that it is unique to your computer. If so, I advise a non-destructive feature update reinstallation – download Media Creation Tool for 1909, create an ISO, open the resulting ISO file, run setup.exe, and tell the installer to upgrade while keeping everything.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 4:49 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I re installed nvda and did your suggestions about the add ons.  I still get version 8.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, November 28, 2019 12:20 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Ah, this explains it – somehow, NVDA was told to run in compatibility mode. Without intervention, Python 2.7 will assume it is running on Windows 8 when in fact you might be using Windows 10. Can you try the following for me:

  1. Restart with all add-ons disabled.
  2. Listen carefully to which synthesizer is now in use; if it is Espeak, then you will need to reinstall NVDA from scratch; if it is Windows OneCore, chances are that there might be an add-on other than Windows 10 App Essentials and Add-on Updater that messed up NVDA’s manifest information.

 

If OneCore comes up, restart NVDA with partial add-on functionality. To do so:

  1. Open Add-ons Manager (NVDA menu/Tools/Manage add-ons).
  2. Disable one add-on at a time and restart NVDA after disabling each one. Do not disable Resource Monitor as we need it to check Windows version.
  3. After disabling an add-on and restarting NVDA, press NVDA+Shift+Number row 6 to verify that you are using Windows 10.
  4. As soon as you find that NVDA says Windows 10, thee the just disabled add-on might be to blame.
  5. To verify step 4, enable all add-ons except the offending one and see if NVDA now reports itself as running on Windows 10.

 

If this does not help, reinstall NVDA from scratch.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 8:58 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

When I press nvda shift plus 6 it says windows 8 64 bit.  I hope this helps.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, November 28, 2019 9:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

You may need to manually type these lines into Python Console.

Another approach: if you have Resource Monitor (hopefully latest stable release), press NVDA+Shift+Number row 6 and see what NVDA says about Windows version.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 6:27 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Jacob,

 

What I did was copy and paste the lines just as Joseph typed them.

 

Jacob Kruger
+2782 413 4791
"Resistance is futile...but, acceptance is versatile..."

On 2019-11-28 10:23 AM, Gary Metzler wrote:

Hi Joseph,

 

After I enter each line I get the error win version not defined.

I hope this helps.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 7:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Hmmm, you get “False” when you’ve got 1909… Let’s try this method:

 

  1. Go back to Python Console (Control+NVDA+Z).
  2. Type the following as exactly as shown (press Enter after each line and listen carefully to what NVDA says):

 

import winVersion

winVersion.winVersion

winVersion.isWin10()

winVersion.isWin10(version=1607)

winVersion.isWin10(version=1709)

winVersion.isWin10(version=1803)

winVersion.isWin10(version=1809)

 

NVDA will first announce Windows version information (major, minor, build, platform, service pack), then for each Windows 10 release we have, “True” or “False”.

Cheers,

Joseph

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I did what you suggested and I get a false response.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 6:32 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

That’s strange. Let’s try:

  1. Open Python Console (Control+NVDA+Z).
  2. Type the following as exactly as I tell you:

 

import winVersion

winVersion.isWin10(version=1809)

 

Press Enter after each line. If it says “True”, then there should not be a reason for Windows 10 App Essentials to complain that you’ve got an older Windows release.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:26 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I got the add on manually but, when I went to install it it said I was using an older version of windows.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 6:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Actually, it is compatible with 1809 and later. I’m beginning to wonder if this affects anyone using Add-on Updater, and if this is the case, it isn’t Windows 10 App Essentials at all.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Sent: Wednesday, November 27, 2019 3:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

I think I know why – I’ll go ahead and release another version in a few moments. Sorry about that.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I’m sorry to say I am getting the error not compatible with this version of windows.  I am using windows 10 1909 and the latest nvda.  

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 2:38 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi all,

 

In a few moments Windows 10 App Essentials 19.11.3 will be made available. This release is a localization and documentation update.

 

A few important notes:

 

  • Windows 10 20H1 is now formally known as Version 2004. Although Windows 10 App Essentials does support Version 2004, formal support won’t begin until early next year.
  • A version scheduled for early next year will retire support for EdgeHTML-based Microsoft Edge from this add-on.

 

Cheers,

Joseph
Re: Windows 10 App Essentials 19.11.3 #addonrelease

Gary Metzler
 

Hi Joseph,

 

I re installed nvda and did your suggestions about the add ons.  I still get version 8.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, November 28, 2019 12:20 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Ah, this explains it – somehow, NVDA was told to run in compatibility mode. Without intervention, Python 2.7 will assume it is running on Windows 8 when in fact you might be using Windows 10. Can you try the following for me:

  1. Restart with all add-ons disabled.
  2. Listen carefully to which synthesizer is now in use; if it is Espeak, then you will need to reinstall NVDA from scratch; if it is Windows OneCore, chances are that there might be an add-on other than Windows 10 App Essentials and Add-on Updater that messed up NVDA’s manifest information.

 

If OneCore comes up, restart NVDA with partial add-on functionality. To do so:

  1. Open Add-ons Manager (NVDA menu/Tools/Manage add-ons).
  2. Disable one add-on at a time and restart NVDA after disabling each one. Do not disable Resource Monitor as we need it to check Windows version.
  3. After disabling an add-on and restarting NVDA, press NVDA+Shift+Number row 6 to verify that you are using Windows 10.
  4. As soon as you find that NVDA says Windows 10, thee the just disabled add-on might be to blame.
  5. To verify step 4, enable all add-ons except the offending one and see if NVDA now reports itself as running on Windows 10.

 

If this does not help, reinstall NVDA from scratch.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 8:58 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

When I press nvda shift plus 6 it says windows 8 64 bit.  I hope this helps.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, November 28, 2019 9:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

You may need to manually type these lines into Python Console.

Another approach: if you have Resource Monitor (hopefully latest stable release), press NVDA+Shift+Number row 6 and see what NVDA says about Windows version.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 6:27 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Jacob,

 

What I did was copy and paste the lines just as Joseph typed them.

 

Jacob Kruger
+2782 413 4791
"Resistance is futile...but, acceptance is versatile..."

On 2019-11-28 10:23 AM, Gary Metzler wrote:

Hi Joseph,

 

After I enter each line I get the error win version not defined.

I hope this helps.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 7:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Hmmm, you get “False” when you’ve got 1909… Let’s try this method:

 

  1. Go back to Python Console (Control+NVDA+Z).
  2. Type the following as exactly as shown (press Enter after each line and listen carefully to what NVDA says):

 

import winVersion

winVersion.winVersion

winVersion.isWin10()

winVersion.isWin10(version=1607)

winVersion.isWin10(version=1709)

winVersion.isWin10(version=1803)

winVersion.isWin10(version=1809)

 

NVDA will first announce Windows version information (major, minor, build, platform, service pack), then for each Windows 10 release we have, “True” or “False”.

Cheers,

Joseph

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I did what you suggested and I get a false response.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 6:32 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

That’s strange. Let’s try:

  1. Open Python Console (Control+NVDA+Z).
  2. Type the following as exactly as I tell you:

 

import winVersion

winVersion.isWin10(version=1809)

 

Press Enter after each line. If it says “True”, then there should not be a reason for Windows 10 App Essentials to complain that you’ve got an older Windows release.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:26 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I got the add on manually but, when I went to install it it said I was using an older version of windows.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 6:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Actually, it is compatible with 1809 and later. I’m beginning to wonder if this affects anyone using Add-on Updater, and if this is the case, it isn’t Windows 10 App Essentials at all.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Sent: Wednesday, November 27, 2019 3:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

I think I know why – I’ll go ahead and release another version in a few moments. Sorry about that.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I’m sorry to say I am getting the error not compatible with this version of windows.  I am using windows 10 1909 and the latest nvda.  

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 2:38 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi all,

 

In a few moments Windows 10 App Essentials 19.11.3 will be made available. This release is a localization and documentation update.

 

A few important notes:

 

  • Windows 10 20H1 is now formally known as Version 2004. Although Windows 10 App Essentials does support Version 2004, formal support won’t begin until early next year.
  • A version scheduled for early next year will retire support for EdgeHTML-based Microsoft Edge from this add-on.

 

Cheers,

Joseph
Enhanced Touch Gestures 19.11 #addonrelease

Joseph Lee
 

Hi all,

 

Enhanced Touch Gestures 19.11 is now available. Apart from localization updates, the biggest change is addition of input help mode messages for additional touch commands that come with this add-on.

 

IMPORTANT: this version is the last version to be compatible with NVDA 2019.2.1 and earlier.

Cheers,

Joseph
Re: Windows 10 App Essentials 19.11.3 #addonrelease

Joseph Lee
 

Hi,

Yes.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 3:12 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

When you say remove nvda you mean from programs and features right?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, November 28, 2019 1:26 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

All your user settings (except ones told to come up in secure screens) will be preserved. After removing NVDA, restart. Then install NVDA, then do a second restart just to make sure. Then see if NVDA now says it’s running on Windows 10. Failing that, we may need to look into compatibility settings for nvda.exe.

Technical details: Microsoft has deprecated a function called “VersionInfoEx” in Windows 8, preferring to use version information functions for each supported Windows release. In order to fully take advantage of this and to let Windows know that an application is compatible with Windows 8.1 and 10 (including server counterparts), an app must come with a manifest declaring support for Windows 8.1 and 10. Without this manifest information present, Windows will tell an app that it is running on Windows 8 even though you are using Windows 8.1 and 10.

In case of NVDA, this manifest is required because of Python. Python 2.7 (NVDA 2019.2.1 and earlier) will assume it is running on Windows 8 (because Windows said so) because it does not include compatibility manifest information for later Windows releases by default (I added compatibility information for Windows 10 back in 2014). This does not affect Python 3 (NVDA 2019.3 or later) because Python 3 does include compatibility manifest for Windows 8.1 and 10.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 10:01 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I did as you suggested but, I still get version 8.  What can I do to preserve all my settings and addons after I wipe out nvda?  Thanks for all your help.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, November 28, 2019 12:20 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Ah, this explains it – somehow, NVDA was told to run in compatibility mode. Without intervention, Python 2.7 will assume it is running on Windows 8 when in fact you might be using Windows 10. Can you try the following for me:

  1. Restart with all add-ons disabled.
  2. Listen carefully to which synthesizer is now in use; if it is Espeak, then you will need to reinstall NVDA from scratch; if it is Windows OneCore, chances are that there might be an add-on other than Windows 10 App Essentials and Add-on Updater that messed up NVDA’s manifest information.

 

If OneCore comes up, restart NVDA with partial add-on functionality. To do so:

  1. Open Add-ons Manager (NVDA menu/Tools/Manage add-ons).
  2. Disable one add-on at a time and restart NVDA after disabling each one. Do not disable Resource Monitor as we need it to check Windows version.
  3. After disabling an add-on and restarting NVDA, press NVDA+Shift+Number row 6 to verify that you are using Windows 10.
  4. As soon as you find that NVDA says Windows 10, thee the just disabled add-on might be to blame.
  5. To verify step 4, enable all add-ons except the offending one and see if NVDA now reports itself as running on Windows 10.

 

If this does not help, reinstall NVDA from scratch.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 8:58 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

When I press nvda shift plus 6 it says windows 8 64 bit.  I hope this helps.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, November 28, 2019 9:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

You may need to manually type these lines into Python Console.

Another approach: if you have Resource Monitor (hopefully latest stable release), press NVDA+Shift+Number row 6 and see what NVDA says about Windows version.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 6:27 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Jacob,

 

What I did was copy and paste the lines just as Joseph typed them.

 

Jacob Kruger
+2782 413 4791
"Resistance is futile...but, acceptance is versatile..."

On 2019-11-28 10:23 AM, Gary Metzler wrote:

Hi Joseph,

 

After I enter each line I get the error win version not defined.

I hope this helps.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 7:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Hmmm, you get “False” when you’ve got 1909… Let’s try this method:

 

  1. Go back to Python Console (Control+NVDA+Z).
  2. Type the following as exactly as shown (press Enter after each line and listen carefully to what NVDA says):

 

import winVersion

winVersion.winVersion

winVersion.isWin10()

winVersion.isWin10(version=1607)

winVersion.isWin10(version=1709)

winVersion.isWin10(version=1803)

winVersion.isWin10(version=1809)

 

NVDA will first announce Windows version information (major, minor, build, platform, service pack), then for each Windows 10 release we have, “True” or “False”.

Cheers,

Joseph

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I did what you suggested and I get a false response.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 6:32 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

That’s strange. Let’s try:

  1. Open Python Console (Control+NVDA+Z).
  2. Type the following as exactly as I tell you:

 

import winVersion

winVersion.isWin10(version=1809)

 

Press Enter after each line. If it says “True”, then there should not be a reason for Windows 10 App Essentials to complain that you’ve got an older Windows release.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:26 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I got the add on manually but, when I went to install it it said I was using an older version of windows.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 6:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Actually, it is compatible with 1809 and later. I’m beginning to wonder if this affects anyone using Add-on Updater, and if this is the case, it isn’t Windows 10 App Essentials at all.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Sent: Wednesday, November 27, 2019 3:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

I think I know why – I’ll go ahead and release another version in a few moments. Sorry about that.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I’m sorry to say I am getting the error not compatible with this version of windows.  I am using windows 10 1909 and the latest nvda.  

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 2:38 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi all,

 

In a few moments Windows 10 App Essentials 19.11.3 will be made available. This release is a localization and documentation update.

 

A few important notes:

 

  • Windows 10 20H1 is now formally known as Version 2004. Although Windows 10 App Essentials does support Version 2004, formal support won’t begin until early next year.
  • A version scheduled for early next year will retire support for EdgeHTML-based Microsoft Edge from this add-on.

 

Cheers,

Joseph
Re: Windows 10 App Essentials 19.11.3 #addonrelease

Gary Metzler
 

Hi Joseph,

 

When you say remove nvda you mean from programs and features right?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, November 28, 2019 1:26 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

All your user settings (except ones told to come up in secure screens) will be preserved. After removing NVDA, restart. Then install NVDA, then do a second restart just to make sure. Then see if NVDA now says it’s running on Windows 10. Failing that, we may need to look into compatibility settings for nvda.exe.

Technical details: Microsoft has deprecated a function called “VersionInfoEx” in Windows 8, preferring to use version information functions for each supported Windows release. In order to fully take advantage of this and to let Windows know that an application is compatible with Windows 8.1 and 10 (including server counterparts), an app must come with a manifest declaring support for Windows 8.1 and 10. Without this manifest information present, Windows will tell an app that it is running on Windows 8 even though you are using Windows 8.1 and 10.

In case of NVDA, this manifest is required because of Python. Python 2.7 (NVDA 2019.2.1 and earlier) will assume it is running on Windows 8 (because Windows said so) because it does not include compatibility manifest information for later Windows releases by default (I added compatibility information for Windows 10 back in 2014). This does not affect Python 3 (NVDA 2019.3 or later) because Python 3 does include compatibility manifest for Windows 8.1 and 10.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 10:01 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I did as you suggested but, I still get version 8.  What can I do to preserve all my settings and addons after I wipe out nvda?  Thanks for all your help.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, November 28, 2019 12:20 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Ah, this explains it – somehow, NVDA was told to run in compatibility mode. Without intervention, Python 2.7 will assume it is running on Windows 8 when in fact you might be using Windows 10. Can you try the following for me:

  1. Restart with all add-ons disabled.
  2. Listen carefully to which synthesizer is now in use; if it is Espeak, then you will need to reinstall NVDA from scratch; if it is Windows OneCore, chances are that there might be an add-on other than Windows 10 App Essentials and Add-on Updater that messed up NVDA’s manifest information.

 

If OneCore comes up, restart NVDA with partial add-on functionality. To do so:

  1. Open Add-ons Manager (NVDA menu/Tools/Manage add-ons).
  2. Disable one add-on at a time and restart NVDA after disabling each one. Do not disable Resource Monitor as we need it to check Windows version.
  3. After disabling an add-on and restarting NVDA, press NVDA+Shift+Number row 6 to verify that you are using Windows 10.
  4. As soon as you find that NVDA says Windows 10, thee the just disabled add-on might be to blame.
  5. To verify step 4, enable all add-ons except the offending one and see if NVDA now reports itself as running on Windows 10.

 

If this does not help, reinstall NVDA from scratch.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 8:58 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

When I press nvda shift plus 6 it says windows 8 64 bit.  I hope this helps.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, November 28, 2019 9:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

You may need to manually type these lines into Python Console.

Another approach: if you have Resource Monitor (hopefully latest stable release), press NVDA+Shift+Number row 6 and see what NVDA says about Windows version.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 6:27 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Jacob,

 

What I did was copy and paste the lines just as Joseph typed them.

 

Jacob Kruger
+2782 413 4791
"Resistance is futile...but, acceptance is versatile..."

On 2019-11-28 10:23 AM, Gary Metzler wrote:

Hi Joseph,

 

After I enter each line I get the error win version not defined.

I hope this helps.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 7:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Hmmm, you get “False” when you’ve got 1909… Let’s try this method:

 

  1. Go back to Python Console (Control+NVDA+Z).
  2. Type the following as exactly as shown (press Enter after each line and listen carefully to what NVDA says):

 

import winVersion

winVersion.winVersion

winVersion.isWin10()

winVersion.isWin10(version=1607)

winVersion.isWin10(version=1709)

winVersion.isWin10(version=1803)

winVersion.isWin10(version=1809)

 

NVDA will first announce Windows version information (major, minor, build, platform, service pack), then for each Windows 10 release we have, “True” or “False”.

Cheers,

Joseph

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I did what you suggested and I get a false response.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 6:32 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

That’s strange. Let’s try:

  1. Open Python Console (Control+NVDA+Z).
  2. Type the following as exactly as I tell you:

 

import winVersion

winVersion.isWin10(version=1809)

 

Press Enter after each line. If it says “True”, then there should not be a reason for Windows 10 App Essentials to complain that you’ve got an older Windows release.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:26 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I got the add on manually but, when I went to install it it said I was using an older version of windows.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 6:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Actually, it is compatible with 1809 and later. I’m beginning to wonder if this affects anyone using Add-on Updater, and if this is the case, it isn’t Windows 10 App Essentials at all.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Sent: Wednesday, November 27, 2019 3:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

I think I know why – I’ll go ahead and release another version in a few moments. Sorry about that.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I’m sorry to say I am getting the error not compatible with this version of windows.  I am using windows 10 1909 and the latest nvda.  

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 2:38 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi all,

 

In a few moments Windows 10 App Essentials 19.11.3 will be made available. This release is a localization and documentation update.

 

A few important notes:

 

  • Windows 10 20H1 is now formally known as Version 2004. Although Windows 10 App Essentials does support Version 2004, formal support won’t begin until early next year.
  • A version scheduled for early next year will retire support for EdgeHTML-based Microsoft Edge from this add-on.

 

Cheers,

Joseph
Re: Virtual review and cmd / power shell

George McCoy
 

FWIW, I can bring it up on two HP computers running windows 10 professional. One is a desktop, the other is a laptop.


George

On 11/27/2019 10:02 PM, Mr. Wong Chi Wai, William wrote:

The problem here is, I can normally bring up the virtual review window under win 7 cmd.

But not under win 10.

This is why I want to bring that into attention, and see if this is a bug or not.

Joseph Lee 於 27/11/2019 23:13 寫道:

Hi,

Technically, it does not replace screen review, especially if modern apps are involved. This add-on will do what JAWS’s “virtualize current window” command does: presents screen content (almost the entire screen content) as a virtual viewer so one can review text. In modern apps such as ones found in Windows 8 and later, this add-on will gather content text by traversing through all screen elements (or almost all elements) and collect labels and present it on screen.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, November 27, 2019 7:07 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Virtual review and cmd / power shell

 

I don't know enough about virtual review to comment on that.  It sounded to me from the description and from the name that it duplicates screen review but are you saying that isn't the case?  I was saying that it evidently allows you to search the screen which is a feature no NVDA review mode has and thus, it shouldn't be described as just a convenience.  But it would be good to clarify if it duplicates screen review but with different commands or does something else.

 

Gene

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

From: Joseph Lee

Sent: Wednesday, November 27, 2019 8:55 AM

Subject: Re: [nvda] Virtual review and cmd / power shell

 

Hi,

Maybe we need to update the description to say that it is useful in modern apps where screen review isn’t working.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, November 27, 2019 2:56 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Virtual review and cmd / power shell

 

I just read the description of the add-on.  The sentence near the beginning that says that it is just for convenience and doesn't replace the NVDA review methods appears to be inaccurate.  Assuming that this is equivalent to screen mode in NVDA, it has an important ability that screen mode has never had, nor object navigation.  You can't search for content in either of those modes.  You have to look at the screen or move through the screen line by line to get to something. 

 

Gene

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

Sent: Wednesday, November 27, 2019 3:17 AM

Subject: Re: [nvda] Virtual review and cmd / power shell

 

You need to install the virtual review addon as this is not a built-in
NVDA function. You can get it at
https://addons.nvda-project.org/addons/virtualRevision.en.html.

On 27/11/2019 19:36, Mr. Wong Chi Wai, William wrote:
> Hi all,
> Under Win 10,
>
> After running cmd or power shell,
>
> If I press nvda ctrl and w,
>
> it didn't show the virtual review window,
>
>
> Could anyone advice me how to fix this?
>
>
> Thanks,
>
> William
>
>
>
>
13861 - 13880 of 81093  
More
Home Messages Hashtags Subgroups About Features Pricing Updates Terms Help Twitter