1. Nvda | Nvda
  2. Topics

Locked NVDA is trapping my grave accent key

Brian Vogel
 

On Mon, Jan 23, 2023 at 10:45 AM, bering.p wrote:
In summary, notice to all those who use extensions, it is not on this list that you should go to get help. It is clearly announced.
-
Paul,

I am speaking as moderator, and I want to be abundantly clear:  DO NOT PUT WORDS INTO MY MOUTH.

Extensions are routinely discussed on this group from a "how to use them" perspective.  They are not discussed at the development or debugging level, period, end of sentence.  There are venues dedicated to that, if such is needed, and as you proposed private conversations are also just fine.

I don't give a flying rat's ass what you think of my moderation style.  If you have issues with what a moderator or group owner has said in regard to how a group is run, then please do the adult thing and take it up via that group's owner address.

We are done now, and this topic is locked.
--

Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881
bering.p
 

Dear Sir.
Let me remind you that this discussion was initiated on this list and that my first message was not addressed to you but to Joseph Lee who had indicated that a discussion had taken place on another list concerning the subject.
This message was just intended to know this other discussion and not to continue to treat the problem on this list and your interventionist answer has somewhat rotten the discussion without answering the message.
Too bad because we lose a lot of time because of this kind of attitude.
On the other hand, when it's clear, I don't see why you have to read between the lines. Admit all the same that this kind of answer does not clarify the ideas either.
In summary, notice to all those who use extensions, it is not on this list that you should go to get help. It is clearly announced.
Too much rigor is a form of censorship.
My last post on this list regarding this topic whatever the answer, rest assured.Best regards.
Paul.
Le 23/01/2023 14:38, Brian Vogel a écrit :

On Mon, Jan 23, 2023 at 04:07 AM, bering.p wrote:
Yes sir.
If it is very clear for you, it is not for me.
-
Paul,

You can keep the attitude.  Discussions of development level add-on issues do not belong here.  All I did was suggest that if they are to be taken up, in public, that they be taken up on the correct group.

This very discussion, here, seems to give a pretty clear indication, if you read it, and read between the lines.  I do hope that you have been contacted privately, as that was the appropriate thing to ask for.
--

Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881
Brian Vogel
 

On Mon, Jan 23, 2023 at 04:07 AM, bering.p wrote:
Yes sir.
If it is very clear for you, it is not for me.
-
Paul,

You can keep the attitude.  Discussions of development level add-on issues do not belong here.  All I did was suggest that if they are to be taken up, in public, that they be taken up on the correct group.

This very discussion, here, seems to give a pretty clear indication, if you read it, and read between the lines.  I do hope that you have been contacted privately, as that was the appropriate thing to ask for.
--

Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881
bering.p
 

Yes sir.
If it is very clear for you, it is not for me.
I can't find any trace of discussion that demonstrates that it is the extension that is in question, (neither on this list, nor on nvda-addons) and that's what I'm looking for.
In case you haven't noticed, I asked to be contacted privately and not on this list.
With that, bye.
Best regards.
Paul.
Le 22/01/2023 18:06, Brian Vogel a écrit :

The discussion (single post) on the Add-Ons group is here:  
Looking for Paul Ber19 maintainer of the NVDA Global commands extension
It's simply Mr. Mehler asking Mr. Bering to contact him.

Since it's pretty clear now that this issue does lie in the extension rather than the NVDA core, it would be a good idea to get into the nitty-gritty on the NVDA Add-Ons group rather than here, particularly the debugging aspects.
--

Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881
Brian Vogel
 

The discussion (single post) on the Add-Ons group is here:  
Looking for Paul Ber19 maintainer of the NVDA Global commands extension
It's simply Mr. Mehler asking Mr. Bering to contact him.

Since it's pretty clear now that this issue does lie in the extension rather than the NVDA core, it would be a good idea to get into the nitty-gritty on the NVDA Add-Ons group rather than here, particularly the debugging aspects.
--

Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881
bering.p
 

Hi,
I'll be happy to correct the problem, if there is a problem, but I can't find any discussion about it on the list you pointed to, and can't reproduce it either.
Can you give me a link?
David, are you using NVDAExtensionGlobalPlugin add-on?
If so, can you provide me privately, the NVDA log in "debug" mode?
Thanks.
Best regards.
 
Paul.
Le 22/01/2023 13:21, Joseph Lee a écrit :

Hi,

Based on latest messages from NVDA add-ons list, it appears NVDA Extensions add-on is the one that ate the grave accent key.

Cheers,

Joseph
Joseph Lee
 

Hi,

Based on latest messages from NVDA add-ons list, it appears NVDA Extensions add-on is the one that ate the grave accent key.

Cheers,

Joseph
Brian's Mail list account
 

Would that be only on a US keyboard?

Is this the key that says U acute on my UK machine?
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: "Sarah k Alawami" <marrie12@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, January 22, 2023 12:19 AM
Subject: Re: [nvda] NVDA is trapping my grave accent key


Ich add on did you disable? If you talk to the author you might be able to submit a bug report.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of David Mehler
Sent: Saturday, January 21, 2023 2:18 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA is trapping my grave accent key

Hello,

I got it, had to disable the addon but functionality is back.


Thanks.
Dave.


On 1/21/23, Tyler Spivey via groups.io <tspivey@...> wrote:
Try one of these:

First, check if that gesture is assigned to anything recognizable.
1. Press NVDA+1 to turn on input help.
2. Press grave accent. If the addon script has documentation it should
tell you what it does, and you can use the Input gestures dialog to
unbind it.
3. Press NVDA+1 to turn input help off again.
If pressing grave didn't tell you what it did, the script it wanted to
execute should still be in your log, so pop it up with NVDA, Tools,
View log and look near the end.

If that doesn't help, disable half your addons and see if the problem
goes away. If it does, you know it's one of those.

On 1/21/2023 1:45 PM, David Mehler wrote:
Hello,

I'm hoping someone can tell me why this is happening. I'm using the
latest NVDA and either it or an add-on is trapping my grave accent
key that's the key immediately to the left of the number 1 key on the
top row. Whenever I hit said key I get a beep, hit it again and I get
a higher-pitched beep. At first I thought this might be an issue with
my keyboard, older one wireless, might be going bad, so just to try
something I restarted NVDA with add-ons disabled and the grave accent
key started working again, restarted normally and the same problem.

I'm open to troubleshooting suggestions.

Thanks.
Dave.















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

Sarah Alawami, owner of flying Blind. Visit my website ( http://flyingblind.us ) to read my story.

Windows 11 22H2 (x64) build 22621.963
NVDA Version: 2022.3.3

Microsoft 365 MSO (Version 2211 Build 16.0.15831.20098) 64-bit
Sarah k Alawami
 

Ich add on did you disable? If you talk to the author you might be able to submit a bug report.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of David Mehler
Sent: Saturday, January 21, 2023 2:18 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA is trapping my grave accent key

Hello,

I got it, had to disable the addon but functionality is back.


Thanks.
Dave.


On 1/21/23, Tyler Spivey via groups.io <tspivey@...> wrote:
Try one of these:

First, check if that gesture is assigned to anything recognizable.
1. Press NVDA+1 to turn on input help.
2. Press grave accent. If the addon script has documentation it should
tell you what it does, and you can use the Input gestures dialog to
unbind it.
3. Press NVDA+1 to turn input help off again.
If pressing grave didn't tell you what it did, the script it wanted to
execute should still be in your log, so pop it up with NVDA, Tools,
View log and look near the end.

If that doesn't help, disable half your addons and see if the problem
goes away. If it does, you know it's one of those.

On 1/21/2023 1:45 PM, David Mehler wrote:
Hello,

I'm hoping someone can tell me why this is happening. I'm using the
latest NVDA and either it or an add-on is trapping my grave accent
key that's the key immediately to the left of the number 1 key on the
top row. Whenever I hit said key I get a beep, hit it again and I get
a higher-pitched beep. At first I thought this might be an issue with
my keyboard, older one wireless, might be going bad, so just to try
something I restarted NVDA with add-ons disabled and the grave accent
key started working again, restarted normally and the same problem.

I'm open to troubleshooting suggestions.

Thanks.
Dave.















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

Sarah Alawami, owner of flying Blind. Visit my website ( http://flyingblind.us ) to read my story.

Windows 11 22H2 (x64) build 22621.963
NVDA Version: 2022.3.3

Microsoft 365 MSO (Version 2211 Build 16.0.15831.20098) 64-bit
David Mehler
 

Hello,

I got it, had to disable the addon but functionality is back.


Thanks.
Dave.

On 1/21/23, Tyler Spivey via groups.io <tspivey@...> wrote:
Try one of these:

First, check if that gesture is assigned to anything recognizable.
1. Press NVDA+1 to turn on input help.
2. Press grave accent. If the addon script has documentation it should
tell you what it does, and you can use the Input gestures dialog to
unbind it.
3. Press NVDA+1 to turn input help off again.
If pressing grave didn't tell you what it did, the script it wanted to
execute should still be in your log, so pop it up with NVDA, Tools, View
log and look near the end.

If that doesn't help, disable half your addons and see if the problem
goes away. If it does, you know it's one of those.

On 1/21/2023 1:45 PM, David Mehler wrote:
Hello,

I'm hoping someone can tell me why this is happening. I'm using the
latest NVDA and either it or an add-on is trapping my grave accent key
that's the key immediately to the left of the number 1 key on the top
row. Whenever I hit said key I get a beep, hit it again and I get a
higher-pitched beep. At first I thought this might be an issue with my
keyboard, older one wireless, might be going bad, so just to try
something I restarted NVDA with add-ons disabled and the grave accent
key started working again, restarted normally and the same problem.

I'm open to troubleshooting suggestions.

Thanks.
Dave.
Tyler Spivey
 

Try one of these:

First, check if that gesture is assigned to anything recognizable.
1. Press NVDA+1 to turn on input help.
2. Press grave accent. If the addon script has documentation it should tell you what it does, and you can use the Input gestures dialog to unbind it.
3. Press NVDA+1 to turn input help off again.
If pressing grave didn't tell you what it did, the script it wanted to execute should still be in your log, so pop it up with NVDA, Tools, View log and look near the end.

If that doesn't help, disable half your addons and see if the problem goes away. If it does, you know it's one of those.

On 1/21/2023 1:45 PM, David Mehler wrote:
Hello,
I'm hoping someone can tell me why this is happening. I'm using the
latest NVDA and either it or an add-on is trapping my grave accent key
that's the key immediately to the left of the number 1 key on the top
row. Whenever I hit said key I get a beep, hit it again and I get a
higher-pitched beep. At first I thought this might be an issue with my
keyboard, older one wireless, might be going bad, so just to try
something I restarted NVDA with add-ons disabled and the grave accent
key started working again, restarted normally and the same problem.
I'm open to troubleshooting suggestions.
Thanks.
Dave.
Gene
 

You may have to disable one add-on at a time, restart NVDA, and see which add-on is causing the problem.

Of course, someone else may have the same problem and may tell you which add-on that person found to cause the problem so you may want to wait, but aside from that, disabling one add-on at a time is my suggestion.

Gene

On 1/21/2023 3:45 PM, David Mehler wrote:
Hello,

I'm hoping someone can tell me why this is happening. I'm using the
latest NVDA and either it or an add-on is trapping my grave accent key
that's the key immediately to the left of the number 1 key on the top
row. Whenever I hit said key I get a beep, hit it again and I get a
higher-pitched beep. At first I thought this might be an issue with my
keyboard, older one wireless, might be going bad, so just to try
something I restarted NVDA with add-ons disabled and the grave accent
key started working again, restarted normally and the same problem.

I'm open to troubleshooting suggestions.

Thanks.
Dave.
David Mehler
 

Hello,

I'm hoping someone can tell me why this is happening. I'm using the
latest NVDA and either it or an add-on is trapping my grave accent key
that's the key immediately to the left of the number 1 key on the top
row. Whenever I hit said key I get a beep, hit it again and I get a
higher-pitched beep. At first I thought this might be an issue with my
keyboard, older one wireless, might be going bad, so just to try
something I restarted NVDA with add-ons disabled and the grave accent
key started working again, restarted normally and the same problem.

I'm open to troubleshooting suggestions.

Thanks.
Dave.

1 - 13 of 13