Thank you Tyler. That's an answer that makes sense to me.
toggle quoted messageShow quoted text
"This might break reading of background progress bars, but that's a small
price to pay for a working system."
I'd be ok with that, a small price as you say.
People with System Access seem to be fine as well.
On 9/2/2018 1:19 PM, Tyler Spivey wrote:
The fault lies with both Microsoft and NVDA.
As far as I understand it, here's the issue. With UIA, you can tell it
which events you want to be notified about, and for which windows.
NVDA decided that it was going to listen to certain events from every
window on the system, and not just the one that had the focus. That
doesn't sound too bad, until...
If another application on the system isn't responding fast enough, UIA
stops notifying NVDA of events if NVDA is listening to certain
properties of that window (I think it was name and value change).
I'll lay out a simple, real-world example:
1. I start uploading a file in WinSCP.
2. I switch away from WinSCP into File Explorer. I guess WinSCP doesn't
respond fast enough to UIA, so UIA decides not to send NVDA events for
anything anymore. From then on, until that upload finishes or I close
WinSCP, my File Explorer won't read properly, nor will alt+tab or
anything else that depends on UIA.
This particular example isn't as bad as I thought, but my UIA does stop
responding for a few seconds at a time, and it's definitely noticeable.
I've heard that the next version of Windows 10 tries to fix this.
However, if NVDA simply listened to events from the currently running
application, I think this would be a much less severe problem.
This might break reading of background progress bars, but that's a small
price to pay for a working system.
Also, JAWS and Narrator don't have this problem, only NVDA.
For more info, see issue 8535 and its linked issues:
On 9/2/2018 12:57 PM, Richard Bartholomew wrote:
Firstly, no, JAWS doesn’t suffer from the same problem.
Secondly, though,I don’t find this slowness either with NVDA – I don’t
use NVDA constantly so maybe it is only after it has been running for a
long time that the problem arises. However, I’ve just spent 15 minutes
going through my various drives and folders with absolutely no slow down
at all – one of the folders had in excess of 1,000 subfolders and it was
as quick as one which only had one or two in it!
The only other thing I can think of is that, possibly, it may be an
add-on which is causing this? The reason I put this out is that I have
very, very few add-ons installed!
Good luck with identifying where the problem is and on fixing it.
Oh yes, and I’m using the latest version of Windows 10 64-bit along with
the latest stable version of NVDA.
*From:*firstname.lastname@example.org <email@example.com> *On Behalf Of *Gene
*Sent:* 02 September 2018 20:25
*Subject:* Re: [nvda] Windows 10 1803 and file explorer sluggishness
Others who use Windows 10 will telll you more and we will see if my
memory is correct. As I recall, this is the result of UIA, a system
used much more in Windows 10 to communicate with screen-readers. I
don't think you can do anything about it, as I recall what I've seen
discussed here, though I may have found a partial work around. I don't
use Windows 10 so you can see. I'll explain it after the rest of my
general comments. I wonder if JAWS has the same problem. Others who
know more technically may comment on whether this is a Microsoft problem
or if it will take both Microsoft and NVDA developers to solve it.
I'm giving desktop layout commands:
Move into the folder where you want to find a file. Instead of down
arrowing, move through each item as though it were its own object, which
it is. The command to move by object down the screen is numpad insert
numpad 6. Keep holding insert and pressing six to move through the
list. To move back, the command is numpad insert numpad 4. When you
want to open something, it will not be selected. use the command numpad
insert numpad enter. Execute the command twice, once to select the
item, once to open it. You are doing what a mouse user does when he/she
double clicks an item. You aren't using a mouse but you are first
selecting, then taking an action, in this case opening it, which is the
same sequence a mouse user follows.
----- Original Message -----
*Sent:*Sunday, September 02, 2018 1:02 PM
*Subject:*[nvda] Windows 10 1803 and file explorer sluggishness
Since asking this on the Windows 10 list, it was also suggested that I
ask more NVDA users here, so am copying below the message I sent to the
other list with an additional NVDA question.
First of all, I'm still getting used to the idea that File Explore now
uses ribbons rather than the menus on my former Windows 7 installation.
What's bothering me more is the sluggishness when moving around through
files and folders. There seems to be between a quarter and a half second
delay after each press of the arrow and enter keys. Same with the
First question: is there a way to toggle between folders and ribbons, or
am I stuck? I'm guessing the answer to be stuck.
Next, is there a way to speed up movement through navigating files and
folders? As far as I can tell, I have all visuals and animations turned
off. The sluggishness remains, and increases over time. Starting and
stopping the "Windows Explorer" process in Task Manager seems to make
things less slow, but still not normal for a few minutes, then things
get more and more sluggish again.
In addition, is there anything in NVDA that I can check to see if it
would help in the new sluggishness? I just miss the snappiness I had in
If anyone knows what I can do, I'd appreciate it. Thanks.