Open lukaszgo1 opened 2 years ago
@cary-rowen Would you be able to confirm that disabling "Handle keys from other applications" makes it possible to move caret to the position of the review cursor in bookworm?
yes i can confirm this.
Also, as you said in #13420, Say all needs to be improved.
@lukaszgo1 Can you still reproduce this with Wordpad in current alpha versions? Note that in NVDA itself, we forcefully disable UIA.
Hi @leonardder
"Handle keys from other applications" is checked.
Excitingly, I can no longer reproduce this in WordPad and Bookworm using NVDA-alpha-28931,186a8d70. But still reproducible in NVDA's log viewer.
Thanks
I'm afraid we can not use UIA in NVDA's log viewer. That said, we could more safely consider disabling ITextDocument2 by default for the log viewer.
Can we assume that #15314 has fixed (or partially fixed) this issue?
Initially described in issue #13420
Steps to reproduce:
Actual behavior:
When Handle keys from other applications is enabled caret fails to move.
Expected behavior:
Caret should be moved to the review position regardless of the "Handle keys from other applications" being enabled or disabled.
NVDA logs, crash dumps and other attachments:
Log snipped with "Handle keys from other applications" enabled:
Notice the additional lines
Input: kb(desktop):NVDA+
which should not be there.Log snipped with "Handle keys from other applications" disabled:
System configuration
NVDA installed/portable/running from source:
Both installed and portable.
NVDA version:
Latest Alpha, 2022.2
Windows version:
Tested on Windows 7 but should not matter.
Name and version of other software in use when reproducing the issue:
Wordpad, NVDA's log viewer, QRead
Other information about your system:
None relevant
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.
The same issue occurs with 2019.2
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Haven't tried.