Re: Strange phenomenon on Windows 10


Felix G.
 

Sure, here goes. This is the log excerpt of me alt+tabbing without any feedback, with debugging enabled:
Input: kb(desktop):alt+tab
IO - speech.speak (08:05:48.842):
Speaking [u'Explorer  Reihe 1  Spalte 2']
DEBUG - NVDAObjects.NVDAObject._get_placeholder (08:05:48.844):
Potential unimplemented child class: <NVDAObjects.Dynamic_MultitaskingViewFrameListItemListItemUIA object at 0x05255B10>
IO - braille.BrailleBuffer.update (08:05:48.845):
Braille regions text: [u'Explorer']
IO - braille.BrailleHandler.update (08:05:48.845):
Braille window dots: 157 1346 1234 123 135 1235 15 1235
IO - inputCore.InputManager.executeGesture (08:05:49.154):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:49.378):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:49.605):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:49.841):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:50.075):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:50.299):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:50.539):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:50.776):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:51.003):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:51.246):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:51.496):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:51.727):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:51.966):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:52.210):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:52.441):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:52.681):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:52.926):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:53.153):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:53.384):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:53.631):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:53.868):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:54.115):
Input: kb(desktop):alt+tab
IO - inputCore.InputManager.executeGesture (08:05:54.351):
Input: kb(desktop):alt+tab
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (08:05:54.711):
accRole failed: (-2147024809, 'Falscher Parameter.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (08:05:54.720):
accRole failed: (-2147024809, 'Falscher Parameter.', (None, None, None, 0, None))
IO - speech.speak (08:05:54.782):
Speaking [u'Letting Go (Pt. 2) - Liquid Mind - Google Play Musik - Mozilla Firefox']
IO - braille.BrailleBuffer.update (08:05:54.785):
Braille regions text: [u'Letting Go (Pt. 2) - Liquid Mind - Google Play Musik - Mozilla Firefox']
IO - braille.BrailleHandler.update (08:05:54.785):
Braille window dots: 1237 15 2345 2345 24 1345 1245 - 12457 135 - 236 12347 2345 3 - 126 356 - 36 - 1237 24 12345 136 24 145 - 1347 24 1345 145 - 36 - 12457 135 135 1245 123
IO - braille.BrailleBuffer.update (08:05:55.119):

As you can see, the first one works, the rest is silence.
All the best,
Felix

Adriani Botez <adriani.botez@...> schrieb am Di., 30. Jan. 2018 um 00:37 Uhr:

Hello,

 

could you post the content of the log file when encountering this issue? Ideally with debugging activated in NVDA’s preferences and general settings.

 

 

Best

Adriani

 

 

Von: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] Im Auftrag von Felix G.
Gesendet: Montag, 29. Januar 2018 19:26
An: nvda@nvda.groups.io
Betreff: [nvda] Strange phenomenon on Windows 10

 

Dear NVDA community,

from time to time on Windows 10 I encounter a strange cluster of symptoms of which I can't make head nor tail, so I thought I'd ask around if anyone else is noticing and may have an explanation for them.

It usually starts with some missing feedback. For instance, I launch a program, and a sighted friend confirms it has indeed launched and has gained focus, but NVDA keeps silent about it.

In that situation, if I decide to alt+tab around, usually the first tab will announce a window title, but subsequent tabs don't. Releasing the alt key often yields the title of the window to which I switched, but no information about the control that gained focus in the process.

Pressing NVDA+t to find out the window title will then usually yield "Explorer."

The tab key will indeed move focus from control to control but NVDA keeps blissfully unaware of it.
The situation often resolves itself after some patient waiting, but may in rare cases leave the system in an altered state until it is rebooted.

Does that ring a bell for anyone?

All the best,

Felix

Join nvda@nvda.groups.io to automatically receive all group messages.