Topics

Problem with NVDA while reading documents


Quentin Christensen
 

As is will be fine - we can skip the unnecessary bits :)

Re UI Automation, it's basically a different way for NVDA to get the information about where the focus is and what is happening in Word.  Not everything is available using UIA, although there are some things available that way which aren't available using traditional methods.  Unfortunately it's not something that we can "mix and match" to get everything - we have to use either all UIA or all traditional methods.

For now, for most users, we feel the original way still works best, but UIA is there either for people who want to try it (probably developers) or for those who need to access something only available using UIA.

Regards

Quentin.

On Fri, Feb 14, 2020 at 1:58 PM Vaibhav Bhandari <vaibhavbhandari2017@...> wrote:
Woops, sorry. It was Alt+tab. And for what it was reading, it was
reading the title of the document. When I pressed alt tab or windows+M
to go to the desktop, the speech would stop and it would go there but
if I pressed Shift or control then still it would not stop speaking. I
will mail the logue to the e-mail you suggested.
One more thing, when I started NVDA in debug mode, the problem
occurred after 15 to 20 minutes. The log is around 8000 characters
long so should I remove the dialogue of the unwanted speech during
those 15 minutes or send the log as it is?
Ralf, I looked at the UI automation option in the advanced settings
and it was not enabled. What does it actually do?

On 2/14/20, Quentin Christensen <quentin@...> wrote:
> Hi Vaibhav,
>
> Can you please give more information about what happened here.  I can't
> quite follow / replicate what you have done.  Firstly which program are you
> working in?  Initially I thought maybe Word, but SHIFT+TAB doesn't change
> documents in Word.  CONTROL+F6 will switch between open Word documents, or
> ALT+TAB will switch between open windows (from any program).
>
> You can use SHIFT+TAB in File Explorer to move from the file list to the
> folder list, which you might do if you want to move to another folder of
> documents?
>
> All of those things worked just fine in Windows 10 / Office 2016 / NVDA
> 2019.3 for me just now.
>
> Also you said NVDA kept talking, what was it saying?
>
> If you could email that information with a full copy of the log to
> info@... I can have a look for you.
>
> Regards
> Quentin.
>
> On Thu, Feb 13, 2020 at 11:02 PM Vaibhav Bhandari <
> vaibhavbhandari2017@...> wrote:
>
>> Hi all,
>> I am using the latest version of NVDA. Today, I was reading and doing
>> work in some documents but when suddenly I switched my documents by
>> pressing shift+tab, my nvda crashed. It was not reading the document
>> and no matter what I pressed it did not stop speaking. After
>> restarting it, the problem occurred again. This time I restarted NVDA
>> in debug mode and got the following message during that problem:
>> DEBUG - IAccessibleHandler.accessibleObjectFromEvent (13:02:41.398) -
>> MainThread (4820):
>> oleacc.AccessibleObjectFromEvent with window 1311748, objectID 109 and
>> childID 0: [WinError -2147467259] Unspecified error
>> This problem is continuously happening though fortunately not so
>> frequently. Can someone help me with this?
>>
>> --
>> Thanks/regards: Vaibhav Bhandari
>>
>>
>>
>>
>
> --
> Quentin Christensen
> Training and Support Manager
>
> NVDA 2019.3 rc2 now available for testing:
> https://www.nvaccess.org/post/nvda-2019-3rc2-now-available-for-testing/
>
> Web: www.nvaccess.org
> Training: https://www.nvaccess.org/shop/
> Certification: https://certification.nvaccess.org/
> User group: https://nvda.groups.io/g/nvda
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess <https://twitter.com/NVAccess>
>
>
>
>


--
Thanks/regards: Vaibhav Bhandari





--
Quentin Christensen
Training and Support Manager



Vaibhav Bhandari
 

Woops, sorry. It was Alt+tab. And for what it was reading, it was
reading the title of the document. When I pressed alt tab or windows+M
to go to the desktop, the speech would stop and it would go there but
if I pressed Shift or control then still it would not stop speaking. I
will mail the logue to the e-mail you suggested.
One more thing, when I started NVDA in debug mode, the problem
occurred after 15 to 20 minutes. The log is around 8000 characters
long so should I remove the dialogue of the unwanted speech during
those 15 minutes or send the log as it is?
Ralf, I looked at the UI automation option in the advanced settings
and it was not enabled. What does it actually do?

On 2/14/20, Quentin Christensen <quentin@...> wrote:
Hi Vaibhav,

Can you please give more information about what happened here. I can't
quite follow / replicate what you have done. Firstly which program are you
working in? Initially I thought maybe Word, but SHIFT+TAB doesn't change
documents in Word. CONTROL+F6 will switch between open Word documents, or
ALT+TAB will switch between open windows (from any program).

You can use SHIFT+TAB in File Explorer to move from the file list to the
folder list, which you might do if you want to move to another folder of
documents?

All of those things worked just fine in Windows 10 / Office 2016 / NVDA
2019.3 for me just now.

Also you said NVDA kept talking, what was it saying?

If you could email that information with a full copy of the log to
info@... I can have a look for you.

Regards
Quentin.

On Thu, Feb 13, 2020 at 11:02 PM Vaibhav Bhandari <
vaibhavbhandari2017@...> wrote:

Hi all,
I am using the latest version of NVDA. Today, I was reading and doing
work in some documents but when suddenly I switched my documents by
pressing shift+tab, my nvda crashed. It was not reading the document
and no matter what I pressed it did not stop speaking. After
restarting it, the problem occurred again. This time I restarted NVDA
in debug mode and got the following message during that problem:
DEBUG - IAccessibleHandler.accessibleObjectFromEvent (13:02:41.398) -
MainThread (4820):
oleacc.AccessibleObjectFromEvent with window 1311748, objectID 109 and
childID 0: [WinError -2147467259] Unspecified error
This problem is continuously happening though fortunately not so
frequently. Can someone help me with this?

--
Thanks/regards: Vaibhav Bhandari



--
Quentin Christensen
Training and Support Manager

NVDA 2019.3 rc2 now available for testing:
https://www.nvaccess.org/post/nvda-2019-3rc2-now-available-for-testing/

Web: www.nvaccess.org
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>



--
Thanks/regards: Vaibhav Bhandari


Quentin Christensen
 

Hi Vaibhav,

Can you please give more information about what happened here.  I can't quite follow / replicate what you have done.  Firstly which program are you working in?  Initially I thought maybe Word, but SHIFT+TAB doesn't change documents in Word.  CONTROL+F6 will switch between open Word documents, or ALT+TAB will switch between open windows (from any program).

You can use SHIFT+TAB in File Explorer to move from the file list to the folder list, which you might do if you want to move to another folder of documents?

All of those things worked just fine in Windows 10 / Office 2016 / NVDA 2019.3 for me just now.

Also you said NVDA kept talking, what was it saying?

If you could email that information with a full copy of the log to info@... I can have a look for you.

Regards
Quentin.

On Thu, Feb 13, 2020 at 11:02 PM Vaibhav Bhandari <vaibhavbhandari2017@...> wrote:
Hi all,
I am using the latest version of NVDA. Today, I was reading and doing
work in some documents but when suddenly I switched my documents by
pressing shift+tab, my nvda crashed. It was not reading the document
and no matter what I pressed it did not stop speaking. After
restarting it, the problem occurred again. This time I restarted NVDA
in debug mode and got the following message during that problem:
DEBUG - IAccessibleHandler.accessibleObjectFromEvent (13:02:41.398) -
MainThread (4820):
oleacc.AccessibleObjectFromEvent with window 1311748, objectID 109 and
childID 0: [WinError -2147467259] Unspecified error
This problem is continuously happening though fortunately not so
frequently. Can someone help me with this?

--
Thanks/regards: Vaibhav Bhandari





--
Quentin Christensen
Training and Support Manager



Ralf Kefferpuetz
 

Hello,
Make sure ! Use UI Automation to access Microsoft Word document controls when available" is not checked in the advanced settings of NVDA.

Regards,
Ralf

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Vaibhav Bhandari
Sent: Donnerstag, 13. Februar 2020 13:02
To: nvda <nvda@nvda.groups.io>
Subject: [nvda] Problem with NVDA while reading documents

Hi all,
I am using the latest version of NVDA. Today, I was reading and doing work in some documents but when suddenly I switched my documents by pressing shift+tab, my nvda crashed. It was not reading the document and no matter what I pressed it did not stop speaking. After restarting it, the problem occurred again. This time I restarted NVDA in debug mode and got the following message during that problem:
DEBUG - IAccessibleHandler.accessibleObjectFromEvent (13:02:41.398) - MainThread (4820):
oleacc.AccessibleObjectFromEvent with window 1311748, objectID 109 and childID 0: [WinError -2147467259] Unspecified error This problem is continuously happening though fortunately not so frequently. Can someone help me with this?

--
Thanks/regards: Vaibhav Bhandari


Vaibhav Bhandari
 

Hi all,
I am using the latest version of NVDA. Today, I was reading and doing
work in some documents but when suddenly I switched my documents by
pressing shift+tab, my nvda crashed. It was not reading the document
and no matter what I pressed it did not stop speaking. After
restarting it, the problem occurred again. This time I restarted NVDA
in debug mode and got the following message during that problem:
DEBUG - IAccessibleHandler.accessibleObjectFromEvent (13:02:41.398) -
MainThread (4820):
oleacc.AccessibleObjectFromEvent with window 1311748, objectID 109 and
childID 0: [WinError -2147467259] Unspecified error
This problem is continuously happening though fortunately not so
frequently. Can someone help me with this?

--
Thanks/regards: Vaibhav Bhandari