Date   

Re: Shortcut commands stopping working in NVDA

Curtis Delzer
 

But, Gene is pointing out a behavior which has nothing to do whatever with anything truly "sticking" in the real world, but only in the electronic one. Jaws does this where it believes a given control or alt key gets stuck in the past, where I've fixed it by pressing the added key which jfw always indicated was stuck, when in fact, if it were mechanically stuck I'd hear either repeats of the control key, or alt key, or interrupted speech because my synth would be interrupted by a real sticky mechanical action. :)
Tapping the "stuck" key usually fixed the action in JFW, I'll try and see if it fixes NVDA, but I doubt it.


Curtis Delzer
HS
K 6 V F O
Rialto, CA

curtis@calweb.com

On 7/21/2021 4:33 PM, Brian Vogel wrote:
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: Update appears to have broken Musescore accessibility with NVDA

umut korkmaz
 

Hi Christopher,

I sent you information in the first two messages.

I am using nvda latest version and musescore latest version. I don't have the problems you describe.

Regards,

Umut KORKMAZ

 

Windows 10 için Posta ile gönderildi

 

Kimden: Christopher Bartlett
Gönderilme: 22 Temmuz 2021 Perşembe 18:33
Kime: nvda@nvda.groups.io
Konu: [nvda] Update appears to have broken Musescore accessibility with NVDA

 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

 

Christopher Bartlett

p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


 

--

Christopher Bartlett

 


Re: Update appears to have broken Musescore accessibility with NVDA

umut korkmaz
 

You can specify the Tempo (BPM) value of our work in the New score wizard at first; If we want, we can add it to the size of our work later.

Now let's first add the New tempo value to our work:

In our example, let's assume that the first 8 measures have a tempo value of 120, and from the 9th measure a value of 75 tempo.

We make sure that we are at the beginning of the first measure by using the Right and Left arrow keys in normal or note writing mode. We can also make sure that we are in the first dimension by opening the search field with CTRL+F and typing 1 and pressing enter.

By pressing ALT+Shift+T, we come to the Tempo writing area.

We find the number 80 after the equal sign with the right arrow and delete it with the del key, and write our new value, the value 120 in our example. and exit with the escape key.

When we switch to note-writing mode with the N key and hover over the first measure:

Pause Measure Measure 1 Beat 1 Tempo Quarter note (crotchet) stem up = 120

NVDA will voice the phrase to us and we'll make sure our value is added.

Again, regardless of the mode, come to the beginning of the 9th measure and open the tempo writing area with ALT+Shift+T; By deleting the digits after the equals, we enter the value 75 this time and exit with the escape key.

When we switch to the note-writing mode with N and come to the beginning of the 9th measure; NVDA tells us this time:

Pause Measure Measure 9 Beat 1 Tempo Quarter note (crotchet) stem up = 75

and we will make sure that the transaction is successful.

In this case: The first eight measures will play at 120 BPM, and the 9th measure and beyond will play at a tempo of 75 BPM.

If we wish, we can add the tempo values ​​by coming to the beginning of the measures we want after we have written our piece, or we can add the tempo values ​​to the beginning of the measures we want first, and then write our note.

We do not need to press enter after opening the typing area with ALT+Shift+T and typing the value.

After typing the value, we may need to press the escape key more than once.

 

Windows 10 için Posta ile gönderildi

 

Kimden: Christopher Bartlett
Gönderilme: 22 Temmuz 2021 Perşembe 18:33
Kime: nvda@nvda.groups.io
Konu: [nvda] Update appears to have broken Musescore accessibility with NVDA

 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

 

Christopher Bartlett

p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


 

--

Christopher Bartlett

 


Re: Shortcut commands stopping working in NVDA

Curtis Delzer
 

jaws exhibited this behavior and still does where a given control or alt key gets stuck and then if you've told jaws to say your keystrokes you'd hear the extra key when you didn't initially press it.
I will try that fix using NVDA and see if access to the NVDA commands return.

Curtis Delzer
HS
K 6 V F O
Rialto, CA

curtis@calweb.com

On 7/21/2021 3:54 PM, Gene wrote:
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: Update appears to have broken Musescore accessibility with NVDA

umut korkmaz
 

We can continue our work with a different tempo number than the one we started in a piece. Let's assume that the first 16 measures in our work are 4/4 (four quarters), and the next four measures are 9/8 (nine eights).

1. We write down our first 16 measurements.

2. When we reach the 17th measure, we press the letter n to make sure that we are in step-by-step note entry mode.

3. Press Shift+F9 to open the main palette window.

4. In the tree view, we find the option Numbers with the down arrow key.

5. Press the Shift+tab keys once, select the 9/8 procedure number from the list that comes up with the arrow keys and press the enter key.

Now, we can see that the first 16 meters of our work have the number of 4/4, and from the 17th measure, the number of 9/8.

Let's say we want to go back to the 4/4 procedure number after the 33rd measure. In this case, it will be sufficient to repeat the above operations and this time select the 4/4 option from the list and press enter.

We can also add a measure that is not in the size list.

For this:

Again, in the measurement numbers window, when you type 5 in the first writing field and 8 in the second writing field, then find the add button with the tab key and press the enter key, five octal procedure numbers are added to the list.

However, the procedure numbers added later cannot be read by NVDA yet.

 

Windows 10 için Posta ile gönderildi

 

Kimden: Christopher Bartlett
Gönderilme: 22 Temmuz 2021 Perşembe 18:33
Kime: nvda@nvda.groups.io
Konu: [nvda] Update appears to have broken Musescore accessibility with NVDA

 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

 

Christopher Bartlett

p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


 

--

Christopher Bartlett

 


Re: Shortcut commands stopping working in NVDA

Curtis Delzer
 

happens to me also, and in my case all NVDA commands such as shutting down, 'NVDA+N, for getting into the menus, all is non responsive, so I just re-start NVDA which always fixes it.
control-alt-N is not non-responsive since it is a system command, not one internal to NVDA.

Curtis Delzer
HS
K 6 V F O
Rialto, CA

curtis@calweb.com

On 7/21/2021 4:49 PM, Don H wrote:
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


Update appears to have broken Musescore accessibility with NVDA

Christopher Bartlett
 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

Christopher Bartlett
p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


--
Christopher Bartlett


Re: my request for NVDA

 

On Thu, Jul 22, 2021 at 10:02 AM, Sarah k Alawami wrote:
what is your windows build, I think you said your nvda build but I can’t remember now.
-
He mentioned Windows 10 Pro Version 21H1, which means the Build must be 19043, but it still helps to have the exact dot number on the build, too, which can be obtained via the winver command.  Most recent for home is 1110, I believe, but it sometimes can be different for Pro.  NVDA was stated as 2021.1.

But even with all that information, what we need is specific descriptions of the difficulties being encountered in the exact contexts of use, as both you and I have now noted.
--

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: my request for NVDA

Sarah k Alawami
 

You need to be more specific. Provide detailed use cases as to why nvda is not working with your softwares, what would you like to see improved. If you failt od this, no one can help you. Also what are your computer’s specs, what is your windows build, I think you said your nvda build but I can’t remember now.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of ( NAJAF . Naqvi )
Sent: Wednesday, July 21, 2021 10:51 PM
To: NVDA Groups.IO <nvda@nvda.groups.io>
Subject: [nvda] my request for NVDA

 

Hello NVDA 

this is me !!

I use Adobe software.

My-List:

1: lightroom CC

2: photoshop.

3: Audition 

4: Pr

5: Ai 

6:Ae

I want my NVDA to work better.

With: windows10 pro 21h1

and NVDA 2021.1.

how to ?????

please reply me 

 

 

have a good day 


Re: my request for NVDA

 

On Thu, Jul 22, 2021 at 01:51 AM, ( NAJAF . Naqvi ) wrote:

I want my NVDA to work better with: windows10 pro 21h1 and NVDA 2021.1. how to ?????

-
Seriously, as new member you need to know that this sort of question is so broad as to be meaningless.  

If you want assistance, you need to be much more specific about exactly what it is you are having a problem with, whether it be in Windows 10 or a specific program.

There is no way to answer your query as posed.  What you've asked is akin to asking, "I want to understand Calculus.  How do I do that?," where the only answer is equally broad and useless, "Take classes."
--

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: Unable to connect to NVDA Remote Server

Mobeen Iqbal
 

Hi.

Are the correct ports open and accessible? I believe port 6837 needs to be open.

cheers,

Mo.

On 22/07/2021 08:20, arqam mehmood wrote:
Hi everyone.
I've recently installed NVDA Remote Server on my debian server.
everything is ok.
when i check sudo NVDARemoteServer status.
it says, active.
but when I tried to connect through my client, it won't connect.
any idea what is the problem?
Arqam Mehmood.




Unable to connect to NVDA Remote Server

arqam mehmood
 

Hi everyone.
I've recently installed NVDA Remote Server on my debian server.
everything is ok.
when i check sudo NVDARemoteServer status.
it says, active.
but when I tried to connect through my client, it won't connect.
any idea what is the problem?
Arqam Mehmood.


Re: Shortcut commands stopping working in NVDA

 
Edited

Hi,

May I offer a really strange suggestion: to those affected by input problem, can you try using the latest NVDA alpha snapshot for at least several days (perhaps as a portable copy) and report as to if the problem is resolved?

Cheers,

Joseph


Re: Shortcut commands stopping working in NVDA

Pranav Lal
 

Jackie,

Were you using keepass 2 by any chance?

Pranav

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jackie
Sent: Thursday, July 22, 2021 6:27 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Shortcut commands stopping working in NVDA

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


my request for NVDA

 

Hello NVDA 
this is me !!
I use Adobe software.
My-List:
1: lightroom CC
2: photoshop.
3: Audition 
4: Pr
5: Ai 
6:Ae
I want my NVDA to work better.
With: windows10 pro 21h1
and NVDA 2021.1.
how to ?????
please reply me 


have a good day 


Re: Shortcut commands stopping working in NVDA

 

Well, I guess one small piece of good news with regard to this issue, even if it is a workaround, is that the Kill NVDA add-on has been updated for compatibility with NVDA 2021.1.
--

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
 

That’s good to know.  I should have searched for a ticket but the problem has been arounde for a long time and has been discussed so little that I didn’t.
 
Gene

-----Original Message-----
From: Joseph Lee
Sent: Wednesday, July 21, 2021 8:31 PM
Subject: Re: [nvda] 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

Sarah k Alawami
 

For me it was nvda 2019.x before the python conversion. And narrator would get stuck as well. The same thing would be done to fix it though.

 

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

 

I had an instance this evening where neither shift key was stuck.  I don’t remember what I figured out was stuck control or alt now. 

 

I don’t know if this line of inquiry would help developers figure out the problem, but sticky keys weren’t always a problem.  It never occurs in NVDA 13.  Perhaps if people remember what the first version they recall it occurring in, it might help developers figure out what might have changed.  I didn’t use current versions of NVDA for a good while.  I started doing so recently but I have no idea in which version the problem began.

 

Also, it appears to me that a key becomes stuck regarding NVDA commands but not affecting the general operation of the computer.  For example, a shift key might be stuck, resulting in NVDA commands not working, but not resulting in every letter typed being a capital letter.;  This may be important in trying to figure out the problem.

 

Gene

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

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

From: Jackie

Sent: Wednesday, July 21, 2021 7:56 PM

Subject: Re: [nvda] Shortcut commands stopping working in NVDA

 

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@...> 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@... 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

Sarah k Alawami
 

Oh thank god. I've been having this issue now for at least a year and it's random too, but annoying at best when it happens.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Spivey via groups.io
Sent: Wednesday, July 21, 2021 6:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Shortcut commands stopping working in NVDA

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

Gene
 

I had an instance this evening where neither shift key was stuck.  I don’t remember what I figured out was stuck control or alt now. 
 
I don’t know if this line of inquiry would help developers figure out the problem, but sticky keys weren’t always a problem.  It never occurs in NVDA 13.  Perhaps if people remember what the first version they recall it occurring in, it might help developers figure out what might have changed.  I didn’t use current versions of NVDA for a good while.  I started doing so recently but I have no idea in which version the problem began.
 
Also, it appears to me that a key becomes stuck regarding NVDA commands but not affecting the general operation of the computer.  For example, a shift key might be stuck, resulting in NVDA commands not working, but not resulting in every letter typed being a capital letter.;  This may be important in trying to figure out the problem.
 
Gene

-----Original Message-----
-----Original Message-----
From: Jackie
Sent: Wednesday, July 21, 2021 7:56 PM
Subject: Re: [nvda] Shortcut commands stopping working in NVDA
 
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@...> 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@... 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




5421 - 5440 of 91814