nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows
https://www.nvaccess.org/
Other
2.11k stars 637 forks source link

Control key does not stop NVDA speech at first press #11401

Open CyrilleB79 opened 4 years ago

CyrilleB79 commented 4 years ago

Steps to reproduce:

Actual behavior:

The whole row is read once again after 'control' has been pressed. A second 'control' keystroke is needed to stop the speech.

Expected behavior:

'control' key should just interrupt the speech at first press.

Additional note

Same issue with the 'shift' keystroke instead of 'control'. First press reads the row again and second press finally pauses the speech.

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

2020.2rc1

Windows version:

Win 10 1809

Name and version of other software in use when reproducing the issue:

Outlook 2016

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

NVDA 2019.2.1 portable: same issue.

If addons are disabled, is your problem still occuring?

Yes

Did you try to run the COM registry fixing tool in NVDA menu / tools?

No

Adriani90 commented 4 years ago

cc: @leonardder

Brian1Gaff commented 4 years ago

Hmm, I've seen this on areas where it used to repeat lines, and suspect some code was written to stop it repeating but if you cancel speech the second version just suppressed is being seen and spoken somehow. At least that is what it looks like. Weird. Brian

bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field. Newsgroup monitored: alt.comp.blind-users

Adriani90 commented 5 months ago

@CyrilleB79 are you still having this issue with NVDA 2024.2 Beta?

CyrilleB79 commented 5 months ago

Not tested on NVDA 2024.2beta. But I have tested this still recently with NVDA 2024.1 and the issue was still present.

First investigation with Event Tracker showed that a double speech was occurring due to two distinct events.