Date   

Thunderbird and trash

Adriano Barbieri
 

Hi to every body,


Version 60.5.1,

I'm forced to compact / empty the basket every 4 or 5 messages deleted, otherwise Thunderbird does not delete others.It only happens to me?

What can be done to solve?

Thanks!


Regards

Adriano


Re: Problem with windows10 OCR and NVDA

 

Good question, I would ask the same.
Em 25/02/2019 10:44, Gene escreveu:

does that mean that the NVDA OCR feature only can recognize a single screen or can it recognize an entire document?  I haven't played with this to any extent.  In Notepad. if you open a document, it is all one single object and can all be read with the screen review keys so you aren't limited to one screen when in object review.  What about a document you use the OCR feature on? 
 
Gene
----- Original Message -----
Sent: Monday, February 25, 2019 7:13 AM
Subject: Re: [nvda] Problem with windows10 OCR and NVDA

It seems the keys to perform such a command using the laptop layout are NVDA+Shift+up arrow.
I found it by going to the keystrokes reference.

By the way, Rui, thanks for the clarification :)
I'll play with it taking this advice into account and see what I can get.
Em 25/02/2019 09:50, Nevzat Adil escreveu:
"If you want to perform the OCR to  all the window, you will need to
move the navegation object to the window itself, pressing
NVDA+NumPad8..."

How does this apply if using a laptop instead of desktop?

On 2/25/19, Rui Fontes <rui.fontes@...> wrote:
Hello!

Please, remember one thing...

When you perform the OCR, using NVDA in Windows 10, pressing NVDA+R, the
OCR is applied only to the object focused by NVDA...

By instance, if you are in a dialog type, "save as" and focused in the
Save button, the OCR result will be only "Save", the text of the focused
object, the Save button.
If you want to perform the OCR to  all the window, you will need to move
the navegation object to the window itself, pressing NVDA+NumPad8...

Regards,

Rui Fontes


Às 11:54 de 25/02/2019, marcio via Groups.Io escreveu:
Just adding
While with this message opened I tried to OCR just for fun, seeing what
I would get.
What a surprise, the OCR worked just like a charm.
Weird!

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 08:48, marcio via Groups.Io escreveu:
Very same here!
And I'm also using the latest NVDA Alpha with Win 10 1803.
Well I'm not using the latest at all because I need to update to the
very latest so to speak which showed up just now. I'll do it sometime
later, I guess.
However, the message I get is absolutely the same and no, I don't
think just updating to the latest Alpha will fix it since aparently
the folks on the NVDA dev side weren't aware of it.
Let's wait...

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 08:31, Mallard escreveu:
Yes, here too. Something must be broken, because I've opened a pdf
that is perfectly visible with any pdf reading apps, including Edge.

I tried opening with Sumatra pdf, which only shows the image and not
the text. Usually, when I do that, I can view the page with Inw10
OCR. Now it keeps saying


"Content not visible" (contenuto non visibile in Italian).


No idea what could have happened.

I'm using the latest Alpha of NVDA and Windows 10 1803.


Ciao,

Ollie




Il 25/02/2019 11:57, marcio via Groups.Io ha scritto:
Same here. I don't have Jaws to test with, though, so don't know if
it would be different.
Anyone to help us? :)

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 06:15, Aravind R escreveu:
Dear friends,

I am trying to do OCR with pdf using NVDA+r in windows10.
Wherever i try, it is saying "Recognising result document" but
nothing
is displayed and its working well with jaws's built-in ocr.
Kindly guide where changes to be made to make work with windows10 OCR




Re: Problem with windows10 OCR and NVDA

Gene
 

does that mean that the NVDA OCR feature only can recognize a single screen or can it recognize an entire document?  I haven't played with this to any extent.  In Notepad. if you open a document, it is all one single object and can all be read with the screen review keys so you aren't limited to one screen when in object review.  What about a document you use the OCR feature on? 
 
Gene

----- Original Message -----
Sent: Monday, February 25, 2019 7:13 AM
Subject: Re: [nvda] Problem with windows10 OCR and NVDA

It seems the keys to perform such a command using the laptop layout are NVDA+Shift+up arrow.
I found it by going to the keystrokes reference.

By the way, Rui, thanks for the clarification :)
I'll play with it taking this advice into account and see what I can get.
Em 25/02/2019 09:50, Nevzat Adil escreveu:
"If you want to perform the OCR to  all the window, you will need to
move the navegation object to the window itself, pressing
NVDA+NumPad8..."

How does this apply if using a laptop instead of desktop?

On 2/25/19, Rui Fontes <rui.fontes@...> wrote:
Hello!

Please, remember one thing...

When you perform the OCR, using NVDA in Windows 10, pressing NVDA+R, the
OCR is applied only to the object focused by NVDA...

By instance, if you are in a dialog type, "save as" and focused in the
Save button, the OCR result will be only "Save", the text of the focused
object, the Save button.
If you want to perform the OCR to  all the window, you will need to move
the navegation object to the window itself, pressing NVDA+NumPad8...

Regards,

Rui Fontes


Às 11:54 de 25/02/2019, marcio via Groups.Io escreveu:
Just adding
While with this message opened I tried to OCR just for fun, seeing what
I would get.
What a surprise, the OCR worked just like a charm.
Weird!

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 08:48, marcio via Groups.Io escreveu:
Very same here!
And I'm also using the latest NVDA Alpha with Win 10 1803.
Well I'm not using the latest at all because I need to update to the
very latest so to speak which showed up just now. I'll do it sometime
later, I guess.
However, the message I get is absolutely the same and no, I don't
think just updating to the latest Alpha will fix it since aparently
the folks on the NVDA dev side weren't aware of it.
Let's wait...

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 08:31, Mallard escreveu:
Yes, here too. Something must be broken, because I've opened a pdf
that is perfectly visible with any pdf reading apps, including Edge.

I tried opening with Sumatra pdf, which only shows the image and not
the text. Usually, when I do that, I can view the page with Inw10
OCR. Now it keeps saying


"Content not visible" (contenuto non visibile in Italian).


No idea what could have happened.

I'm using the latest Alpha of NVDA and Windows 10 1803.


Ciao,

Ollie




Il 25/02/2019 11:57, marcio via Groups.Io ha scritto:
Same here. I don't have Jaws to test with, though, so don't know if
it would be different.
Anyone to help us? :)

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 06:15, Aravind R escreveu:
Dear friends,

I am trying to do OCR with pdf using NVDA+r in windows10.
Wherever i try, it is saying "Recognising result document" but
nothing
is displayed and its working well with jaws's built-in ocr.
Kindly guide where changes to be made to make work with windows10 OCR






Re: Problem with windows10 OCR and NVDA

 

It seems the keys to perform such a command using the laptop layout are NVDA+Shift+up arrow.
I found it by going to the keystrokes reference.

By the way, Rui, thanks for the clarification :)
I'll play with it taking this advice into account and see what I can get.
Em 25/02/2019 09:50, Nevzat Adil escreveu:

"If you want to perform the OCR to  all the window, you will need to
move the navegation object to the window itself, pressing
NVDA+NumPad8..."

How does this apply if using a laptop instead of desktop?

On 2/25/19, Rui Fontes <rui.fontes@...> wrote:
Hello!

Please, remember one thing...

When you perform the OCR, using NVDA in Windows 10, pressing NVDA+R, the
OCR is applied only to the object focused by NVDA...

By instance, if you are in a dialog type, "save as" and focused in the
Save button, the OCR result will be only "Save", the text of the focused
object, the Save button.
If you want to perform the OCR to  all the window, you will need to move
the navegation object to the window itself, pressing NVDA+NumPad8...

Regards,

Rui Fontes


Às 11:54 de 25/02/2019, marcio via Groups.Io escreveu:
Just adding
While with this message opened I tried to OCR just for fun, seeing what
I would get.
What a surprise, the OCR worked just like a charm.
Weird!

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 08:48, marcio via Groups.Io escreveu:
Very same here!
And I'm also using the latest NVDA Alpha with Win 10 1803.
Well I'm not using the latest at all because I need to update to the
very latest so to speak which showed up just now. I'll do it sometime
later, I guess.
However, the message I get is absolutely the same and no, I don't
think just updating to the latest Alpha will fix it since aparently
the folks on the NVDA dev side weren't aware of it.
Let's wait...

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 08:31, Mallard escreveu:
Yes, here too. Something must be broken, because I've opened a pdf
that is perfectly visible with any pdf reading apps, including Edge.

I tried opening with Sumatra pdf, which only shows the image and not
the text. Usually, when I do that, I can view the page with Inw10
OCR. Now it keeps saying


"Content not visible" (contenuto non visibile in Italian).


No idea what could have happened.

I'm using the latest Alpha of NVDA and Windows 10 1803.


Ciao,

Ollie




Il 25/02/2019 11:57, marcio via Groups.Io ha scritto:
Same here. I don't have Jaws to test with, though, so don't know if
it would be different.
Anyone to help us? :)

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 06:15, Aravind R escreveu:
Dear friends,

I am trying to do OCR with pdf using NVDA+r in windows10.
Wherever i try, it is saying "Recognising result document" but
nothing
is displayed and its working well with jaws's built-in ocr.
Kindly guide where changes to be made to make work with windows10 OCR






          









Re: Problem with windows10 OCR and NVDA

Rui Fontes
 

NVDA+Shift+Up arrow.

Do you know you have an entry in NVDA, Help menu named Quick reference command guide, or something like that?

Rui Fontes


Às 12:50 de 25/02/2019, Nevzat Adil escreveu:

"If you want to perform the OCR to  all the window, you will need to
move the navegation object to the window itself, pressing
NVDA+NumPad8..."
How does this apply if using a laptop instead of desktop?
On 2/25/19, Rui Fontes <rui.fontes@tiflotecnia.com> wrote:
Hello!

Please, remember one thing...

When you perform the OCR, using NVDA in Windows 10, pressing NVDA+R, the
OCR is applied only to the object focused by NVDA...

By instance, if you are in a dialog type, "save as" and focused in the
Save button, the OCR result will be only "Save", the text of the focused
object, the Save button.
If you want to perform the OCR to all the window, you will need to move
the navegation object to the window itself, pressing NVDA+NumPad8...

Regards,

Rui Fontes


Às 11:54 de 25/02/2019, marcio via Groups.Io escreveu:
Just adding
While with this message opened I tried to OCR just for fun, seeing what
I would get.
What a surprise, the OCR worked just like a charm.
Weird!

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 08:48, marcio via Groups.Io escreveu:
Very same here!
And I'm also using the latest NVDA Alpha with Win 10 1803.
Well I'm not using the latest at all because I need to update to the
very latest so to speak which showed up just now. I'll do it sometime
later, I guess.
However, the message I get is absolutely the same and no, I don't
think just updating to the latest Alpha will fix it since aparently
the folks on the NVDA dev side weren't aware of it.
Let's wait...

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 08:31, Mallard escreveu:
Yes, here too. Something must be broken, because I've opened a pdf
that is perfectly visible with any pdf reading apps, including Edge.

I tried opening with Sumatra pdf, which only shows the image and not
the text. Usually, when I do that, I can view the page with Inw10
OCR. Now it keeps saying


"Content not visible" (contenuto non visibile in Italian).


No idea what could have happened.

I'm using the latest Alpha of NVDA and Windows 10 1803.


Ciao,

Ollie




Il 25/02/2019 11:57, marcio via Groups.Io ha scritto:
Same here. I don't have Jaws to test with, though, so don't know if
it would be different.
Anyone to help us? :)

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 06:15, Aravind R escreveu:
Dear friends,

I am trying to do OCR with pdf using NVDA+r in windows10.
Wherever i try, it is saying "Recognising result document" but
nothing
is displayed and its working well with jaws's built-in ocr.
Kindly guide where changes to be made to make work with windows10 OCR





Re: Having troubles to play with a website

 

Actually I had tried, but not knowing the right commands to apply. I should have tried after, though :)
Em 25/02/2019 09:47, Gene escreveu:

You should always try another browser when there is a problem.  That is one of the first things that should always be done.
 
Gene
----- Original Message -----
Sent: Monday, February 25, 2019 6:42 AM
Subject: Re: [nvda] Having troubles to play with a website

YAY! I tried it with Chrome and now it worked. Seems like the problem is with Firefox.
Man what a fantastic project! I'll try to contact this guy and make sure of congratulate him. If I ever could I'd buy this album. I loved it!

Em 25/02/2019 09:25, Gene escreveu:
Assuming you did it correctly and nothing played, that means you may have problems playing audio in future because the site appears to use HTML5 for audio.  Let us know if you have problems with other sites.  If you have another browser, using another one may play the audio.
 
Gene
----- Original Message -----
Sent: Monday, February 25, 2019 5:50 AM
Subject: Re: [nvda] Having troubles to play with a website

Hi George,
I'm using the laptop layout. And I just did it yesterday before giving up on this site. Nothing happened at all, so I really don't feel like trying it anymore :(
Em 25/02/2019 00:23, George McCoy escreveu:

Do you have nvda's keyboard layout  set to laptop?  if so, do the following:

Press b until you get to the button you want to click.

hold down the nvda and shift keys and press the letter m to route the mouse to the button.

Hold down the nvda key and press the left bracket key to click the button.


To see whether keyboard layout is set to laptop or desktop, do the following:

Press nvda plus n to open the nvda menu.

Press p to open preferences.

Press enter to open settings.

Press the letter k for keyboard.

Tab once and the keyboard layout setting will be spoken.

Press escape to exit the nvda menu.


Hth,

George


On 2/24/2019 3:47 PM, marcio via Groups.Io wrote:
Well I tried to use the said commands to make whatever there play, but still no luck.
As I am using a Dell laptop, I do:
Hit B until I hear play.
Press NVDA+SHIFT+BACKSPACE twice until hear play again.
Press NVDA+].
And that's it. Nothing happens :(

Em 24/02/2019 16:56, Brian Vogel escreveu:
Indeed, all of the following are true:

  1. You will not find the buttons for audio control on the https://golubovsky.bandcamp.com/album/unhuman-voices page except by using the B quick navigation shortcut
  2. Hitting spacebar or enter when you have gained focus on those buttons does nothing.
  3. Using NVDA+/ to route the PC mouse pointer to the NVDA navigator object, then using NumPad slash to activate it will make it play (or, if you're on the jump to next track or other audio control button do what that button does).
-- 

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 






Re: Problem with windows10 OCR and NVDA

Mallard
 

Gene,


I use the Windows 10 OCR, and the add-on was completely removed as soon as I updated to Win10 two years ago...


I use OCR to read image-only pdf's, but now it doesn't even read pdf's that have readable text in them. I tried them with Edge first, and they're read perfectly well. Usually I can read a whole screen using arrows, but now it just doesn't work.


Re: Problem with windows10 OCR and NVDA

 

"If you want to perform the OCR to  all the window, you will need to
move the navegation object to the window itself, pressing
NVDA+NumPad8..."

How does this apply if using a laptop instead of desktop?

On 2/25/19, Rui Fontes <rui.fontes@tiflotecnia.com> wrote:
Hello!

Please, remember one thing...

When you perform the OCR, using NVDA in Windows 10, pressing NVDA+R, the
OCR is applied only to the object focused by NVDA...

By instance, if you are in a dialog type, "save as" and focused in the
Save button, the OCR result will be only "Save", the text of the focused
object, the Save button.
If you want to perform the OCR to all the window, you will need to move
the navegation object to the window itself, pressing NVDA+NumPad8...

Regards,

Rui Fontes


Às 11:54 de 25/02/2019, marcio via Groups.Io escreveu:
Just adding
While with this message opened I tried to OCR just for fun, seeing what
I would get.
What a surprise, the OCR worked just like a charm.
Weird!

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 08:48, marcio via Groups.Io escreveu:
Very same here!
And I'm also using the latest NVDA Alpha with Win 10 1803.
Well I'm not using the latest at all because I need to update to the
very latest so to speak which showed up just now. I'll do it sometime
later, I guess.
However, the message I get is absolutely the same and no, I don't
think just updating to the latest Alpha will fix it since aparently
the folks on the NVDA dev side weren't aware of it.
Let's wait...

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 08:31, Mallard escreveu:
Yes, here too. Something must be broken, because I've opened a pdf
that is perfectly visible with any pdf reading apps, including Edge.

I tried opening with Sumatra pdf, which only shows the image and not
the text. Usually, when I do that, I can view the page with Inw10
OCR. Now it keeps saying


"Content not visible" (contenuto non visibile in Italian).


No idea what could have happened.

I'm using the latest Alpha of NVDA and Windows 10 1803.


Ciao,

Ollie




Il 25/02/2019 11:57, marcio via Groups.Io ha scritto:
Same here. I don't have Jaws to test with, though, so don't know if
it would be different.
Anyone to help us? :)

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 06:15, Aravind R escreveu:
Dear friends,

I am trying to do OCR with pdf using NVDA+r in windows10.
Wherever i try, it is saying "Recognising result document" but
nothing
is displayed and its working well with jaws's built-in ocr.
Kindly guide where changes to be made to make work with windows10 OCR





Re: Having troubles to play with a website

Gene
 

You should always try another browser when there is a problem.  That is one of the first things that should always be done.
 
Gene

----- Original Message -----
Sent: Monday, February 25, 2019 6:42 AM
Subject: Re: [nvda] Having troubles to play with a website

YAY! I tried it with Chrome and now it worked. Seems like the problem is with Firefox.
Man what a fantastic project! I'll try to contact this guy and make sure of congratulate him. If I ever could I'd buy this album. I loved it!

Em 25/02/2019 09:25, Gene escreveu:
Assuming you did it correctly and nothing played, that means you may have problems playing audio in future because the site appears to use HTML5 for audio.  Let us know if you have problems with other sites.  If you have another browser, using another one may play the audio.
 
Gene
----- Original Message -----
Sent: Monday, February 25, 2019 5:50 AM
Subject: Re: [nvda] Having troubles to play with a website

Hi George,
I'm using the laptop layout. And I just did it yesterday before giving up on this site. Nothing happened at all, so I really don't feel like trying it anymore :(
Em 25/02/2019 00:23, George McCoy escreveu:

Do you have nvda's keyboard layout  set to laptop?  if so, do the following:

Press b until you get to the button you want to click.

hold down the nvda and shift keys and press the letter m to route the mouse to the button.

Hold down the nvda key and press the left bracket key to click the button.


To see whether keyboard layout is set to laptop or desktop, do the following:

Press nvda plus n to open the nvda menu.

Press p to open preferences.

Press enter to open settings.

Press the letter k for keyboard.

Tab once and the keyboard layout setting will be spoken.

Press escape to exit the nvda menu.


Hth,

George


On 2/24/2019 3:47 PM, marcio via Groups.Io wrote:
Well I tried to use the said commands to make whatever there play, but still no luck.
As I am using a Dell laptop, I do:
Hit B until I hear play.
Press NVDA+SHIFT+BACKSPACE twice until hear play again.
Press NVDA+].
And that's it. Nothing happens :(

Em 24/02/2019 16:56, Brian Vogel escreveu:
Indeed, all of the following are true:

  1. You will not find the buttons for audio control on the https://golubovsky.bandcamp.com/album/unhuman-voices page except by using the B quick navigation shortcut
  2. Hitting spacebar or enter when you have gained focus on those buttons does nothing.
  3. Using NVDA+/ to route the PC mouse pointer to the NVDA navigator object, then using NumPad slash to activate it will make it play (or, if you're on the jump to next track or other audio control button do what that button does).
-- 

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 





Re: Having troubles to play with a website

 

YAY! I tried it with Chrome and now it worked. Seems like the problem is with Firefox.
Man what a fantastic project! I'll try to contact this guy and make sure of congratulate him. If I ever could I'd buy this album. I loved it!

Em 25/02/2019 09:25, Gene escreveu:

Assuming you did it correctly and nothing played, that means you may have problems playing audio in future because the site appears to use HTML5 for audio.  Let us know if you have problems with other sites.  If you have another browser, using another one may play the audio.
 
Gene
----- Original Message -----
Sent: Monday, February 25, 2019 5:50 AM
Subject: Re: [nvda] Having troubles to play with a website

Hi George,
I'm using the laptop layout. And I just did it yesterday before giving up on this site. Nothing happened at all, so I really don't feel like trying it anymore :(
Em 25/02/2019 00:23, George McCoy escreveu:

Do you have nvda's keyboard layout  set to laptop?  if so, do the following:

Press b until you get to the button you want to click.

hold down the nvda and shift keys and press the letter m to route the mouse to the button.

Hold down the nvda key and press the left bracket key to click the button.


To see whether keyboard layout is set to laptop or desktop, do the following:

Press nvda plus n to open the nvda menu.

Press p to open preferences.

Press enter to open settings.

Press the letter k for keyboard.

Tab once and the keyboard layout setting will be spoken.

Press escape to exit the nvda menu.


Hth,

George


On 2/24/2019 3:47 PM, marcio via Groups.Io wrote:
Well I tried to use the said commands to make whatever there play, but still no luck.
As I am using a Dell laptop, I do:
Hit B until I hear play.
Press NVDA+SHIFT+BACKSPACE twice until hear play again.
Press NVDA+].
And that's it. Nothing happens :(

Em 24/02/2019 16:56, Brian Vogel escreveu:
Indeed, all of the following are true:

  1. You will not find the buttons for audio control on the https://golubovsky.bandcamp.com/album/unhuman-voices page except by using the B quick navigation shortcut
  2. Hitting spacebar or enter when you have gained focus on those buttons does nothing.
  3. Using NVDA+/ to route the PC mouse pointer to the NVDA navigator object, then using NumPad slash to activate it will make it play (or, if you're on the jump to next track or other audio control button do what that button does).
-- 

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 





Re: Problem with windows10 OCR and NVDA

Rui Fontes
 

Hello!

Please, remember one thing...

When you perform the OCR, using NVDA in Windows 10, pressing NVDA+R, the OCR is applied only to the object focused by NVDA...

By instance, if you are in a dialog type, "save as" and focused in the Save button, the OCR result will be only "Save", the text of the focused object, the Save button.
If you want to perform the OCR to all the window, you will need to move the navegation object to the window itself, pressing NVDA+NumPad8...

Regards,

Rui Fontes


Às 11:54 de 25/02/2019, marcio via Groups.Io escreveu:

Just adding
While with this message opened I tried to OCR just for fun, seeing what I would get.
What a surprise, the OCR worked just like a charm.
Weird!
Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>
Em 25/02/2019 08:48, marcio via Groups.Io escreveu:
Very same here!
And I'm also using the latest NVDA Alpha with Win 10 1803.
Well I'm not using the latest at all because I need to update to the very latest so to speak which showed up just now. I'll do it sometime later, I guess.
However, the message I get is absolutely the same and no, I don't think just updating to the latest Alpha will fix it since aparently the folks on the NVDA dev side weren't aware of it.
Let's wait...

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 08:31, Mallard escreveu:
Yes, here too. Something must be broken, because I've opened a pdf that is perfectly visible with any pdf reading apps, including Edge.

I tried opening with Sumatra pdf, which only shows the image and not the text. Usually, when I do that, I can view the page with Inw10 OCR. Now it keeps saying


"Content not visible" (contenuto non visibile in Italian).


No idea what could have happened.

I'm using the latest Alpha of NVDA and Windows 10 1803.


Ciao,

Ollie




Il 25/02/2019 11:57, marcio via Groups.Io ha scritto:
Same here. I don't have Jaws to test with, though, so don't know if it would be different.
Anyone to help us? :)

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 06:15, Aravind R escreveu:
Dear friends,

I am trying to do OCR with pdf using NVDA+r in windows10.
Wherever i try, it is saying "Recognising result document" but nothing
is displayed and its working well with jaws's built-in ocr.
Kindly guide where changes to be made to make work with windows10 OCR



Re: Having troubles to play with a website

Gene
 

Assuming you did it correctly and nothing played, that means you may have problems playing audio in future because the site appears to use HTML5 for audio.  Let us know if you have problems with other sites.  If you have another browser, using another one may play the audio.
 
Gene

----- Original Message -----
Sent: Monday, February 25, 2019 5:50 AM
Subject: Re: [nvda] Having troubles to play with a website

Hi George,
I'm using the laptop layout. And I just did it yesterday before giving up on this site. Nothing happened at all, so I really don't feel like trying it anymore :(
Em 25/02/2019 00:23, George McCoy escreveu:

Do you have nvda's keyboard layout  set to laptop?  if so, do the following:

Press b until you get to the button you want to click.

hold down the nvda and shift keys and press the letter m to route the mouse to the button.

Hold down the nvda key and press the left bracket key to click the button.


To see whether keyboard layout is set to laptop or desktop, do the following:

Press nvda plus n to open the nvda menu.

Press p to open preferences.

Press enter to open settings.

Press the letter k for keyboard.

Tab once and the keyboard layout setting will be spoken.

Press escape to exit the nvda menu.


Hth,

George


On 2/24/2019 3:47 PM, marcio via Groups.Io wrote:
Well I tried to use the said commands to make whatever there play, but still no luck.
As I am using a Dell laptop, I do:
Hit B until I hear play.
Press NVDA+SHIFT+BACKSPACE twice until hear play again.
Press NVDA+].
And that's it. Nothing happens :(

Em 24/02/2019 16:56, Brian Vogel escreveu:
Indeed, all of the following are true:

  1. You will not find the buttons for audio control on the https://golubovsky.bandcamp.com/album/unhuman-voices page except by using the B quick navigation shortcut
  2. Hitting spacebar or enter when you have gained focus on those buttons does nothing.
  3. Using NVDA+/ to route the PC mouse pointer to the NVDA navigator object, then using NumPad slash to activate it will make it play (or, if you're on the jump to next track or other audio control button do what that button does).
-- 

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 




Re: Problem with windows10 OCR and NVDA

 

Using the built-in OCR.
Em 25/02/2019 09:22, Gene escreveu:

Are you using the add-on or the OCR built into NVDA for use in Windows 10?  I don't know what happens if you use the add-on but if you are, disable or remove it. 
 
Gene
----- Original Message -----
Sent: Monday, February 25, 2019 4:57 AM
Subject: Re: [nvda] Problem with windows10 OCR and NVDA

Same here. I don't have Jaws to test with, though, so don't know if it would be different.
Anyone to help us? :)
Em 25/02/2019 06:15, Aravind R escreveu:
Dear friends,

I am trying to do OCR with pdf using NVDA+r in windows10.
Wherever i try, it is saying "Recognising result document" but nothing
is displayed and its working well with jaws's built-in ocr.
Kindly guide where changes to be made to make work with windows10 OCR




Re: Problem with windows10 OCR and NVDA

Gene
 

Are you using the add-on or the OCR built into NVDA for use in Windows 10?  I don't know what happens if you use the add-on but if you are, disable or remove it. 
 
Gene

----- Original Message -----
Sent: Monday, February 25, 2019 4:57 AM
Subject: Re: [nvda] Problem with windows10 OCR and NVDA

Same here. I don't have Jaws to test with, though, so don't know if it would be different.
Anyone to help us? :)
Em 25/02/2019 06:15, Aravind R escreveu:
Dear friends,

I am trying to do OCR with pdf using NVDA+r in windows10.
Wherever i try, it is saying "Recognising result document" but nothing
is displayed and its working well with jaws's built-in ocr.
Kindly guide where changes to be made to make work with windows10 OCR



Re: Invisible Dropbox pop-ups

Gene
 

Has anyone looked through options in Dropbox to see if anything is available about not showing notifications or messages?  These are, presumably, shown in the system tray.  I almost never use DropBox, though I have it, and I usually don't have it running.  I don't know if I have the latest version.  But the first thing I would do is look through the options to see if anything is available.  I may check later today but it might be better if someone checks who uses it regularly, and knows they have the problem version.  Presumably, I either do or it would update if I leave it on.
 
Gene

----- Original Message -----
Sent: Monday, February 25, 2019 3:18 AM
Subject: Re: [nvda] Invisible Dropbox pop-ups

The whole thrust of it for us is that you can hear when new updates come in.
To try to schedule everything at the studio will cause our non tech folk a
problem
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Gene" <gsasner@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, February 24, 2019 3:45 PM
Subject: Re: [nvda] Invisible Dropbox pop-ups


Is there any reason to have it running constantly?  You can exit it and only
run it when you want to use it.

Gene
----- Original Message -----

From: James Scholes
Sent: Sunday, February 24, 2019 9:32 AM
To: nvda@groups.io
Subject: [nvda] Invisible Dropbox pop-ups


Hi all,

I'm running Dropbox v68.3.92.  Approximately every half an hour or so,
NVDA's focus is being moved to a Dropbox window which only seems to
contain a single, blank edit field.  The window doesn't seem to stay on
the screen, but focus isn't returned to where it was previously after it
disappears.  In fact, NVDA reports it as taking up a rectangle of 0
pixels, so I don't know if anything shows up visually on the screen at all.

As you can imagine, having to dismiss these boxes several times per day
is irritating.  Does anybody have a work-around?

Regards,

James Scholes
https://twitter.com/JamesScholes









Re: New addon: BrowserNav

 

Just saw this this morning, but, list moderators, you know you can integrate an RSS feed to post to this group when there is new content, right? So, take the NVDA add on-s RSS feed and the NVDA main RSS feed and have them post to here whenever content gets updated.


Re: Emailing: NVDA Excel losing focus

Gene
 

What happens if you use read current line when speech starts?  I don't use Excel (spelling) but in general, if I use something like browser mode search on an Internet page or elsewhere and excess verbiage is spoken, as it usually is, using read current line immediately reads what is found.
 
Gene

----- Original Message -----
Sent: Monday, February 25, 2019 2:43 AM
Subject: Re: [nvda] Emailing: NVDA Excel losing focus

Quentin,

 

Thanks, the double tap of the left alt key does bring back the focus.

 

It begins with a lengthy statement:

ribbon tab tab control expanded. Home tab alt h, 2 of 13

before stating the cell contents!

 

Despite the verbiage, That is much better than swapping out and back which involves a delay because the workbook is very big.

 

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Monday, February 25, 2019 4:03 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Emailing: NVDA Excel losing focus

 

Hi Cearbhall,

 

Excel is mostly behaving for me, however, I did find sometimes using F5 to jump between cells, particularly when it changes pages, it sometimes loses focus like you found, although mine didn't throw up errors like yours.  When it does lose focus in Excel, you should be able to press ALT twice quickly to get the focus back.  I was sure we had an issue for it, probably several, but they are hiding from me this afternoon, so I can't check where they are at.  I will keep looking.

 

Quentin.

 

On Mon, Feb 25, 2019 at 12:00 AM Gene <gsasner@...> wrote:

Most lists don't allow attachments for security reasons.

 

Gene

----- Original Message -----

Sent: Sunday, February 24, 2019 5:48 AM

Subject: [nvda] Emailing: NVDA Excel losing focus

 

Quentin and friends,

I apologise for sending this several times. It seems that the system,
somewhere, will not allow the log file to remain attached so I am pasting it
to the bottom of the message and sending it again. I hope you forgive the
long message that results!

Here is the issue:

I wonder if you can help me with this problem?

I am running Windows 10, Office 365, and the latest NVDA. I am working on an
Excel worksheet where I have three panels of data that must correlate in
various ways.     One of the tasks is to compare the contents of cells in
columns "K", "Z" and "AK for the same row.

When I press F5 to go to, say, K19, NVDA echoes the contents of the cell
perfectly and I can review the data under the numpad key 5 .
I then press F5 again and type in AK19 and press enter to reach that cell.
NVDA does not call out the contents of the cell but focusses on the top of
the screen and will not be moved for love or money!
I then press alt+tab to swap out of Excel elsewhere and press alt+tab again
to get back into excel. Now NVDA reports the contents of the cell and I can
review the contents under the numpad 5 key.
Pressing F5 again, brings me back to the K19 cell and this time NVDA does
not focus on the cell and so I must switch away and back again with alt+tab
to read the cell contents.

This is the repeated pattern. Occasionally, NVDA does echo the target cell
on landing but more often than not, it does not do so.

I have attached the log file but all I can see in it are errors and no sign
of my keystrokes.

I tried these steps with JAWS and each cell is echoed perfectly. I take it,
then, that Windows is working perfectly.
Is this a known bug in NVDA?
Is there an options setting that I should set?

All advice welcome!

All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

Here is the log file:
INFO - __main__ (23:02:40.913):
Starting NVDA
INFO - core.main (23:02:41.256):
Config dir: C:\Users\Cearbhall\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (23:02:41.256):
Loading config: C:\Users\Cearbhall\AppData\Roaming\nvda\nvda.ini
INFO - core.main (23:02:41.444):
NVDA version 2018.4
INFO - core.main (23:02:41.444):
Using Windows version 10.0.17134 workstation
INFO - core.main (23:02:41.444):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC
v.1500 32 bit (Intel)]
INFO - core.main (23:02:41.444):
Using comtypes version 1.1.3
INFO - core.main (23:02:41.444):
Using configobj version 5.1.0 with validate version 1.0.1
DEBUGWARNING - touchHandler.touchSupported (23:02:41.631):
No touch devices found
INFO - synthDriverHandler.setSynth (23:02:42.461):
Loaded synthDriver eloquence
INFO - core.main (23:02:42.461):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (23:02:42.467):
Braille input initialized
INFO - braille.initialize (23:02:42.467):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (23:02:42.471):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (23:02:42.512):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (23:02:42.536):
UIAutomation: IUIAutomation5
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (23:02:44.267):
No locale gesture map for language en
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (23:02:44.267):
No user gesture map
DEBUGWARNING - touchHandler.touchSupported (23:02:44.328):
No touch devices found
DEBUGWARNING - Python warning (23:02:44.542):
C:\Users\Cearbhall\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteCl
ient\configuration.py:5: DeprecationWarning: Importing validate directly is
deprecated. Please use configobj.validate instead
INFO - core.main (23:02:45.365):
NVDA initialized
DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale
(23:02:45.382):
No CLDR data for locale en_UK
DEBUGWARNING - RPC process 7160 (SearchUI.exe) (23:02:48.476):
Thread 7520, build\x86_64\remote\ia2Support.cpp,
IA2Support_inProcess_initialize, 121:
disabling IA2 support

DEBUGWARNING - RPC process 7668 (ShellExperienceHost.exe) (23:02:51.595):
Thread 10536, build\x86_64\remote\ia2Support.cpp,
IA2Support_inProcess_initialize, 121:
disabling IA2 support

DEBUGWARNING - watchdog._watcher (23:02:54.650):
Trying to recover from freeze, core stack:
  File "nvda.pyw", line 217, in <module>
  File "core.pyo", line 515, in main
  File "wx\core.pyo", line 2134, in MainLoop
  File "gui\__init__.pyo", line 963, in Notify
  File "core.pyo", line 485, in run
  File "IAccessibleHandler.pyo", line 897, in pumpAll
  File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
  File "IAccessibleHandler.pyo", line 524, in winEventToNVDAEvent
  File "_UIAHandler.pyo", line 378, in isUIAWindow
  File "_UIAHandler.pyo", line 366, in _isUIAWindowHelper

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:02:56.904):
oleacc.AccessibleObjectFromEvent with window 66800, objectID -4 and childID
0: [Error -2147024809] The parameter is incorrect
INFO - config.ConfigManager._loadConfig (23:02:57.153):
Loading config:
C:\Users\Cearbhall\AppData\Roaming\nvda\profiles\spreadsheet.ini
DEBUGWARNING - NVDAObjects.window.excel.ExcelBase._getDropdown
(23:02:57.194):
Could not locate dropdown list in previous objects
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:02:57.364):
oleacc.AccessibleObjectFromEvent with window 66984, objectID 12 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:02:57.367):
oleacc.AccessibleObjectFromEvent with window 66984, objectID 6 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - watchdog._watcher (23:03:07.131):
Trying to recover from freeze, core stack:
  File "nvda.pyw", line 217, in <module>
  File "core.pyo", line 515, in main
  File "wx\core.pyo", line 2134, in MainLoop
  File "gui\__init__.pyo", line 963, in Notify
  File "core.pyo", line 485, in run
  File "IAccessibleHandler.pyo", line 897, in pumpAll
  File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
  File "IAccessibleHandler.pyo", line 524, in winEventToNVDAEvent
  File "_UIAHandler.pyo", line 378, in isUIAWindow
  File "_UIAHandler.pyo", line 366, in _isUIAWindowHelper

DEBUGWARNING - watchdog._watcher (23:03:09.135):
Trying to recover from freeze, core stack:
  File "nvda.pyw", line 217, in <module>
  File "core.pyo", line 515, in main
  File "wx\core.pyo", line 2134, in MainLoop
  File "gui\__init__.pyo", line 963, in Notify
  File "core.pyo", line 486, in run
  File "queueHandler.pyo", line 86, in pumpAll
  File "queueHandler.pyo", line 53, in flushQueue
  File "eventHandler.pyo", line 62, in _queueEventCallback
  File "eventHandler.pyo", line 155, in executeEvent
  File "eventHandler.pyo", line 92, in __init__
  File "eventHandler.pyo", line 100, in next
  File "NVDAObjects\__init__.pyo", line 908, in event_typedCharacter
  File "speech.pyo", line 679, in speakTypedCharacters
  File "api.pyo", line 248, in isTypingProtected
  File "baseObject.pyo", line 34, in __get__
  File "baseObject.pyo", line 115, in _getPropertyViaCache
  File "NVDAObjects\__init__.pyo", line 782, in _get_isProtected
  File "baseObject.pyo", line 34, in __get__
  File "baseObject.pyo", line 115, in _getPropertyViaCache
  File "NVDAObjects\UIA\__init__.pyo", line 1071, in _get_states
  File "NVDAObjects\UIA\__init__.pyo", line 738, in
_prefetchUIACacheForPropertyIDs

DEBUGWARNING - eventHandler.executeEvent (23:03:12.355):
error executing event: typedCharacter on <NVDAObjects.UIA.ListItem object at
0x068AD290> with extra args of {'ch': u'\r'}
Traceback (most recent call last):
  File "eventHandler.pyo", line 155, in executeEvent
  File "eventHandler.pyo", line 92, in __init__
  File "eventHandler.pyo", line 100, in next
  File "NVDAObjects\__init__.pyo", line 908, in event_typedCharacter
  File "speech.pyo", line 679, in speakTypedCharacters
  File "api.pyo", line 248, in isTypingProtected
  File "baseObject.pyo", line 34, in __get__
  File "baseObject.pyo", line 115, in _getPropertyViaCache
  File "NVDAObjects\__init__.pyo", line 782, in _get_isProtected
  File "baseObject.pyo", line 34, in __get__
  File "baseObject.pyo", line 115, in _getPropertyViaCache
  File "NVDAObjects\UIA\__init__.pyo", line 1071, in _get_states
  File "NVDAObjects\UIA\__init__.pyo", line 738, in
_prefetchUIACacheForPropertyIDs
COMError: (-2147220991, 'An event was unable to invoke any of the
subscribers', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IA2WindowHandle
(23:03:12.638):
IAccessible2::windowHandle failed: (-2147467259, 'Unspecified error', (None,
None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (23:03:12.648):
Resorting to WindowFromPoint on accLocation
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IA2WindowHandle
(23:03:12.716):
IAccessible2::windowHandle failed: (-2147467259, 'Unspecified error', (None,
None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (23:03:12.717):
Resorting to WindowFromPoint on accLocation
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IA2WindowHandle
(23:03:13.559):
IAccessible2::windowHandle failed: (-2147467259, 'Unspecified error', (None,
None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (23:03:13.562):
Resorting to WindowFromPoint on accLocation
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IA2WindowHandle
(23:03:17.036):
IAccessible2::windowHandle failed: (-2147467259, 'Unspecified error', (None,
None, None, 0, None))
DEBUGWARNING - Python warning (23:03:19.766):
C:\Program Files (x86)\NVDA\library.zip\keyboardHandler.py:511:
DeprecationWarning: Yield() is deprecated
DEBUGWARNING - Python warning (23:03:19.766):
C:\Program Files (x86)\NVDA\library.zip\api.py:274: DeprecationWarning:
Yield() is deprecated
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:19.766):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 131 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:19.766):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 133 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:20.470):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 139 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:20.470):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 140 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:20.470):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 142 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.325):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 144 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - NVDAObjects.window.excel.ExcelBase._getDropdown
(23:03:28.364):
Could not locate dropdown list in previous objects
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.484):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 175 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.484):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 176 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.484):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 177 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.489):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 178 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.489):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 179 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.489):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 180 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.489):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 181 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.489):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 182 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.489):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 183 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.489):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 184 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.489):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 223 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:28.489):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 186 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:37.490):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 230 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:37.490):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 320 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:37.490):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 323 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:37.490):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 324 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:37.490):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 327 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:37.490):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 328 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:37.490):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 330 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:37.490):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 2147483647 and
childID 1: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:37.490):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 2147483647 and
childID 2: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:37.500):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 350 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:37.500):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 344 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING -
NVDAObjects.window.excel.ExcelBrowseModeTreeInterceptor._get_isAlive
(23:03:40.201):
could not compare sheet names
Traceback (most recent call last):
  File "NVDAObjects\window\excel.pyo", line 452, in _get_isAlive
  File "comtypesMonkeyPatches.pyo", line 35, in new__getattr__
  File "comtypes\client\lazybind.pyo", line 168, in __getattr__
  File "comtypes\automation.pyo", line 729, in _invoke
COMError: (-2147418111, 'Call was rejected by callee.', (None, None, None,
0, None))
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.065):
oleacc.AccessibleObjectFromEvent with window 720986, objectID -4 and childID
5: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.118):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 356 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.118):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 354 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.118):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 442 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.118):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 445 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.118):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 446 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.118):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 449 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.118):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 450 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.118):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 453 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.134):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 454 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.134):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 461 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - NVDAObjects.window.excel.ExcelBase._getDropdown
(23:03:43.173):
Could not locate dropdown list in previous objects
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.286):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 481 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:43.286):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 475 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:50.282):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 486 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:50.283):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 500 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:50.285):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 494 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:50.285):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 488 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:51.148):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 506 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:51.148):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 507 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:51.148):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 525 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:51.148):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 517 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:51.148):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 509 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:54.016):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 532 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:54.016):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 579 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:54.016):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 580 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:54.026):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 583 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:54.026):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 584 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:54.026):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 586 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:54.026):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 587 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:54.026):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 2147483647 and
childID 1: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:54.026):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 2147483647 and
childID 2: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:54.026):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 611 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:54.026):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 601 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:56.048):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 618 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:56.048):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 665 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:56.048):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 666 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:56.048):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 669 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:56.048):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 670 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:56.048):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 672 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:56.048):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 673 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:56.048):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 2147483647 and
childID 1: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:56.048):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 2147483647 and
childID 2: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:56.058):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 701 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:56.058):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 695 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:57.197):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 708 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:57.197):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 755 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:57.197):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 756 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:57.197):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 759 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:57.197):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 760 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:57.197):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 762 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:57.197):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 763 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:57.197):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 2147483647 and
childID 1: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:57.197):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 2147483647 and
childID 2: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:57.207):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 787 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:57.207):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 777 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:58.022):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 793 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:58.244):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 805 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:03:58.244):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 799 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING -
NVDAObjects.window.excel.ExcelBrowseModeTreeInterceptor._get_isAlive
(23:03:59.503):
could not compare sheet names
Traceback (most recent call last):
  File "NVDAObjects\window\excel.pyo", line 452, in _get_isAlive
  File "comtypesMonkeyPatches.pyo", line 35, in new__getattr__
  File "comtypes\client\lazybind.pyo", line 168, in __getattr__
  File "comtypes\automation.pyo", line 729, in _invoke
COMError: (-2147418111, 'Call was rejected by callee.', (None, None, None,
0, None))
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:04.174):
oleacc.AccessibleObjectFromEvent with window 262252, objectID -4 and childID
5: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:04.275):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 811 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:04.275):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 809 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:04.275):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 896 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:04.275):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 899 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:04.275):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 900 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:04.275):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 903 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:04.275):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 904 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:04.275):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 907 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:04.275):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 908 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:04.275):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 915 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - NVDAObjects.window.excel.ExcelBase._getDropdown
(23:04:04.328):
Could not locate dropdown list in previous objects
DEBUGWARNING -
NVDAObjects.window.excel.ExcelBrowseModeTreeInterceptor._get_isAlive
(23:04:09.213):
could not compare sheet names
Traceback (most recent call last):
  File "NVDAObjects\window\excel.pyo", line 452, in _get_isAlive
  File "comtypesMonkeyPatches.pyo", line 35, in new__getattr__
  File "comtypes\client\lazybind.pyo", line 168, in __getattr__
  File "comtypes\automation.pyo", line 729, in _invoke
COMError: (-2147418111, 'Call was rejected by callee.', (None, None, None,
0, None))
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.256):
oleacc.AccessibleObjectFromEvent with window 197100, objectID -4 and childID
5: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.302):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 964 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.318):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 959 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.318):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 957 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.318):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 997 and childID
0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.318):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1000 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.318):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1001 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.318):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1004 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.318):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1005 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.318):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1008 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.318):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1009 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.325):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1012 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.325):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1013 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:12.325):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1020 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:20.865):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1038 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - NVDAObjects.window.excel.ExcelBase._getDropdown
(23:04:20.895):
Could not locate dropdown list in previous objects
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:21.006):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1056 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:21.006):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1044 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING -
NVDAObjects.window.excel.ExcelBrowseModeTreeInterceptor._get_isAlive
(23:04:25.884):
could not compare sheet names
Traceback (most recent call last):
  File "NVDAObjects\window\excel.pyo", line 452, in _get_isAlive
  File "comtypesMonkeyPatches.pyo", line 35, in new__getattr__
  File "comtypes\client\lazybind.pyo", line 168, in __getattr__
  File "comtypes\automation.pyo", line 729, in _invoke
COMError: (-2147418111, 'Call was rejected by callee.', (None, None, None,
0, None))
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.611):
oleacc.AccessibleObjectFromEvent with window 48301500, objectID -8 and
childID 0: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.671):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1067 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.671):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1062 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.671):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1060 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.671):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1100 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.681):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1103 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.681):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1104 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.681):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1107 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.681):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1108 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.681):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1111 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.681):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1112 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.681):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1115 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.681):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1116 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:26.681):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1123 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:33.898):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1153 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - NVDAObjects.window.excel.ExcelBase._getDropdown
(23:04:33.928):
Could not locate dropdown list in previous objects
DEBUGWARNING -
NVDAObjects.window.excel.ExcelBrowseModeTreeInterceptor._get_isAlive
(23:04:39.108):
could not compare sheet names
Traceback (most recent call last):
  File "NVDAObjects\window\excel.pyo", line 452, in _get_isAlive
  File "comtypesMonkeyPatches.pyo", line 35, in new__getattr__
  File "comtypes\client\lazybind.pyo", line 168, in __getattr__
  File "comtypes\automation.pyo", line 729, in _invoke
COMError: (-2147418111, 'Call was rejected by callee.', (None, None, None,
0, None))
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.723):
oleacc.AccessibleObjectFromEvent with window 132762, objectID -4 and childID
5: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1179 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1174 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1172 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1212 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1215 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1216 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1219 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1220 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1223 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1224 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1227 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1228 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:41.786):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1235 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:46.788):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1261 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - NVDAObjects.window.excel.ExcelBase._getDropdown
(23:04:46.822):
Could not locate dropdown list in previous objects
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:46.937):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1278 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:46.937):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1267 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING -
NVDAObjects.window.excel.ExcelBrowseModeTreeInterceptor._get_isAlive
(23:04:51.917):
could not compare sheet names
Traceback (most recent call last):
  File "NVDAObjects\window\excel.pyo", line 452, in _get_isAlive
  File "comtypesMonkeyPatches.pyo", line 35, in new__getattr__
  File "comtypes\client\lazybind.pyo", line 168, in __getattr__
  File "comtypes\automation.pyo", line 729, in _invoke
COMError: (-2147418111, 'Call was rejected by callee.', (None, None, None,
0, None))
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.842):
oleacc.AccessibleObjectFromEvent with window 329370, objectID -8 and childID
0: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.903):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1289 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1284 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1282 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1322 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1325 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1326 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1329 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1330 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1333 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1334 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1337 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1338 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:52.911):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1345 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:04:57.441):
oleacc.AccessibleObjectFromEvent with window 67262, objectID 1375 and
childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - NVDAObjects.window.excel.ExcelBase._getDropdown
(23:04:57.492):
Could not locate dropdown list in previous objects

That is the end fo the log file! Any ideas?



 

--

Quentin Christensen
Training and Support Manager

 

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

 

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Problem with windows10 OCR and NVDA

 

Just adding
While with this message opened I tried to OCR just for fun, seeing what I would get.
What a surprise, the OCR worked just like a charm.
Weird!
Em 25/02/2019 08:48, marcio via Groups.Io escreveu:

Very same here!
And I'm also using the latest NVDA Alpha with Win 10 1803.
Well I'm not using the latest at all because I need to update to the very latest so to speak which showed up just now. I'll do it sometime later, I guess.
However, the message I get is absolutely the same and no, I don't think just updating to the latest Alpha will fix it since aparently the folks on the NVDA dev side weren't aware of it.
Let's wait...

Em 25/02/2019 08:31, Mallard escreveu:
Yes, here too. Something must be broken, because I've opened a pdf that is perfectly visible with any pdf reading apps, including Edge.

I tried opening with Sumatra pdf, which only shows the image and not the text. Usually, when I do that, I can view the page with Inw10 OCR. Now it keeps saying


"Content not visible" (contenuto non visibile in Italian).


No idea what could have happened.

I'm using the latest Alpha of NVDA and Windows 10 1803.


Ciao,

Ollie




Il 25/02/2019 11:57, marcio via Groups.Io ha scritto:
Same here. I don't have Jaws to test with, though, so don't know if it would be different.
Anyone to help us? :)

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 06:15, Aravind R escreveu:
Dear friends,

I am trying to do OCR with pdf using NVDA+r in windows10.
Wherever i try, it is saying "Recognising result document" but nothing
is displayed and its working well with jaws's built-in ocr.
Kindly guide where changes to be made to make work with windows10 OCR










Re: Having troubles to play with a website

 

Hi George,
I'm using the laptop layout. And I just did it yesterday before giving up on this site. Nothing happened at all, so I really don't feel like trying it anymore :(
Em 25/02/2019 00:23, George McCoy escreveu:

Do you have nvda's keyboard layout  set to laptop?  if so, do the following:

Press b until you get to the button you want to click.

hold down the nvda and shift keys and press the letter m to route the mouse to the button.

Hold down the nvda key and press the left bracket key to click the button.


To see whether keyboard layout is set to laptop or desktop, do the following:

Press nvda plus n to open the nvda menu.

Press p to open preferences.

Press enter to open settings.

Press the letter k for keyboard.

Tab once and the keyboard layout setting will be spoken.

Press escape to exit the nvda menu.


Hth,

George


On 2/24/2019 3:47 PM, marcio via Groups.Io wrote:
Well I tried to use the said commands to make whatever there play, but still no luck.
As I am using a Dell laptop, I do:
Hit B until I hear play.
Press NVDA+SHIFT+BACKSPACE twice until hear play again.
Press NVDA+].
And that's it. Nothing happens :(

Em 24/02/2019 16:56, Brian Vogel escreveu:
Indeed, all of the following are true:

  1. You will not find the buttons for audio control on the https://golubovsky.bandcamp.com/album/unhuman-voices page except by using the B quick navigation shortcut
  2. Hitting spacebar or enter when you have gained focus on those buttons does nothing.
  3. Using NVDA+/ to route the PC mouse pointer to the NVDA navigator object, then using NumPad slash to activate it will make it play (or, if you're on the jump to next track or other audio control button do what that button does).
-- 

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 




Re: Problem with windows10 OCR and NVDA

 

Very same here!
And I'm also using the latest NVDA Alpha with Win 10 1803.
Well I'm not using the latest at all because I need to update to the very latest so to speak which showed up just now. I'll do it sometime later, I guess.
However, the message I get is absolutely the same and no, I don't think just updating to the latest Alpha will fix it since aparently the folks on the NVDA dev side weren't aware of it.
Let's wait...

Em 25/02/2019 08:31, Mallard escreveu:

Yes, here too. Something must be broken, because I've opened a pdf that is perfectly visible with any pdf reading apps, including Edge.

I tried opening with Sumatra pdf, which only shows the image and not the text. Usually, when I do that, I can view the page with Inw10 OCR. Now it keeps saying


"Content not visible" (contenuto non visibile in Italian).


No idea what could have happened.

I'm using the latest Alpha of NVDA and Windows 10 1803.


Ciao,

Ollie




Il 25/02/2019 11:57, marcio via Groups.Io ha scritto:
Same here. I don't have Jaws to test with, though, so don't know if it would be different.
Anyone to help us? :)

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 25/02/2019 06:15, Aravind R escreveu:
Dear friends,

I am trying to do OCR with pdf using NVDA+r in windows10.
Wherever i try, it is saying "Recognising result document" but nothing
is displayed and its working well with jaws's built-in ocr.
Kindly guide where changes to be made to make work with windows10 OCR