Open mehgcap opened 3 years ago
Would you mind testing an older version? You can run the 2021.2 release and then look in the log for the same error. It helps us a lot to know if the issue is introduced in this release.
Also please test with add-ons disabled.
I've confirmed this with 2021.2 and 2020.4
I haven't noticed any effects as a user
Thanks for confirming with older versions.
I just tested this in the beta with add-ons disabled, and got the same result.
In case this helps, the error does not happen when I use ctrl-p to open a file that is already open in my workspace. Also, the error does not happen when I press ctrl-n to open a new, blank file. However, once I save that new file, the error is encountered.
@mehgcap are you still having this issue with NVDA 2024.4.1?
Steps to reproduce:
Actual behavior:
When the new file opens, NVDA plays an error sound. The log contains the following:
Expected behavior:
No error should be produced.
System configuration
NVDA installed/portable/running from source:
installed
NVDA version:
2021.3 beta 1
Windows version:
10
Name and version of other software in use when reproducing the issue:
VSCode 1.60.1
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.
To my knowledge, 2021.2 and earlier didn't do this, though as error sounds never play outside of betas, I may have just not noticed. This error doesn't impact usability, as far as I can tell, so I'd have had no reason to check the NVDA log when opening files.
If NVDA add-ons are disabled, is your problem still occurring?
not yet tested
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
yes