Re: Logging how NVDA tracks focus


Felix G.
 

I agree! That's why I am searching for a way to log all events which could, in principle, mean that the focus has changed. Given such logging facilities, we could then compare the cases in which it works to those in which it doesn't.

Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> schrieb am Di., 6. Feb. 2018 um 14:18 Uhr:

Well without some idea of why things are being not seen, its very hard to be
specific, even back in the xp days some machines were more prone to the
problem without any kind of observable difference affecting anything else.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Felix G." <constantlyvariable@...>
To: <nvda@nvda.groups.io>
Sent: Monday, February 05, 2018 3:52 PM
Subject: Re: [nvda] Logging how NVDA tracks focus


> Hello Brian,
> thank you for the additional information. My original question was not
> touched upon here and therefore remains open.
> Best regards,
> Felix
>
> Brian's Mail list account via Groups.Io
> <bglists=blueyonder.co.uk@groups.io>
> schrieb am Mo., 5. Feb. 2018 um 16:43 Uhr:
>
>> Yess look at the log, often at least in the case of Firefox i see core
>> frozen in stack messages and this I think means that nvda is unable to
>> intercept the data it needs to tell what is going on.
>>
>> However a move away and back normally puts it back. In a way what nvda
>> needs
>> is to protect enough running resources to always allow it to run when
>> other
>> software momentarily gobbles up the computer processor time.This, I
>> suspect
>> needs to be sorted by Microsoft. jaws, I fancy has some kind of system
>> different to nnvda in this respect. Core frozen in stack has been with us
>> for ever.
>>  Brian
>>
>> bglists@...
>> Sent via blueyonder.
>> Please address personal email to:-
>> briang1@..., putting 'Brian Gaff'
>> in the display name field.
>> ----- Original Message -----
>> From: "Felix G." <constantlyvariable@...>
>> To: <nvda@nvda.groups.io>
>> Sent: Monday, February 05, 2018 1:56 PM
>> Subject: [nvda] Logging how NVDA tracks focus
>>
>>
>> > Hello,
>> > I am currently searching for clues why NVDA sometimes fails to track
>> > focus.
>> > Remember those moments when you launch a program, a window opens but
>> > NVDA
>> > doesn't announce it, even insisting you are still on the desktop when
>> > you
>> > ask it via NVDA+t? Or those times when it just says "Mozilla Firefox,"
>> > ignoring that focus has long since moved on to the address bar? The
>> common
>> > denominator of all these scenarios is this: NVDA has lost track of the
>> > focus, believing it where it once was rather than where it is now.
>> > The proof can be found by pressing NVDA+f1 in those cases, requesting
>> > technical information about the current navigator object. If we assume
>> > NVDA
>> > is configured so that the navigator object follows focus, this
>> > technical
>> > information should always indicate that the object in question indeed
>> > has
>> > focus. And in most cases it does. Just not in those special cases I'm
>> > trying to hunt down. In those instances, I am always rewarded with the
>> > line:
>> > hasFocus: False
>> > So, even though the navigator object has been set up to follow the
>> > focus,
>> > it has somehow ended up on an object which doesn't have focus. Or to
>> > put
>> > this differently: Focus has moved on, leaving the navigator object
>> > trailing
>> > behind like a shadow at sunset.
>> > Which makes me wonder: Is there a way to log how NVDA tracks focus? In
>> > other words, is there a way to tell NVDA to log each incoming event
>> > which
>> > makes it think the focus has changed, and also where it thinks it went?
>> > The
>> > time has come that we once and for all find out where things go wrong.
>> > Is
>> > it a UIA event that never arrives? One which arrives but has wrong
>> > parameters? One which arrives but is incorrectly interpreted?
>> > I tried setting the log level to debug but in the resulting logs I saw
>> > nothing pertaining to focus events. That's why I'm asking.
>> > All the best,
>> > Felix
>> >
>>
>>
>>
>>
>>
>




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