Re: Intermittent lack of feedback in Windows Explorer

Felix G.

no, the issue cannot be described in terms of delays. When feedback fails to occur, it will then simply not occur no matter how long I would wait. It is genuinely different behavior rather than just slowed down normal behavior.

Brian's Mail list account via Groups.Io <> schrieb am Do., 2. Aug. 2018 um 10:55 Uhr:

When cursoring up and down, does the selcted item  get said after a delay,
and if so and you hear that, can you then select the file?

I had this with explorer both on windows 7 and 10, and it was the processor
in the  computer actually not running at full speed. It seems on many
laptops the processor is slow to catch up with demand and hence the actual
selection is behind the  one you think it is on, or worse, on nothing at
 I'm sure somebody else will respond but I had to go digging into advanced
power management and crank up the idle speed to at least 50 percent, it was
set at 10 percent, before acceptable results occurred.
 Of course it could be something else, but this was the reason I found for
most of it. I would have thought that as nvda is hogging one core and hence
stopping the machine using it, Windows ought to sense it and up the speed of
the cores. It seems that this only happens sometimes when more than one core
is maxed out. I guess this might be because nvda is a 32 bit app, not a 64
bit one with  the ability to  push threads though different processor cores.
I'd welcome some more knowledgeable people to comment.

Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Felix G." <constantlyvariable@...>
To: <>
Sent: Thursday, August 02, 2018 8:46 AM
Subject: [nvda] Intermittent lack of feedback in Windows Explorer

> Hello,
> I'd like to ask around if anyone else has noticed this disturbing trend:
> When pressing enter on a folder in Windows Explorer, NVDA usually
> announces
> "element view list" followed by the name of the first element in that
> folder. Often, however, NVDA remains silent. Requesting developer info for
> the navigator object then yields something like the log excerpt I am
> posting below.
> Any ideas how I could make this behave? Being a child of the age of DOS,
> when there is silence I usually wait because I assume my command takes
> longer to complete. I know I'm pedantic, but then this is software and
> not,
> say, astrology.
> Here is that log excerpt now:
> name: ''
> states: exception: (-2147220991, 'Ein Ereignis konnte keinen Abonnenten
> aufrufen.', (None, None, None, 0, None))
> isFocusable: exception: (-2147220991, 'Ein Ereignis konnte keinen
> Abonnenten aufrufen.', (None, None, None, 0, None))
> hasFocus: False
> Python object: <NVDAObjects.Dynamic_UIItemListItemUIA object at
> 0x05B786D0>
> Python class mro: (<class 'NVDAObjects.Dynamic_UIItemListItemUIA'>, <class
> 'NVDAObjects.UIA.UIItem'>, <class 'NVDAObjects.UIA.ListItem'>, <class
> 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class
> 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>,
> <class 'baseObject.ScriptableObject'>, <class
> 'baseObject.AutoPropertyObject'>, <type 'object'>)
> description: ''
> location: None
> value: ''
> appModule: <'explorer' (appName u'explorer', process ID 1492) at address
> 5a151f0>
> appModule.productName: u'Betriebssystem Microsoft\xae Windows\xae'
> appModule.productVersion: u'6.1.7600.16385'
> TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
> windowHandle: 264856
> windowClassName: u'DirectUIHWND'
> windowControlID: 0
> windowStyle: 0
> windowThreadID: 0
> windowText: u''
> displayText: exception: 'NoneType' object is not iterable
> UIAElement: <POINTER(IUIAutomationElement) ptr=0x42cc2e8 at 5c5be40>
> UIA automationID: Exception: (-2147220991, 'Ein Ereignis konnte keinen
> Abonnenten aufrufen.', (None, None, None, 0, None))
> UIA frameworkID: DirectUI
> UIA runtimeID: (1492, 217953568, 0)
> UIA providerDescription: [pid:1492,hwnd:0x0 Main(parent link):Unidentified
> Provider (unmanaged:EXPLORERFRAME.dll)]
> UIA className: Exception: (-2147220991, 'Ein Ereignis konnte keinen
> Abonnenten aufrufen.', (None, None, None, 0, None))
> UIA patterns available:
> All the best,
> Felix

Join to automatically receive all group messages.