Date   

Re: "input gesture dialog" bug

bering.p
 

Thanks Cyril.
I took the time because I had it, but I won't do it every day.
Others will have done it much faster than me.
For information, I have worked around this problem in my add-on.
If necessary, I will explain it when answering the ticket.
Best regards.

Paul.
Le 29/06/2022 21:55, Cyrille via groups.io a écrit :

Paul, I have seen that you have opened the ticket.
Thanks and congratulations!
For reference, here is the link: #13854.

Cyrille

On Wed, Jun 29, 2022 at 08:44 AM, Cyrille wrote:
Hi all

@Paul,
Why don't you open the ticket yourself? You have all the skills to do it. The technical description that you made of this issue is more than correct with a detailed way to reproduce the issue. And your English, as written in your messages, is also correct.
If something else is blocking you, just let us know and we can help, here or in GitHub once the ticket is opened.

@Gene:
A common consequence of an error occurring in the GUI is that the GUI may not work as expected in the future. For example if you add the following steps to Paul's steps:
- close the input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window

You will end up with many input gesture window opened, whereas the standard behaviour of NVDA is to re-focus the input gesture window if it is already opened in the background.

Cheers,

Cyrille




On Wed, Jun 29, 2022 at 04:08 AM, bering.p wrote:
Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.

-- 

Paul.


Re: "input gesture dialog" bug

Cyrille
 

Paul, I have seen that you have opened the ticket.
Thanks and congratulations!
For reference, here is the link: #13854.

Cyrille


On Wed, Jun 29, 2022 at 08:44 AM, Cyrille wrote:
Hi all

@Paul,
Why don't you open the ticket yourself? You have all the skills to do it. The technical description that you made of this issue is more than correct with a detailed way to reproduce the issue. And your English, as written in your messages, is also correct.
If something else is blocking you, just let us know and we can help, here or in GitHub once the ticket is opened.

@Gene:
A common consequence of an error occurring in the GUI is that the GUI may not work as expected in the future. For example if you add the following steps to Paul's steps:
- close the input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window

You will end up with many input gesture window opened, whereas the standard behaviour of NVDA is to re-focus the input gesture window if it is already opened in the background.

Cheers,

Cyrille




On Wed, Jun 29, 2022 at 04:08 AM, bering.p wrote:
Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.

-- 

Paul.


Re: [Solved] Pacmate 40 display problem

Timothy VD Berg
 

Good news

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Andre Vosloo via groups.io
Sent: Wednesday, 29 June 2022 18:48
To: nvda@groups.io
Subject: [nvda] pacmate 40 display problemsd

 

Hi all

 

I sorted the problem out.  Uninstalled device and deleted driver.  When I rebooted and plugged the display in NVDA recognized it immediately and it is more responsive now than before.

 

regards


Re: "input gesture dialog" bug

 

On Wed, Jun 29, 2022 at 09:16 AM, bering.p wrote:
When an error is traced in the log, how do you as a user know that it does not impact NVDA?
-
Do you notice any difference whatsoever in NVDA (or insert appropriate program here for others) behavior?   If no, that's enough.

I'd love for those getting exercised about this to one day open up virtually any Windows error log you can think of.  There are literally hundreds of errors per day, sometimes per hour, where the world goes merrily along.

If the error is neither fatal, nor deleterious to the user experience, then it's a big meh.  Normal errors do exist.  And we know this in NVDA because every time those inexperienced with the betas start using one there are almost invariably reports here stating, "I'm hearing the error sound repeatedly."  Those are almost equally invariably "normal errors" that would never be reported to the end user in the production software, even if that very beta is what becomes the production software.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill


[Solved] Pacmate 40 display problem

Andre Vosloo
 

Hi all

 

I sorted the problem out.  Uninstalled device and deleted driver.  When I rebooted and plugged the display in NVDA recognized it immediately and it is more responsive now than before.

 

regards


Re: "input gesture dialog" bug

Gene
 

That's interesting.  I wasn't sure if it was causing any problems.  When I tried to reproduce it, I couldn't either because I did something incorrectly or for some other reason but others have reproduced it.

Gene

On 6/29/2022 10:44 AM, Cyrille via groups.io wrote:

Hi all

@Paul,
Why don't you open the ticket yourself? You have all the skills to do it. The technical description that you made of this issue is more than correct with a detailed way to reproduce the issue. And your English, as written in your messages, is also correct.
If something else is blocking you, just let us know and we can help, here or in GitHub once the ticket is opened.

@Gene:
A common consequence of an error occurring in the GUI is that the GUI may not work as expected in the future. For example if you add the following steps to Paul's steps:
- close the input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window

You will end up with many input gesture window opened, whereas the standard behaviour of NVDA is to re-focus the input gesture window if it is already opened in the background.

Cheers,

Cyrille




On Wed, Jun 29, 2022 at 04:08 AM, bering.p wrote:
Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.

-- 

Paul.


Re: "input gesture dialog" bug

Cyrille
 

Hi all

@Paul,
Why don't you open the ticket yourself? You have all the skills to do it. The technical description that you made of this issue is more than correct with a detailed way to reproduce the issue. And your English, as written in your messages, is also correct.
If something else is blocking you, just let us know and we can help, here or in GitHub once the ticket is opened.

@Gene:
A common consequence of an error occurring in the GUI is that the GUI may not work as expected in the future. For example if you add the following steps to Paul's steps:
- close the input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window

You will end up with many input gesture window opened, whereas the standard behaviour of NVDA is to re-focus the input gesture window if it is already opened in the background.

Cheers,

Cyrille




On Wed, Jun 29, 2022 at 04:08 AM, bering.p wrote:
Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.

-- 

Paul.


Re: "input gesture dialog" bug

 
Edited

Hi all,

As Luke pointed out, this is caused by input gestures dialog trying to show more categories than category results count it has found. You can reproduce this bug across languages (which explains results Paul and Rui were reporting) as follows:

  1. Open input gestures dialog.
  2. Do not select any category (NVDA should select the first category, so leave it at that).
  3. Press Shift+Tab to move to "filter by" edit field and type a letter.
  4. Press Tab to move to gestures/categories tree view and record how many categories are showing.
  5. Move back to filter by edit field and clear it (delete whatever letter you wrote).
  6. Move to the tree view and select a category that is positioned one below the number of categories from steps 3 and 4.
  7. Move to filter by edit field and enter the letter from step 3.

Expected: no errors.

Actual: error with IndexError traceback is recorded in the log. You won't hear the error tone if you are using stable version of NVDA.

Cause: see Luke's remark.

Technical (internals): a gestures view model is used by NVDA to show you categories, input help messages, and associated commands. During normal business hours (when no errors occur), you would select the first category, search for gestures, and NVDA will not play error tones. This is because the list of results is greater than 1 unless you type a string of letters and symbols which results in the tree view becoming empty. The IndexError comes not from input gestures dialog per say, but from the gestures view model as the categories count exceeded the position of the tree view you were focused on (NVDA uses GetSelection function from various wxWidgets controls a lot to determine where you are and take appropriate actions as this function returns the position index (0-based)).

For folks wishing to submit a GitHub issue, search for existing issues on input gestures dialog before writing a new issue.

Cheers, Joseph


Re: "input gesture dialog" bug

bering.p
 

Sorry, but I use NVDA in french language.
For english language, it's the "tools" category.
I don't think it's up to the user to decide whether this error is important or not.
If developers are logging errors, maybe it matters and probably want to know when they happen.
Otherwise, they log warnings.
I think it is up to them whether the errors that have been reported to them should be corrected or not.
Best regards.
Paul.
Le 29/06/2022 14:26, Gene a écrit :

I don't know why you see the mouse category where you describe it.  I have to up arrow something like seven or eight times.  Once I get there, if I shift tab once to the filter field and type z, then tab once to the list of filtered results, the results are filtered properly.  There are many times when errors occur in NVDA that don't have any effect on the operation of the screen-reader and in such cases, errors are generally not corrected. 

Gene

On 6/29/2022 6:08 AM, bering.p wrote:
Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.
-- 

Paul.



Re: "input gesture dialog" bug

bering.p
 

Hi.
When an error is traced in the log, how do you as a user know that it does not impact NVDA?
How can we verify that the result of the filter is correct when there is this error?
It seems to me that an error that does not impact NVDA, is reported as a warning.
Best regards.
Paul.
Le 29/06/2022 13:53, Gene a écrit :

But do the errors effect NVDA?  It sounds as though the point is to provide a command to take an action.  Is the action taken?  I have no objection to reporting the error, but if it doesn't affect performance in any way, correcting it may not be a good use of resources and time.

Gene

On 6/29/2022 6:08 AM, bering.p wrote:
Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.
-- 

Paul.



Re: "input gesture dialog" bug

Luke Davis
 

Gene wrote:

There are many times when errors
occur in NVDA that don't have any effect on the operation of the screen-reader and in such cases, errors are generally not corrected. 
Warnings, yes. Errors, not so much.

But this one is an index off by one error. Someone coded it so that it looks up index 4 in a 4 item list that starts at 0. In other words, it has items zero through three, and the code wants the fourth one. It should ask for three, since it counts from zero, but instead it's asking for 4, which doesn't exist.

This is a moderate problem, because as Rui pointed out, the dialog isn't being properly terminated because of the error.

Luke


Re: "input gesture dialog" bug

Gene
 

I suspect this error has been around for a long time.  Does the error only occur when you type an individual letter?  It may be a bug that doesn't matter.  I generally would expect people to filter by a word or group of words and not by  a letter.  . 

Gene

On 6/29/2022 7:30 AM, Rui Fontes wrote:

Hello!


A curious error...

It only happens at certain categories and with certain letters...

By instance, in the Mouse category, if I search by "a" don't gave errors... If I search by "b" it gaves the error...


And the error is index out of range...


The error when you open again the Input gestures dialog is because the previous instance was not destroyed because of the error...


Rui Fontes



Às 12:08 de 29/06/2022, bering.p escreveu:
Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.
-- 

Paul.


Re: "input gesture dialog" bug

Rui Fontes
 

Hello Gene!


Às 13:26 de 29/06/2022, Gene escreveu:
I don't know why you see the mouse category where you describe it.  I have to up arrow something like seven or eight times.  Once I get there, if I shift tab once to the filter field and type z, then tab once to the list of filtered results, the results are filtered properly.

As I said in previous message, it happens in various sections, not only mouse...

But do not happen with all letters...



Gene wrote:

There are many times when errors occur in NVDA that don't have any effect on the operation of the screen-reader and in such cases, errors are generally not corrected.

Sorry, but for me, all errors should be corrected... Of course priority should go to errors that affect the operations...

But all errors should be corrected!


Rui Fontes


Re: "input gesture dialog" bug

Rui Fontes
 

Hello!


A curious error...

It only happens at certain categories and with certain letters...

By instance, in the Mouse category, if I search by "a" don't gave errors... If I search by "b" it gaves the error...


And the error is index out of range...


The error when you open again the Input gestures dialog is because the previous instance was not destroyed because of the error...


Rui Fontes



Às 12:08 de 29/06/2022, bering.p escreveu:

Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.
-- 

Paul.


Re: "input gesture dialog" bug

Gene
 

I don't know why you see the mouse category where you describe it.  I have to up arrow something like seven or eight times.  Once I get there, if I shift tab once to the filter field and type z, then tab once to the list of filtered results, the results are filtered properly.  There are many times when errors occur in NVDA that don't have any effect on the operation of the screen-reader and in such cases, errors are generally not corrected. 

Gene

On 6/29/2022 6:08 AM, bering.p wrote:

Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.
-- 

Paul.


Re: "input gesture dialog" bug

Gene
 

But do the errors effect NVDA?  It sounds as though the point is to provide a command to take an action.  Is the action taken?  I have no objection to reporting the error, but if it doesn't affect performance in any way, correcting it may not be a good use of resources and time.

Gene

On 6/29/2022 6:08 AM, bering.p wrote:

Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.
-- 

Paul.


"input gesture dialog" bug

bering.p
 

Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.

-- 

Paul.


Re: reducing the frequency of progress updates

 

Hi,

Actually, it is not NVDA that holds progress bar values - it says things according to what Firefox (or any app) tells it to say, more so if this is a live region (for live regions, provided that the application developer or website author is informing screen readers that live text should be announced).

Cheers,

Joseph


Re: reducing the frequency of progress updates

Brian's Mail list account
 

This same issue exists in command prompt of course, where the process finishes almost instantly but the reading goes on for an age.
I've not found any way to control either problem.
I have one web page where there are progress bars for file and total upload so the bleeping can sound most odd as can the reading. I've yet to find a way to say only read this progress bar, but not this one etc, I guess in the command prompt you can output to a text file, but not every dos based program will respect that choice either!
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Bob Cavanaugh" <cavbob1993@...>
To: <nvda@nvda.groups.io>
Sent: Monday, June 27, 2022 11:38 PM
Subject: [nvda] reducing the frequency of progress updates


Hi all,
I have changed my NVDA progress indicator from beep to speak, but am
wondering if there is a way to refine the way progress is announced.
Is there some way I can only have as many indicators announced as NVDA
can read without getting behind? For example, I just sent a file to
someone using We Transfer. As the file was uploading, NVDA would say
1% transferring, 2% transferring, 3% transferring, and on and on. If I
hit the control key at that point, it would continue to speak, but say
8% transferring, 9% transferring, etc. Is there a way for NVDA to only
give as many progress indicator outputs as it can comfortably speak?
Thanks,
Bob




Re: IMPORTANT Notice on Joseph Lee's add-ons: reducing/ending support for Windows 7, 8, 8.1 and unsupported Windows 10 feature updates effective january 2023

Brian's Mail list account
 

Thanks for the clarification. I do feel that the worries over security are over the top, but at the moment everyone seems to be taking this line of trying to stop people downloading stuff at their own risk.
I would point out that a straw poll of home users, not scientific at all, I have to say, suggests to me that many, probably about half or slightly less of them are using Windows 7 on at least one machine.

Of course there is nothing stopping them getting windows 10, but many tell me in these cash strapped days that buying new hardware merely to run Windows 11 cannot be justified, so down the line we could be seeing a similar problem with people using 10 who have no plans to go 11.
Of course even if support for 7 ends, there is really nothing to stop people still using the NVDA add ons that work and older copies of those which don't.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Monday, June 27, 2022 10:04 PM
Subject: [nvda] IMPORTANT Notice on Joseph Lee's add-ons: reducing/ending support for Windows 7, 8, 8.1 and unsupported Windows 10 feature updates effective january 2023


Hello NVDA community,

Before I get into the heart of this announcement, I'm delighted to announce
that all my add-ons are compatible with NVDA 2022.2 changes. And yes, I'm
back - thank you everyone for your valuable feedback, comments, and
criticisms - I still have some residue from NVDA 2022.1 and add-ons work but
feeling a bit better after taking a break for a while.

The following notice is applicable to anyone using my add-ons (Ad-on
Updater, Windows App Essentials, future add-ons and/or add-ons awaiting new
maintainers), specifically for anyone using Windows 7, 8, 8.1, and their
server counterparts. Please do NOT take this as a statement on NVDA and
support for Windows releases (for that one, see a message from Quentin from
NV Access posted earlier this year):

Earlier this year I (Joseph Lee) announced that my add-ons will eventually
end support for Windows 7, 8, and 8.1, noting that I will provide a 60-day
notice before then. I then sent a notice in March 2022, stating that
add-ons, including ones leaving my maintenance (which there were five then)
will end support for Windows 7 and 8.x effective May 2022; I also noted that
there will be an exception, namely Add-on Updater which will support old
Windows releases as long as NVDA supports them. On paper, end of support
date was May 7, 2022 but due to various community events (namely preparing
for NVDA 2022.1), I forgot to announce that fact.

My original plan was and still is to see if anyone from the NVDA community
can take care of now unmaintained add-ons from me (Enhanced Touch Gestures,
Event Tracker, GoldWave, Resource Monitor, Sound Splitter, StationPlaylist)
with a possibility that new maintainers will release a version of these
add-ons requiring Windows 10 or later eventually (source code is ready).
However, since I haven't received messages about new maintainers (as of time
of this announcement), I am revising the plan as follows:

Effective January 2023, all of my add-ons with limited exceptions will no
longer support unsupported or soon to be unsupported Windows releases,
including Windows 7/Server 2008 R2, Windows 8/Server 2012, Windows
8.1/Server 2012 R2, and unsupported feature updates for Windows 10 and later
from the standpoint of consumers and businesses. For Windows 10, unsupported
feature updates are 1507 (build 10240), 1511 (build 10586/November Update),
1607 (build 14393/Anniversary Update), 1703 (build 15063/Creators Update),
1709 (build 16299/Fall Creators Update), 1803 (build 17134/April 2018
Update), 1809 (build 17763/October 2018 Update), 1903 (build 18362/May 2019
Update), 1909 (build 18363/November 2019 Update), 2004 (build 19041/May 2020
Update), and from December 2022 onwards, 21H1 (build 19043/May 2021 Update);
although consumer support for 20H2 (build 19042/October 2020 Update) ended
in May 2022, business support ends in May 2023, thus it is still a supported
Windows 10 feature update. The list of supported and unsupported Windows
releases can change based on Windows product lifecycle schedule. This policy
applies to current and future add-ons, and if circumstances warrant it, any
add-ons I have maintained in the past that are not being maintained by the
community as of January 2023 (see notes).

Notes:

1. The only exception will be Add-on Updater which will have reduced
functionality on unsupported Windows releases so that it can provide a
"nightlight" (minimal service for emergency and special uses) and to keep my
promise of supporting old Windows releases as long as NVDA itself supports
them. That is, even though updates for Ad-on Updater will be compatible with
unsupported releases, new features will be exclusive to supported Windows
releases; for users of older Windows releases, consider this a "feature
freeze" notice. As for what constitutes nightlight functionality, I expect
that you will be able to at least check for, download, and install add-on
updates and tell Add-on Updater to not check for some add-on updates;
details will be communicated soon. One thing is certain: unless things
change, Add-on Updater will continue to work on unsupported Windows releases
but remember that you will be on your own due to security risks associated
with downloading data from the Internet; PROCEED WITH CAUTION!
2. Windows App Essentials supports Windows 10 and 11 feature updates
that are actively supported for consumers (as of time of this writing,
Windows 10 Version 21H1, 21H2 (build 19044/November 2021 Update), Windows
Server 2022 (build 20348), Windows 11 Version 21H2 (build 22000)), with the
add-on ending support for a given feature update prior to end of consumer
support from Microsoft (for example, Windows App Essentials will end support
for Windows 10 Version 21H1 by September 2022, three months prior to
Microsoft ending support for it (December), and support for Windows 10
Version 21H2 from the add-on is scheduled to end in early 2023 prior to end
of consumer-level support in June 2023).
3. The following add-ons are no longer (actively) maintained by me as
of time of this post: Enhanced Touch Gestures, Event Tracker, GoldWave,
Resource Monitor, Sound Splitter, StationPlaylist. If no-one volunteers to
maintain them by January 2023, the unsupported Windows release policy will
apply to them as well - that is, a version of these add-ons will be released
that will not install on unsupported Windows releases.



Frequently asked questions:



Q. Does this mean NVDA itself will end support for unsupported Windows
releases?

No. NV Access noted that NVDA will support Windows 7, 8, 8.1 and other old
releases.



Q. What about add-ons such as Control Usage Assistant?

Add-ons such as Control Usage Assistant (formerly maintained by me) have new
maintainers, therefore this policy notice does not apply to them.



Q. Can I modify future add-on releases for use on unsupported Windows
releases?

Yes and no. Yes you can view and modify add-ons so they can work on
unsupported releases. At the same time, for some add-ons, supporting legacy
Windows releases will require extensive edits to the add-on source code as
legacy Windows code were removed for some add-ons in March 2022.



Q. Why is using Add-on Updater on unsupported Windows releases a potential
security risk?

At its core, Add-on Updater downloads data from the Internet. Therefore, it
might be possible that add-on hosting repositories can be compromised,
leading to distribution of malicious add-ons. The add-ons community takes
add-on security seriously, particularly when it comes to distribution
channels.



Q. Does this mean future add-ons from Joseph will not support old Windows
releases?

Yes. While the policy takes full effect in January 2023, you can assume that
new add-ons I (Joseph Lee) may publish in 2022 will require Windows 10
Version 21H1 or later.



Q. Do you have plans to release updates for unmaintained add-ons prior to
the policy taking effect in January 2023?

For Enhanced Touch Gestures, Event Tracker, GoldWave, Resource Monitor,
Sound Splitter, and StationPlaylist, I have no plans to release updates in
2022; rather, releasing updates is close to impossible as these add-ons no
longer support old Windows releases at the source code level.



Q. Wait, the just announced policy sounds similar to the feature update
support policy for Windows App Essentials add-on.

In some ways, yes. The difference is that Windows App Essentials support
Windows 10 and later whereas other add-ons support old Windows releases such
as Windows 7.



Q. Why January 2023?

This is when support for Windows 7 and 8.1 will end for most users (extended
security updates for Windows 7, extended support for Windows 8.1; Windows 8
is end of life as of January 2016).



Q. Does this policy apply to Windows Server releases?

Yes. While some Windows 10 releases have a server counterpart, they (2016,
2019, 2022) are still supported by Microsoft.



Q. What if I'm using Windows 10 Enterprise long-term servicing
branch/channel (LTSB/LTSC) releases?

Since this edition is meant for mission-critical devices, I and my add-ons
do not support this scenario. Windows App Essentials add-on itself does not
support this configuration either.



The key takeaway is this: if you can, please upgrade to supported Windows
releases as soon as possible. Feel free to contact me if you have additional
questions or comments.

Cheers,

Joseph

4201 - 4220 of 101014