Excel not speaking cell coordinates or content on startup or refocus


Dark Count
 

Hello.

I am running into a rather odd situation when I startup Excel

Or when I take focus away from it and minimize, then come back to it.


NVDA will say A1 selected, and then will not speak as I arrow around.

If I press alt to go into the ribbon menus, and then alt to exit them, then it will start speaking the cell's coordinates and content.


If I minimize and come back, again, NVDA will speak the cell at cursor with the selected term, and not speak on arrowing.

Same solution as above works.


I don't hear error sounds, and a quick look the log does not seem to indicate anything wrong in Excel either.

I have unchecked use UI automation for controls when available in Excel as a test.


I am using office 365 with the latest updates, and NVDA 2022.2, as well as 2022.3 beta.

The results are the same.


Thanks,


D C


Luke Davis
 

Dark Count wrote:

I am running into a rather odd situation when I startup Excel
Or when I take focus away from it and minimize, then come back to it.
NVDA will say A1 selected, and then will not speak as I arrow around.
I had something similar to this happening with Office 2019, about 18 months ago. I reported it in a Github issue, but it never got any love. In my case, the logs showed that the virtual buffer was crashing, and the alt trick caused it to be reinitialized. But switching apps would also fix it, which doesn't seem to be happening with you.

Have you tried NVDA with add-ons disabled?

Also, have you tried the COM Registration Fixing Tool in the NVDA tools menu?

Luke


hurrikennyandopo ...
 

Hi


I remember a fix but can not remember what version of excel it was but one was apparently if you went into excel then tried to arrow around say from a1 to other cells it would not say any thing.


Apparently if the scroll lock was on it would cause this problem


When turned off you could arrow around and hear what was in each cell. Maybe it was hit accidentally.


I did also about the same time see the other suggestion given but think it was for latest excel?



Let us know if it was the scroll lock causing the problem?


Gene nz

On 7/08/2022 6:23 pm, William wrote:
Luke

My experience is disabling the uia option in nvda will correctly report the set column and row header.


Luke Davis 於 7/8/2022 07:10 寫道:
Dark Count wrote:

I am running into a rather odd situation when I startup Excel
Or when I take focus away from it and minimize, then come back to it.
NVDA will say A1 selected, and then will not speak as I arrow around.
I had something similar to this happening with Office 2019, about 18 months ago. I reported it in a Github issue, but it never got any love. In my case, the logs showed that the virtual buffer was crashing, and the alt trick caused it to be reinitialized. But switching apps would also fix it, which doesn't seem to be happening with you.

Have you tried NVDA with add-ons disabled?

Also, have you tried the COM Registration Fixing Tool in the NVDA tools menu?

Luke








Dark Count
 

Unfortunately it is not the scroll lock causing this.

Though I too have had that happen before.

The com registration tool did not fix this, though I seem to have this happening more randomly.


TY


D C

On 8/7/2022 1:15 PM, hurrikennyandopo ... wrote:
Hi


I remember a fix but can not remember what version of excel it was but one was apparently if you went into excel then tried to arrow around say from a1 to other cells it would not say any thing.


Apparently if the scroll lock was on it would cause this problem


When turned off you could arrow around and hear what was in each cell. Maybe it was hit accidentally.


I did also about the same time see the other suggestion given but think it was for latest excel?



Let us know if it was the scroll lock causing the problem?


Gene nz


On 7/08/2022 6:23 pm, William wrote:
Luke

My experience is disabling the uia option in nvda will correctly report the set column and row header.


Luke Davis 於 7/8/2022 07:10 寫道:
Dark Count wrote:

I am running into a rather odd situation when I startup Excel
Or when I take focus away from it and minimize, then come back to it.
NVDA will say A1 selected, and then will not speak as I arrow around.
I had something similar to this happening with Office 2019, about 18 months ago. I reported it in a Github issue, but it never got any love. In my case, the logs showed that the virtual buffer was crashing, and the alt trick caused it to be reinitialized. But switching apps would also fix it, which doesn't seem to be happening with you.

Have you tried NVDA with add-ons disabled?

Also, have you tried the COM Registration Fixing Tool in the NVDA tools menu?

Luke











 

On Sun, Aug 7, 2022 at 06:38 PM, Dark Count wrote:
The com registration tool did not fix this, though I seem to have this happening more randomly.
-
Have you tried running NVDA with add-ons disabled to see if that makes any difference?

At least doing so allows you to rule in/out a possible culprit.  I realize that you likely can't use NVDA sans add-ons as a permanent situation, but you can then systematically do a "search and destroy" mission to determine which add-on is causing the issue if it disappears when you run sans add-ons.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard


Dark Count
 

I have done so.

I also ran a repair of office.

Now, here is an interesting conundrum.

I disabled add-ons, and one core voices not only has the issue, but also errors on focus to Excel.


E-speak altogether does not seem to be having this issue in Excel.

Tempted to just create a profile on focus to excel with E-speak and call it a day, but for the fact this is not going to solve the overall issue.


TY


D C


On 8/7/2022 3:42 PM, Brian Vogel wrote:
On Sun, Aug 7, 2022 at 06:38 PM, Dark Count wrote:
The com registration tool did not fix this, though I seem to have this happening more randomly.
-
Have you tried running NVDA with add-ons disabled to see if that makes any difference?

At least doing so allows you to rule in/out a possible culprit.  I realize that you likely can't use NVDA sans add-ons as a permanent situation, but you can then systematically do a "search and destroy" mission to determine which add-on is causing the issue if it disappears when you run sans add-ons.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard


Dark Count
 

Just a quick update:


Under the this is going to be one of those weird cases which we never found a solution to because resolved itself, sort of...

It seems after changing to E-speak, and then restarting NVDA with add-ons enabled again, and changing back to my default synth, things are for now at least behaving.

I did run a prepare of Office 365, and also the com registration tool which I think I will get into the habit of doing so every few months just because I notice things are snappier where they were not before in other applications.


Why the different synthesizer would make a difference is still a mystery to me.

So, till somebody spins a theory, or comes up with an explanation, I'll say... just because.


Thanks for the help.


D C



On 8/8/2022 11:42 AM, Dark Count via groups.io wrote:

I have done so.

I also ran a repair of office.

Now, here is an interesting conundrum.

I disabled add-ons, and one core voices not only has the issue, but also errors on focus to Excel.


E-speak altogether does not seem to be having this issue in Excel.

Tempted to just create a profile on focus to excel with E-speak and call it a day, but for the fact this is not going to solve the overall issue.


TY


D C


On 8/7/2022 3:42 PM, Brian Vogel wrote:
On Sun, Aug 7, 2022 at 06:38 PM, Dark Count wrote:
The com registration tool did not fix this, though I seem to have this happening more randomly.
-
Have you tried running NVDA with add-ons disabled to see if that makes any difference?

At least doing so allows you to rule in/out a possible culprit.  I realize that you likely can't use NVDA sans add-ons as a permanent situation, but you can then systematically do a "search and destroy" mission to determine which add-on is causing the issue if it disappears when you run sans add-ons.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard