Hello,
I have been following NVDA's transition to python3 for a long time.
Meanwhile, I encountered a problem.
I do not know what kind of analysis I will present on this topic. But with the same settings, NVDA 2019.2 reacts faster.
When I move around the screen by pressing any letter, NVDA waits too long to speak.
I think there is an estimated 200 ms delay.
Steps to reproduce:
For example, let's imagine that we are navigating on the desktop
- Windows+M = Folder View, or another folder
Our sample items are:
- Recycle Bin
- Control Panel
- Firefox
- GitHub Desktop
- Google Chrome
Actual behavior:
- Let's navigate between the items here by pressing the first letters of the items.
Example: press g: google chrome, after press: github desktop
Result: Compared to the python 2 version of NVDA, 2019.3 seems to have a late response in letter navigation.
Expected behavior:
- fixing of the delay in letter navigation.
Unfortunately, I don't know what I can write more.
I can't explain this with logs and error reports :).
System configuration
NVDA installed/portable/running from source:
- sistem installed: tested
- portable: tested
- source: tested
- alpha versions: tested
NVDA version:
Problem: 2019.3
Windows version:
windows 1903, 64bit, 18358.1
Name and version of other software in use when reproducing the issue:
IBMTTS: IBMTTS driver; Status: Enabled; Version: 19.8B4; Author: David CM dhf360@gmail.com and others
I tested it with other synthesizers. No problem is accuring.
Other information about your system:
There is an SSD.
No problem from CPU, RAM and SSD.
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.
2019.2: non-problem. speed response
If addons are disabled, is your problem still occuring?
yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?
yes
Notes!
There may be places I am confused about English. My main language is not English.
Please pay attention to plain writing when answering me. Sometimes I can't understand you. Because technical problem.
I can write other information if you want. Maybe there may be something I forgot.
And this problem is very frustrating.
I hope we can find a way to fix it.
Hello,
I have been following NVDA's transition to python3 for a long time.
Meanwhile, I encountered a problem.
I do not know what kind of analysis I will present on this topic. But with the same settings, NVDA 2019.2 reacts faster.
When I move around the screen by pressing any letter, NVDA waits too long to speak.
I think there is an estimated 200 ms delay.
Steps to reproduce:
For example, let's imagine that we are navigating on the desktop
Our sample items are:
Actual behavior:
Example: press g: google chrome, after press: github desktop
Result: Compared to the python 2 version of NVDA, 2019.3 seems to have a late response in letter navigation.
Expected behavior:
Unfortunately, I don't know what I can write more.
I can't explain this with logs and error reports :).
System configuration
NVDA installed/portable/running from source:
NVDA version:
Problem: 2019.3
Windows version:
windows 1903, 64bit, 18358.1
Name and version of other software in use when reproducing the issue:
IBMTTS: IBMTTS driver; Status: Enabled; Version: 19.8B4; Author: David CM dhf360@gmail.com and others
I tested it with other synthesizers. No problem is accuring.
Other information about your system:
There is an SSD.
No problem from CPU, RAM and SSD.
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.
2019.2: non-problem. speed response
If addons are disabled, is your problem still occuring?
yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?
yes
Notes!
There may be places I am confused about English. My main language is not English.
Please pay attention to plain writing when answering me. Sometimes I can't understand you. Because technical problem.
I can write other information if you want. Maybe there may be something I forgot.
And this problem is very frustrating.
I hope we can find a way to fix it.