Hi Paul

Yes, for technical details, this can be discussed:
1. In the GitHub issue, best place in my opinion
2. On the nvda-devel mailing list
3. On another technical list, e.g. the French NVDA script list if you prefer continue in French.
4. Privately if needed; worst place in my opinion, but you may have any good reason to do it.

Cheers,

Cyrille


On Thu, Jun 30, 2022 at 01:53 AM, bering.p wrote:

Hi.
OK, maybe it's better to discuss this on the scriptNVDA list?
Best regards.
Paul.

Le 30/06/2022 09:39, Cyrille via groups.io a écrit :

Hi Paul

Yes, if you have investigated the root cause of the issue, that may be valuable to describe it in the ticket, except if the log makes it already obvious.
You may also describe the work-around you have used in your add-on to solve it; it may be a source of inspiration for someone wanting to implement a pull-request to fix the issue. But beware that NVAccess will probably want to fix the root cause of the issue if possible. Thus, if this solution is a workaround that does not solve the root cause, they may not accept it in a PR.

Cheers,

Cyrille

On Wed, Jun 29, 2022 at 02:06 PM, bering.p wrote:

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.