Date   

Re: Shortcut commands stopping working in NVDA

Sarah k Alawami
 

It’s not sticking keys. It happens on my keyboard as well, and on my laptop keys as well. I already submitted a lot of logs on a github page, I think in regard to this. Narrator will even stick as well. The only way is to reboot, or do the left shift right shift, control, etc.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Wednesday, July 21, 2021 4:41 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Shortcut commands stopping working in NVDA

 

On Wed, Jul 21, 2021 at 07:36 PM, Sarah k Alawami wrote:

This is not anything new, now we need to figure out why this happens.

-
I say the following not to be snarky, but if it is actually sticking keys, we already know why this happens.

Another good thing, and dirt cheap, is to obtain a USB keyboard (and thrift stores are loaded with them, fully functional) to keep "as the testing spare" and check if the issue persists, when it occurs, on a different keyboard that's available for the machine.

If the shortcuts work immediately when you use the alternative keyboard, and consistently, you know you have a hardware issue of some sort with your primary keyboard.  While these are, relatively speaking, rare they are far from never happening.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Re: Shortcut commands stopping working in NVDA

Tyler Spivey
 

Fortunately for this one, a recent PR got merged into master which might fix it.

https://github.com/nvaccess/nvda/pull/12610

On 7/21/2021 5:04 PM, Brian Vogel wrote:
Gene,
Thanks for the clarification.
There is the Windows Feature called sticky keys, and there are sticking keyboard keys, and there are unintentional software-generated sticky keys, too.  It's now clear that the last of the three is what's under discussion, and this was not initially clear to me.  And it's a different kettle of fish, as the saying goes.
--
Brian -Windows 10, 64-Bit, Version 21H1, Build 19043
Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.
That's what life is about.  And in that order.
        ~ Liza Minnelli


Re: Shortcut commands stopping working in NVDA

 

Hi,

It appears one of the NVDA add-on authors may have found a solution to the "stuck key" problem:

Specifically, according to the pull request (the second link), when NVDA watchdog finds itself stuck, it will attempt to recover itself, and in the midst of it, keyboard modifier state is not checked, leading to stuck keys. This should be resolved now in latest alpha development snapshot, and the fix for this proboem may or may not become part of NVDA 2021.2.

Cheers,

Joseph


Re: Shortcut commands stopping working in NVDA

Jackie
 

So I just experimented w/it, as I found myself precisely in this
position this very moment. Shift & control keys didn't work, but
capslock, which I use as an NVDA modifier, did. So I'm wondering if
somehow the NVDA modifier key isn't being released properly at
times,ie, buffers aren't being flushed when required, etc.

On 7/21/21, Gene <gsasner@gmail.com> wrote:
I should add that I remember at least one person describing the problem in a
way that caused me to think it might be sticky keys and that’s why I started
experimenting.; I don’t want to take credit for an idea I saw from one or
more other people. I brought it up again because I didn’t think it got the
attention it should and because the limited about of experimenting I’ve
done, I have to wait until the problem occurs, has so far confirmed that
sticky keys are the problem.

Gene
-----Original Message-----

From: Gene
Sent: Wednesday, July 21, 2021 7:02 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Shortcut commands stopping working in NVDA

I remember a bit of discussion of what you are describing before but I don’t
think it was sustained enough to catch the attention of the developers on
the list. I didn’t remember who, for the most part, had brought it up. I
suppose it should be filed as a ticket.

My impression from before is that the problem would be mentioned and one or
two messages would result and it would then not be mentioned again for a
good while. While I think this is a general problem, it may be that not
enough people complained of it that it was recognized as such. I think that
almost no one spoke of it as a sticky key problem before, which may have
made the problem not properly replicable by developers.

Gene
-----Original Message-----
From: Sarah k Alawami
Sent: Wednesday, July 21, 2021 6:36 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Shortcut commands stopping working in NVDA

Yeah, I already said that a few months ago. I in fact go control left right,
alt left right, windows, windows, shift left, right, tab when I know a key
is stuck. This is not anything new, now we need to figure out why this
happens.



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, July 21, 2021 3:54 PM
To: nvda@nvda.groups.io
Subject: [nvda] Shortcut commands stopping working in NVDA



Occasionally, a problem where NVDA shortcut commands such as read title bar,
open menus, etc. stop working has been discussed here. I may have found out
what is actually going on and it may either eliminate or almost fully
eliminate the need to unload, then run NVDA again.



It appears to me that a key is getting stuck. When this happens, try
pressing the left shift key, then the right shift key quickly perhaps five
or six times each. Then see if the commands work again.



Caution: It used to be and probably still is the default that if you press
either shift something like five times, it will turn on something. I don’t
recall if it is some sort of sounds Windows will make when certain keys are
pressed or sticky keys. At any rate, if you haven’t turned off this
behavior, don’t press the shift five times. Try three or four.



I’ve just been trying this recently. I don’t have this happen enough to see
if the same key, for example, one of the shift keys, or another key, such as
either control, either alt, or the NVDA key, gets stuck in new occurrences
or if the same key gets stuck and no others. Experimentation by people will
answer that question.



If it turns out to be keys getting stuck, that may lead to a solution.



Gene









--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@freelists.org with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com


Re: Shortcut commands stopping working in NVDA

Gene
 

I should add that I remember at least one person describing the problem in a way that caused me to think it might be sticky keys and that’s why I started experimenting.;  I don’t want to take credit for an idea I saw from one or more other people.  I brought it up again because I didn’t think it got the attention it should and because the limited about of experimenting I’ve done, I have to wait until the problem occurs, has so far confirmed that sticky keys are the problem.
 
Gene

-----Original Message-----
 
From: Gene
Sent: Wednesday, July 21, 2021 7:02 PM
Subject: Re: [nvda] Shortcut commands stopping working in NVDA
 
I remember a bit of discussion of what you are describing before but I don’t think it was sustained enough to catch the attention of the developers on the list.  I didn’t remember who, for the most part, had brought it up.  I suppose it should be filed as a ticket. 
 
My impression from before is that the problem would be mentioned and one or two messages would result and it would then not be mentioned again for a good while.  While I think this is a general problem, it may be that not enough people complained of it that it was recognized as such.  I think that almost no one spoke of it as a sticky key problem before, which may have made the problem not properly replicable by developers.
 
Gene
-----Original Message-----
Sent: Wednesday, July 21, 2021 6:36 PM
Subject: Re: [nvda] Shortcut commands stopping working in NVDA
 

Yeah, I already said that a few months ago. I in fact go control left right, alt left right, windows, windows, shift left, right, tab when I know a key is stuck. This is not anything new, now we need to figure out why this happens.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, July 21, 2021 3:54 PM
To: nvda@nvda.groups.io
Subject: [nvda] Shortcut commands stopping working in NVDA

 

Occasionally, a problem where NVDA shortcut commands such as read title bar, open menus, etc. stop working has been discussed here.  I may have found out what is actually going on and it may either eliminate or almost fully eliminate the need to unload, then run NVDA again.

 

It appears to me that a key is getting stuck.  When this happens, try pressing the left shift key, then the right shift key quickly perhaps five or six times each.  Then see if the commands work again. 

 

Caution: It used to be and probably still is the default that if you press either shift something like five times, it will turn on something.  I don’t recall if it is some sort of sounds Windows will make when certain keys are pressed or sticky keys.  At any rate, if you haven’t turned off this behavior, don’t press the shift five times.  Try three or four. 

 

I’ve just been trying this recently.  I don’t have this happen enough to see if the same key, for example, one of the shift keys, or another key, such as either control, either alt, or the NVDA key, gets stuck in new occurrences or if the same key gets stuck and no others.  Experimentation by people will answer that question. 

 

If it turns out to be keys getting stuck, that may lead to a solution. 

 

Gene

 


Re: Shortcut commands stopping working in NVDA

 

Gene,

Thanks for the clarification.

There is the Windows Feature called sticky keys, and there are sticking keyboard keys, and there are unintentional software-generated sticky keys, too.  It's now clear that the last of the three is what's under discussion, and this was not initially clear to me.  And it's a different kettle of fish, as the saying goes.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Re: Shortcut commands stopping working in NVDA

Gene
 

I remember a bit of discussion of what you are describing before but I don’t think it was sustained enough to catch the attention of the developers on the list.  I didn’t remember who, for the most part, had brought it up.  I suppose it should be filed as a ticket. 
 
My impression from before is that the problem would be mentioned and one or two messages would result and it would then not be mentioned again for a good while.  While I think this is a general problem, it may be that not enough people complained of it that it was recognized as such.  I think that almost no one spoke of it as a sticky key problem before, which may have made the problem not properly replicable by developers.
 
Gene

-----Original Message-----
Sent: Wednesday, July 21, 2021 6:36 PM
Subject: Re: [nvda] Shortcut commands stopping working in NVDA
 

Yeah, I already said that a few months ago. I in fact go control left right, alt left right, windows, windows, shift left, right, tab when I know a key is stuck. This is not anything new, now we need to figure out why this happens.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, July 21, 2021 3:54 PM
To: nvda@nvda.groups.io
Subject: [nvda] Shortcut commands stopping working in NVDA

 

Occasionally, a problem where NVDA shortcut commands such as read title bar, open menus, etc. stop working has been discussed here.  I may have found out what is actually going on and it may either eliminate or almost fully eliminate the need to unload, then run NVDA again.

 

It appears to me that a key is getting stuck.  When this happens, try pressing the left shift key, then the right shift key quickly perhaps five or six times each.  Then see if the commands work again. 

 

Caution: It used to be and probably still is the default that if you press either shift something like five times, it will turn on something.  I don’t recall if it is some sort of sounds Windows will make when certain keys are pressed or sticky keys.  At any rate, if you haven’t turned off this behavior, don’t press the shift five times.  Try three or four. 

 

I’ve just been trying this recently.  I don’t have this happen enough to see if the same key, for example, one of the shift keys, or another key, such as either control, either alt, or the NVDA key, gets stuck in new occurrences or if the same key gets stuck and no others.  Experimentation by people will answer that question. 

 

If it turns out to be keys getting stuck, that may lead to a solution. 

 

Gene

 


Re: Shortcut commands stopping working in NVDA

Gene
 

Sticky keys in this context, I don’t know how else the term may be used, is caused by a screen-reader somehow causing a key to get stuck on, but not because of the keyboard.  I don’t know if JAWS still has the problem, but years ago, it had a sticky key problem.  It referred to the problem as sticky keys.  It appears that NVDA may have one now.
 
Gene

-----Original Message-----
Sent: Wednesday, July 21, 2021 6:33 PM
Subject: Re: [nvda] Shortcut commands stopping working in NVDA
 
On Wed, Jul 21, 2021 at 06:54 PM, Gene wrote:
If it turns out to be keys getting stuck, that may lead to a solution.
-
Gene,

Before I say what I'm about to say, I want to preface it with this contribution is greatly appreciated, at least by me.  This is a great diagnostic to undertake.

With that being said, if the root cause were traced to literal sticky keys, the solution is getting a new keyboard.  There is nothing that the developers of NVDA could or should do about sticking keyboard keys.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Re: Shortcut commands stopping working in NVDA

 

On Wed, Jul 21, 2021 at 07:49 PM, Don H wrote:
If this is a hardware issue why does restarting NVDA fix the issue?
-
This could be coincidental.  Sticking keys often "unstick" on their own.

There are things that can be done for process of elimination.  And let me make clear, I am not saying that this behavior is a hardware issue at the outset.  Just that it very well could be, and there are things that can be done, "dual and dualing" keyboards being something that can help to figure this out.  If the issue disappeared without restarting NVDA after pulling the primary keyboard, that would help to narrow things down.  Remember, if you have two keyboards and a key were to be sticking on either one, the machine would still be getting the input from the stuck keyboard.

All in all, this is a major detective effort.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Re: Shortcut commands stopping working in NVDA

Don H
 

If this is a hardware issue why does restarting NVDA fix the issue?

On 7/21/2021 6:40 PM, Brian Vogel wrote:
On Wed, Jul 21, 2021 at 07:36 PM, Sarah k Alawami wrote:
This is not anything new, now we need to figure out why this happens.
-
I say the following not to be snarky, but if it is actually sticking keys, we already know why this happens.
Another good thing, and dirt cheap, is to obtain a USB keyboard (and thrift stores are loaded with them, fully functional) to keep "as the testing spare" and check if the issue persists, when it occurs, on a different keyboard that's available for the machine.
If the shortcuts work immediately when you use the alternative keyboard, and consistently, you know you have a hardware issue of some sort with your primary keyboard.  While these are, relatively speaking, rare they are far from never happening.
--
Brian -Windows 10, 64-Bit, Version 21H1, Build 19043
Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.
That's what life is about.  And in that order.
        ~ Liza Minnelli


Re: Shortcut commands stopping working in NVDA

 

On Wed, Jul 21, 2021 at 07:36 PM, Sarah k Alawami wrote:
This is not anything new, now we need to figure out why this happens.
-
I say the following not to be snarky, but if it is actually sticking keys, we already know why this happens.

Another good thing, and dirt cheap, is to obtain a USB keyboard (and thrift stores are loaded with them, fully functional) to keep "as the testing spare" and check if the issue persists, when it occurs, on a different keyboard that's available for the machine.

If the shortcuts work immediately when you use the alternative keyboard, and consistently, you know you have a hardware issue of some sort with your primary keyboard.  While these are, relatively speaking, rare they are far from never happening.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Re: Shortcut commands stopping working in NVDA

Sarah k Alawami
 

Yeah, I already said that a few months ago. I in fact go control left right, alt left right, windows, windows, shift left, right, tab when I know a key is stuck. This is not anything new, now we need to figure out why this happens.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, July 21, 2021 3:54 PM
To: nvda@nvda.groups.io
Subject: [nvda] Shortcut commands stopping working in NVDA

 

Occasionally, a problem where NVDA shortcut commands such as read title bar, open menus, etc. stop working has been discussed here.  I may have found out what is actually going on and it may either eliminate or almost fully eliminate the need to unload, then run NVDA again.

 

It appears to me that a key is getting stuck.  When this happens, try pressing the left shift key, then the right shift key quickly perhaps five or six times each.  Then see if the commands work again. 

 

Caution: It used to be and probably still is the default that if you press either shift something like five times, it will turn on something.  I don’t recall if it is some sort of sounds Windows will make when certain keys are pressed or sticky keys.  At any rate, if you haven’t turned off this behavior, don’t press the shift five times.  Try three or four. 

 

I’ve just been trying this recently.  I don’t have this happen enough to see if the same key, for example, one of the shift keys, or another key, such as either control, either alt, or the NVDA key, gets stuck in new occurrences or if the same key gets stuck and no others.  Experimentation by people will answer that question. 

 

If it turns out to be keys getting stuck, that may lead to a solution. 

 

Gene

 


Re: Shortcut commands stopping working in NVDA

 

On Wed, Jul 21, 2021 at 06:54 PM, Gene wrote:
If it turns out to be keys getting stuck, that may lead to a solution.
-
Gene,

Before I say what I'm about to say, I want to preface it with this contribution is greatly appreciated, at least by me.  This is a great diagnostic to undertake.

With that being said, if the root cause were traced to literal sticky keys, the solution is getting a new keyboard.  There is nothing that the developers of NVDA could or should do about sticking keyboard keys.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Shortcut commands stopping working in NVDA

Gene
 

Occasionally, a problem where NVDA shortcut commands such as read title bar, open menus, etc. stop working has been discussed here.  I may have found out what is actually going on and it may either eliminate or almost fully eliminate the need to unload, then run NVDA again.
 
It appears to me that a key is getting stuck.  When this happens, try pressing the left shift key, then the right shift key quickly perhaps five or six times each.  Then see if the commands work again. 
 
Caution: It used to be and probably still is the default that if you press either shift something like five times, it will turn on something.  I don’t recall if it is some sort of sounds Windows will make when certain keys are pressed or sticky keys.  At any rate, if you haven’t turned off this behavior, don’t press the shift five times.  Try three or four. 
 
I’ve just been trying this recently.  I don’t have this happen enough to see if the same key, for example, one of the shift keys, or another key, such as either control, either alt, or the NVDA key, gets stuck in new occurrences or if the same key gets stuck and no others.  Experimentation by people will answer that question. 
 
If it turns out to be keys getting stuck, that may lead to a solution. 
 
Gene
 


Introducing Event Tracker, an add-on to track and record information on events #addonrelease

 

Hi all,

Yes, a brand new add-on, and most likely my last one for now:

A new add-on designed for developers and power users, called Event Tracker is now available:

Event Tracker (nvda-project.org)

An event is raised when things happen, such as typing characters, moving system focus, and when notifications are announced. Event Tracker will track these events and will log information such as the control where the event came from, its name and role, app module, and information specific to accessibility API’s such as MSAA properties. As this is an add-on designed for developers and power users, it is not really recommended for beginners, and in order to use the add-on, you must be running NVDA in debug logging mode.

Cheers,

Joseph


Re: Notice for users of Joseph Lee's add-ons: what's new in version 21.08, an important announcement or two regarding support for NVDA changes going forward

anthony borg
 

Many thanks Joseph for your great help and support you are giving us.

 

Regards

 

Anthony

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: 21 July 2021 07:06
To: nvda@nvda.groups.io
Subject: [nvda] Notice for users of Joseph Lee's add-ons: what's new in version 21.08, an important announcement or two regarding support for NVDA changes going forward

 

Hello NvDA users,

First, I hope you are staying safe and healthy in the midst of events around the world, namely the ongoing pandemic.

Second, I and several folks here are in contact with NvDA add-ons community regarding add-ons you know and love. I’m delighted to announce that, as of this moment, 70 percent of add-ons hosted on community add-ons website are showing as compatible with NVDA 2021.1. I know there are more add-ons out there, and more of these are becoming compatible as time passes. As was stated many times, the actual people to contact regarding add-ons is the author of these add-ons, not NV Access, and authors were encouraged to update incompatible add-ons as soon as possible.

 

Onto the matter at hand:

Heads up if you are using any of my add-ons (Add-on Updater, Control Usage Assistant, Enhanced Touch Gestures, GoldWave, Resource Monitor, StationPlaylist, Windows App Essentials): version 21.08 updates are being prepared (scheduled for next week). Most add-ons include feature updates, while others include localization updates from translators around the world. But most importantly, a major change in NVDA is coming which will affect most of my add-ons, and the time has come to start letting go of most add-ons to focus on school.

What’s new in version 21.08? For starters, Windows 11 support. Enhanced Touch Gestures, Resource Monitor, and Windows App Essentials will include support for Windows 11. The biggest changes were made in Windows App Essentials, followed by Resource Monitor, the former to work around current Windows 11 preview issues, the latter to recognize Windows 11 builds properly. A bonus for Enhanced Touch Gestures users: current and upcoming add-on releases will work beautifully on Windows 11. Note that for at least Windows App Essentials, Windows 11 support is experimental/in preview and things can change without notice (I’m planning a follow-up release in late August that will update the add-on to support the state of Windows 11 preview then).

Second, localization updates. These include all add-ons. Several add-ons didn’t have localization updates for almost half a year, while others include recent changes. Note that Add-on Updater is not amongst these at this time.

Third (and most importantly and will get lengthy)), preparing to respond to changes being introduced to NVDA. One of the biggest features in Python 3 series is support for enumerations (or enums for short). An enumeration is a collection of values and flags that are easily grouped and identifiable. For example, suppose you are defining colors and decide to use integers to represent colors such as “blue” (0), “red” (1), “green” (2) and so on, housed inside a “colors” collection. In the past, you had to remember which color corresponds to which integer, but with enumerations, when you say “colors.Red”, Python will know what you are talking about (integer 1). This makes the program source code easier to read.

In the NVDA world, there are places in NVDA screen reader source code that resemble a collection of flags and constants. The best known example is a module called “control types” that include definitions of control roles and states. The roles and states collection is so important that NVDA itself and many add-ons use this module as a backbone for their proper operation, including recognizing specific controls in apps, reacting to state changes such as radio buttons being checked, and even providing user-level help (Control Usage Assistant). The current code (NVDA 2021.1) is compatible with both Python 2 and 3, but NV Access and contributors felt modernization should be attempted, specifically using facilities from Python 3 in more places.

Last year, NVDA moved from Python 2 to Python 3, the former without enumerations, the latter including it as part of an “enum” module. To study the impact of using enumerations to represent values and constants, NV Access introduced enums in a limited scale in NVDA 2020.1 (May 2020), specifically to represent speech output reasons (converted from a collection of integers to an enumeration in 2020.1). It turned out several add-ons (including StationPlaylist) used the old speech style, and since NVDA 2021.1 removed old style speech output reason collection in favor of enumeration, add-ons were modified recently to take advantage of the new style (that’s one of the reasons why, for some add-ons, you can’t modify manifests alone).

In the next version of NVDA (2021.2), enumeration usage is expanded to cover control roles and states (these are now enumerations, not constants anymore), and this work is termed “control types refactor”. Because the new enumerations are here to stay, NV Access promised old style (constants) will remain until NVDA 2022.1 (the next backwards incompatible release) is released to the public; until then, add-ons are welcome to use old and new styles to detect control roles and states.

So what does this “control types refactor” got to do with Joseph Lee’s add-ons? Control types refactor affects add-ons using control types module contents, including Control Usage Assistant, Enhanced Touch Gestures, GoldWave, StationPlaylist, and Windows App Essentials. At least until NVDA 2022.1 is released, the old control roles and states style will be kept, so it won’t affect my add-ons. However, after looking at the scale of control types refactor, coupled with impact of graduate school on add-on maintenance work, I decided to let my add-ons work with new (enumeration) style sooner than later. Therefore;

I hereby announce that version 21.08 of my add-ons will be the last releases to support NVDA 2021.1 or earlier, with the next releases exclusively supporting NVDA 2021.2 or later. This is so that I can spend more time studying and eventually easing add-on maintenance.

Not all add-ons are impacted by this announcement at the moment:

  • Affected add-ons: Control Usage Assistant, Enhanced Touch Gestures, GoldWave, StationPlaylist
  • Not affected but a separate compatibility announcement forthcoming: Resource Monitor
  • Affected by things in addition to control types refactor: Windows App Essentials due to Windows 11 being a preview release at the moment

Add-on Updater is not affected at this time.

Next steps:

  1. For affected add-ons, there will be no updates between 21.08 (next week) and the week during which NVDA 2021.2 release candidate is announced. The actual releases requiring NVDA 2021.2 will be posted at least two days after NVDA 2021.2 is released to the general public. This is done so you can focus on other add-ons.
  2. Windows App Essentials will receive updates while Windows 11 is being finalized. This is so that the add-on and NVDA can respond to late changes.
  3. To make life easier, there will be no updates to Resource Monitor between 21.08 and the day NVDA 2021.2 is released to everyone. Again this is so that I can focus on graduate studies before releasing a version of Resource Monitor requiring newer NVDA releases.
  4. Add-on Updater is on standby – that is, localization updates can be released anytime.

 

As a volunteer add-on author and maintainer with NVDA code contribution experience, I take add-on maintenance seriously. I feel it is important to tell you what’s going on so you can prepare accordingly, especially since what I just announced is based on changes to NVDA that will affect many add-ons. As long as I maintain these add-ons, I will do my best to make add-ons work with newer NVDA releases and make them compatible the day new NVDA versions show up when you check for updates.

 

Thanks. Hope this helps.

Cheers,

Joseph


Welcome to the NVDA Community Add-ons website - Event Tracker #nvdaaddonsfeed

nvda@nvda.groups.io Integration <nvda@...>
 

Event Tracker

  • Author: Joseph Lee
  • Download stable version
  • NVDA compatibility: 2021.1 and beyond

This add-on outputs information about objects for which events were fired. Properties recorded in debug log mode include object type, name, role, event, app module, and accessibility API specific information such as accName for IAccessible object and Automation Id for UIA objects.

Notes:

  • This add-on is designed for developers and power users needing to track events coming from apps and various controls.
  • In order to use the add-on, NVDA must be logging in debug mode (configured from general settings/logging level, or restart with debug logging enabled).
  • It might be possible that add-ons loaded earlier than Event Tracker may not pass on the event to other add-ons, including Event Tracker. If this happens, Event Tracker will not be able to log events.
  • Events are handled from global plugins, app modules, tree interceptors, and NVDA objects, in that order.

Events and their information

The following events are tracked and recorded:

  • Focus manipulation: gain focus, lose focus, focus entered, foreground
  • Changes: name, value, state, description, live region
  • UIA events: element selected, item status, controller for, notification, tooltip open, window open, text change

For each event, the following information will be recorded:

  • Event name
  • Object
  • Object name
  • Object role
  • Object value or state depending on events
  • App module
  • For IAccessible objects: acc name, child ID
  • For UIA objects: Automation Id, class name, notification properties if recording notification event information

Version 21.07

  • Initial release.


NVDA 2021.1 and add-ons: more add-on updates #addonrelease

 

Hello all,

More add-ons were updated to support NVDA 2021.1. Among these are OCR, Switch Synth, and Extended Winamp. Just like we did for the last three years, please check for updates from Add-on Updater (some of you should have received a Windows 10/11 notification about add-on updates by now).

By the way, a new add-on from yours truly is on its way…

Cheers,

Joseph


Re: Com Registration fixing and narrator

mk360
 

I sent you a log privately. Please, I don't know whats the bug for NVDA, I preffer win 10 actually, and I can help testing whatever you need, but I need windows 7 for my work :(.

El 20/07/2021 a las 23:54, Quentin Christensen escribió:
If you turn off Narrator on the login screen, does it come back next time?


I haven't encountered the issue, and we'd need a bit more info to try to investigate (such as Windows & NVDA versions, etc, and ideally a debug log from running the COM registration tool - though not sure if it would show anything) - if you'd like to investigate a bit more, after fixing it and restarting to confirm, if you then ran the COM registration tool again it would be interesting to see if it did the same thing.

Regards

Quentin.

On Wed, Jul 21, 2021 at 10:38 AM mk360 <mk.seventhson@...> wrote:
Hi,

I'm having a problem with com registration fixing and narrator. I
executed the tool under Windows 7 and now Narrator starts on secure
screens, what can I do? because when it starts I can't use NVDA and is
very disturbing.

Thanks,

mk.








--
Quentin Christensen
Training and Support Manager


Notice for users of Joseph Lee's add-ons: what's new in version 21.08, an important announcement or two regarding support for NVDA changes going forward

 
Edited

Hello NvDA users,

First, I hope you are staying safe and healthy in the midst of events around the world, namely the ongoing pandemic.

Second, I and several folks here are in contact with NvDA add-ons community regarding add-ons you know and love. I’m delighted to announce that, as of this moment, 70 percent of add-ons hosted on community add-ons website are showing as compatible with NVDA 2021.1. I know there are more add-ons out there, and more of these are becoming compatible as time passes. As was stated many times, the actual people to contact regarding add-ons is the author of these add-ons, not NV Access, and authors were encouraged to update incompatible add-ons as soon as possible.

 

Onto the matter at hand:

Heads up if you are using any of my add-ons (Add-on Updater, Control Usage Assistant, Enhanced Touch Gestures, GoldWave, Resource Monitor, StationPlaylist, Windows App Essentials): version 21.08 updates are being prepared (scheduled for next week). Most add-ons include feature updates, while others include localization updates from translators around the world. But most importantly, a major change in NVDA is coming which will affect most of my add-ons, and the time has come to start letting go of most add-ons to focus on school.

What’s new in version 21.08? For starters, Windows 11 support. Enhanced Touch Gestures, Resource Monitor, and Windows App Essentials will include support for Windows 11. The biggest changes were made in Windows App Essentials, followed by Resource Monitor, the former to work around current Windows 11 preview issues, the latter to recognize Windows 11 builds properly. A bonus for Enhanced Touch Gestures users: current and upcoming add-on releases will work beautifully on Windows 11. Note that for at least Windows App Essentials, Windows 11 support is experimental/in preview and things can change without notice (I’m planning a follow-up release in late August that will update the add-on to support the state of Windows 11 preview then).

Second, localization updates. These include all add-ons. Several add-ons didn’t have localization updates for almost half a year, while others include recent changes. Note that Add-on Updater is not amongst these at this time.

Third (and most importantly and will get lengthy)), preparing to respond to changes being introduced to NVDA. One of the biggest features in Python 3 series is support for enumerations (or enums for short). An enumeration is a collection of values and flags that are easily grouped and identifiable. For example, suppose you are defining colors and decide to use integers to represent colors such as “blue” (0), “red” (1), “green” (2) and so on, housed inside a “colors” collection. In the past, you had to remember which color corresponds to which integer, but with enumerations, when you say “colors.Red”, Python will know what you are talking about (integer 1). This makes the program source code easier to read.

In the NVDA world, there are places in NVDA screen reader source code that resemble a collection of flags and constants. The best known example is a module called “control types” that include definitions of control roles and states. The roles and states collection is so important that NVDA itself and many add-ons use this module as a backbone for their proper operation, including recognizing specific controls in apps, reacting to state changes such as radio buttons being checked, and even providing user-level help (Control Usage Assistant). The current code (NVDA 2021.1) is compatible with both Python 2 and 3, but NV Access and contributors felt modernization should be attempted, specifically using facilities from Python 3 in more places.

Last year, NVDA moved from Python 2 to Python 3, the former without enumerations, the latter including it as part of an “enum” module. To study the impact of using enumerations to represent values and constants, NV Access introduced enums in a limited scale in NVDA 2020.1 (May 2020), specifically to represent speech output reasons (converted from a collection of integers to an enumeration in 2020.1). It turned out several add-ons (including StationPlaylist) used the old speech style, and since NVDA 2021.1 removed old style speech output reason collection in favor of enumeration, add-ons were modified recently to take advantage of the new style (that’s one of the reasons why, for some add-ons, you can’t modify manifests alone).

In the next version of NVDA (2021.2), enumeration usage is expanded to cover control roles and states (these are now enumerations, not constants anymore), and this work is termed “control types refactor”. Because the new enumerations are here to stay, NV Access promised old style (constants) will remain until NVDA 2022.1 (the next backwards incompatible release) is released to the public; until then, add-ons are welcome to use old and new styles to detect control roles and states.

So what does this “control types refactor” got to do with Joseph Lee’s add-ons? Control types refactor affects add-ons using control types module contents, including Control Usage Assistant, Enhanced Touch Gestures, GoldWave, StationPlaylist, and Windows App Essentials. At least until NVDA 2022.1 is released, the old control roles and states style will be kept, so it won’t affect my add-ons. However, after looking at the scale of control types refactor, coupled with impact of graduate school on add-on maintenance work, I decided to let my add-ons work with new (enumeration) style sooner than later. Therefore:

I hereby announce that version 21.08 of my add-ons will be the last releases to support NVDA 2021.1 or earlier, with the next releases exclusively supporting NVDA 2021.2 or later. This is so that I can spend more time studying and eventually easing add-on maintenance.

Not all add-ons are impacted by this announcement at the moment:

  • Affected add-ons: Control Usage Assistant, Enhanced Touch Gestures, GoldWave, StationPlaylist
  • Not affected but a separate compatibility announcement forthcoming: Resource Monitor
  • Affected by things in addition to control types refactor: Windows App Essentials due to Windows 11 being a preview release at the moment

Add-on Updater is not affected at this time.

Next steps:

  1. For affected add-ons, there will be no updates between 21.08 (next week) and the week during which NVDA 2021.2 release candidate is announced. The actual releases requiring NVDA 2021.2 will be posted at least two days after NVDA 2021.2 is released to the general public. This is done so you can focus on other add-ons.
  2. Windows App Essentials will receive updates while Windows 11 is being finalized. This is so that the add-on and NVDA can respond to late changes.
  3. To make life easier, there will be no updates to Resource Monitor between 21.08 and the day NVDA 2021.2 is released to everyone. Again this is so that I can focus on graduate studies before releasing a version of Resource Monitor requiring newer NVDA releases.
  4. Add-on Updater is on standby – that is, localization updates can be released anytime.


Update: Event Tracker is affected by control types refactor, and a version to be released later this year will require NvDA 2021.2 and later also.

As a volunteer add-on author and maintainer with NVDA code contribution experience, I take add-on maintenance seriously. I feel it is important to tell you what’s going on so you can prepare accordingly, especially since what I just announced is based on changes to NVDA that will affect many add-ons. As long as I maintain these add-ons, I will do my best to make add-ons work with newer NVDA releases and make them compatible the day new NVDA versions show up when you check for updates.

 

Thanks. Hope this helps.

Cheers,

Joseph

5481 - 5500 of 91853