Comment 1 by mohammadobid on 2015-07-16 11:10
Oh, I forget something,
I also use nvda version: next-12289,171a430

Comment 2 by briang1 on 2015-07-16 16:29
I don't use Windows 10, its true, but this problem existed for me in Windows 7, and I eventually traced it to an inappropriate idle setting of the processor. I made its idle mode run faster by quite a lot, ie 5 percent to 50 percent and the lag vanished.
I'd imagine a portable machine might do this sort of thing to conserve battery power, and its not obvious that its been set like that till you go and look at the settings and trigger levels etc in the control panel.

Comment 3 by jteh on 2015-07-30 04:01
Is this fixed in the current "next" snapshot? beb693f should have at least improved this.

Comment 4 by jteh on 2015-08-06 00:29
It is somewhat faster on my system, but it does get sluggish when running on battery. From what I can see, Explorer's accessibility implementation is just sluggish in general now. Do you see the same kind of lag when using Explorer with Narrator?

Comment 5 by tyrylu on 2015-08-06 10:07
It's somewhat hard to tell, because of the Narrator's speech level (the selected state announcement is really not something relevant for testing this), but even with it it's probably a little bit sluggish. It's sad to hear the bad news about the accessibility implementation performance on Microsoft's part.

Comment 6 by James Teh <jamie@... on 2015-08-11 06:11
In [020e3f6]:

UIAHandler.getNearestWindowHandle: Cache the result and use the cache for any future call. This yields a noticeable performance improvement in Windows 10 Task View and File Explorer.

Re #5229.

Comment 7 by James Teh <jamie@... on 2015-08-11 06:55
In [8fc7574]:

UIA NVDAObject parent property: If neither self nor parent have a window handle themselves, their nearest window handle will be the same, so cache this on the parent. Slight performance improvement in Windows 10 File Explorer.

Re #5229.

Comment 8 by Michael Curran <mick@... on 2015-08-12 00:36
In [caf154c]:

Catch AttributeError when fetching the nearestWindowHandle cache from a UIA object onto its parent. This may not exist on self if self was instantiated  given a specific windowhandle. Re #5229. Fixes regression in 8fc7574

Comment 9 by mayson on 2015-08-12 18:17
its getting a little better. its not as bad as it was befor, still just a little bit sluggish. its a slightly bit better

Comment 11 by mdcurran on 2015-10-21 23:57
Major performance improvements were made to UI Automation in Windows 10 update KB3093266 (cumulative update for September 30 2015). This may improve navigating in File Explorer a little. It should certainly stop any performance decrease over time.

As per previous comments, we believe this issue to be fixed now.