Date   

Recommended way of excluding certain elements from navigation

Toni Barth
 

Hello,
 
because noone replied to my last post from a few days ago and I accidentally used the wrong tag for my question, i'm sending my previous message again down below.
 
i'm developing an add-on right now to enhance the usability of an application. This application contains at least one table with several cells, but some of those cells, even though they are navigatable by NVDA, contain unimportant information, like the value 'None' or just an icon. I thus wanted to "hide" those cells for the user, meaning that they shouldn't be able to navigate to them using the tab key or arrow keys and tried several ways to do so.
 
I overlayed the table row and override _get_children(), removing the certain children from the list, but I noticed that _get_children() never seems to get executed.
 
I also tried adding states to the specific cells like controlTypes.STATE_INVISIBLE or controlTypes.STATE_UNAVAILABLE, but nothing helped.
 
I also tried moving the focus manually whenever the cell is focused by using event_gainFocus(), but even this seems to mess up things even further. Same goes for using redirectFocus and/or _get_redirectFocus(). It properly redirects my focus to the next cell, but the cursor still seems to be located in the cell whatsoever, means whenever I press the right arrow key, i'll get the same, second cell announced a second time.
 
Do you have an idea how to remove those cells from keyboard navigation (not navigator, but at least from tab/arrow keys navigation)?
 
There must be an easy way to exclude certain elements from keyboard navigation.
 
Thanks for your help :).
 
Best Regards.
 
Toni Barth


Re: WX.Menu item help text: where is it used?

Noelia Ruiz
 

Hi, answering in devel in case lead developers would like to clarify
something or use this discussion for NVDA's improvements.
I think that, in practical terms, the optional help string is never
used by NVDA, never spoken or braillified.
I don't know if this would make sense with the new vision framework,
for instance if this can be highlighted or show in some way.

Cheers

2019-08-30 4:22 GMT+02:00, Luke Davis <luke@...>:

Hello

Perhaps a stupid question, but if I call something like:

gui.mainFrame.sysTrayIcon.preferencesMenu.Append(wx.ID_ANY,
_("&menuItemName..."), _("Some descriptive text"))

where will "Some descriptive text" be used?

WX calls this "help", so I thought I would find it in a mouse hover or
tooltip
of some kind, but in attempting this with both the keyboard and the actual
mouse, in NVDA 2017.3, I can not get anything spoken.

The docs for WX.Menu 4.1.0 say:

An optional help string associated with the item. By default, the handler
for
the wxEVT_MENU_HIGHLIGHT event
displays this string in the status line.

Which helps me not at all.

Thanks

--
Luke Davis
Moderator: the new NVDA Help mailing list! (NVDAHelp+subscribe@groups.io)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)




Re: Visual studio version

Karl-Otto Rosenqvist
 

Hi!
I just realized that you're trying to use Visual Studio to compile NVDA... my answer was about using NVDA when developing in Visual Studio. I'm very sorry for this confusion and I'm sorry that I cannot help you.


Kind regards

Karl-Otto


Karl-Otto Rosenqvist
Mawingu
Orgnr: 750804-3937
0701- 75 98 56
karl-otto@...
https://mawingu.se

Den 2019-09-02 kl. 21:00, skrev Tage Johansson:

Ok, thanks for the information. As I understand it, I can use vs 2019.
How ever, I am not very sure which components to install. The README says that I should install:
◾ In the Installation details section, under Individual components, ensure the following are selected:
◾ Visual C++ compilers and libraries for ARM64
◾ Visual C++ ATL for ARM64
I cannot find those specific names, so I tried to install the following:
* MSVC v141 - VS 2017 C++ ARM64 build tools (v14.16)
* C++ ATL for v141 build tools (ARM64)
But when I run scons source I get the following error:
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
link /nologo /incremental:no /WX /subsystem:windows,6.02 /release /OPT:REF /export:DllGetClassObject,private /export:DllCanUnloadNow,private /export:GetProxyDllInfo,private /manifest:embed /manifestinput:build\a
rm64\IAccessible2proxy.manifest /dll /out:build\arm64\IAccessible2proxy.dll /implib:build\arm64\IAccessible2proxy.lib rpcrt4.lib oleaut32.lib ole32.lib /PDB:build\arm64\IAccessible2proxy.dll.pdb /DEBUG build\arm
64\ia2_i.obj build\arm64\ia2_p.obj build\arm64\ia2_data.obj
LINK : fatal error LNK1104: cannot open file 'LIBCMT.lib'
scons: *** [build\arm64\IAccessible2proxy.dll] Error 1104
scons: building terminated because of errors.
Can anyone help me to solve the problem and build NVDA?
Best regards,
Tage
On 8/31/2019 6:44 PM, Brian's Mail list account via Groups.Io wrote:
I suppose you could prove it by using jaws demo and see if it works differently?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message ----- From: "Karl-Otto Rosenqvist" <Karl-otto@...>
To: <nvda-devel@groups.io>
Sent: Saturday, August 31, 2019 9:35 AM
Subject: Re: [nvda-devel] Visual studio version


Hi!
I’m using NVDA with both Visual Studio 2017 and 2019 and it works quite well.
The most annoying thing is that Visual Studio compiles your code in the background and that takes quite a lot of processing power so NVDA stops talking sometimes.
This occurs when moving in the solution tree with the keyboard and when a file is selected Visual Studio automatically opens it in the editor which seems to be a heavy task. It’s probably NVDA that processes the text in the file that’s beeing shown in the editor and that’s why it stops talking.

When I build a solution and there are errors that’s shown in the error list there’s a looong silence before NVDA starts talking again. That’s probably the compilation that kills it.

I’ve tried to lower the execution priority for the compiler and ide and increased the priority of NVDA but it tidn’t make any difference.


Kind regards


Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

31 aug. 2019 kl. 05:51 skrev Luke Davis <luke@...>:

You may want to search the archives, this question has come up before. I believe the answer was that it's fine to use 2019, but there was a small issue or two. I can't remember exactly.

Luke
On Fri, 30 Aug 2019, Tage Johansson wrote:

Do I need visual studio 2017 specificly or is it fine to use visual studio 2019?
Best regards,
Tage
--
Luke Davis
Moderator: the new NVDA Help mailing list! (https://groups.io/g/NVDAHelp)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)








Subscribing to UIAutomation events

Karl-Otto Rosenqvist
 

Hi!
It's me with the UIA DataGrid again...
Now they've added events to the UIA DataGrid and I'm able to subscribe to it from C# as follows:

Automation.AddAutomationEventHandler(
SelectionPattern.InvalidatedEvent,
grid,
TreeScope.Element,
UIAeventHandler = new AutomationEventHandler(OnUIAutomationEvent)
);

And then unsubscribe like this:
if (UIAeventHandler != null)
{
Automation.RemoveAutomationEventHandler(
SelectionPattern.InvalidatedEvent,
grid,
UIAeventHandler
);
} // if

The method that's getting called when the event is raised looks like this:
private static void OnUIAutomationEvent(object src, AutomationEventArgs e)
{
// Make sure the element still exists. Elements such as tooltips
// can disappear before the event is processed.
AutomationElement sourceElement;
try
{
sourceElement = src as AutomationElement;
}
catch (ElementNotAvailableException)
{
return;
}

if (e.EventId == SelectionPattern.InvalidatedEvent)
{
try
{
Console.WriteLine("--- Markering ---");
var s = grid.GetCurrentPattern(SelectionPattern.Pattern) as SelectionPattern;
foreach (var c in s.Current.GetSelection())
{
var v = c.GetCurrentPattern(ValuePattern.Pattern) as ValuePattern;
System.Console.WriteLine(v.Current.Value);
} // foreach

}
catch (Exception ex)
{
Console.WriteLine("Fel när markerad rad hämtades");
Console.WriteLine(ex.Message);
}

} // if

}


I have the following questions:

1. How do I subscribe to an UIA event in an app m module? I will create a class for the specific UIA element type.

2. How do I get hold of the Selection pattern and the Value patterns for an UIA element? When trying to get hold of the UIASelectionPattern NVDA says that it isn't implemented. The UIASelectionItemPattern is shown when I do a dir(nav) in the Python console but that pattern isn't implemented by the DataGrid.

It seems so close because I can hook up the grid event and print the selection to the console in C# but not in Python. Can anyone point me in the right direction?


Best regards

Karl-Otto

--
Karl-Otto Rosenqvist
Mawingu
Orgnr: 750804-3937
0701- 75 98 56
karl-otto@...
https://mawingu.se


Re: Visual studio version

Tage Johansson <frans.tage@...>
 

Ok, thanks for the information. As I understand it, I can use vs 2019.

How ever, I am not very sure which components to install. The README says that I should install:

◾ In the Installation details section, under Individual components, ensure the following are selected:
◾ Visual C++ compilers and libraries for ARM64
◾ Visual C++ ATL for ARM64


I cannot find those specific names, so I tried to install the following:

* MSVC v141 - VS 2017 C++ ARM64 build tools (v14.16)

* C++ ATL for v141 build tools (ARM64)


But when I run scons source I get the following error:
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
link /nologo /incremental:no /WX /subsystem:windows,6.02 /release /OPT:REF /export:DllGetClassObject,private /export:DllCanUnloadNow,private /export:GetProxyDllInfo,private /manifest:embed /manifestinput:build\a
rm64\IAccessible2proxy.manifest /dll /out:build\arm64\IAccessible2proxy.dll /implib:build\arm64\IAccessible2proxy.lib rpcrt4.lib oleaut32.lib ole32.lib /PDB:build\arm64\IAccessible2proxy.dll.pdb /DEBUG build\arm
64\ia2_i.obj build\arm64\ia2_p.obj build\arm64\ia2_data.obj
LINK : fatal error LNK1104: cannot open file 'LIBCMT.lib'
scons: *** [build\arm64\IAccessible2proxy.dll] Error 1104
scons: building terminated because of errors.

Can anyone help me to solve the problem and build NVDA?

Best regards,
Tage

On 8/31/2019 6:44 PM, Brian's Mail list account via Groups.Io wrote:
I suppose you could prove it by using jaws demo and see if it works differently?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message ----- From: "Karl-Otto Rosenqvist" <Karl-otto@...>
To: <nvda-devel@groups.io>
Sent: Saturday, August 31, 2019 9:35 AM
Subject: Re: [nvda-devel] Visual studio version


Hi!
I’m using NVDA with both Visual Studio 2017 and 2019 and it works quite well.
The most annoying thing is that Visual Studio compiles your code in the background and that takes quite a lot of processing power so NVDA stops talking sometimes.
This occurs when moving in the solution tree with the keyboard and when a file is selected Visual Studio automatically opens it in the editor which seems to be a heavy task. It’s probably NVDA that processes the text in the file that’s beeing shown in the editor and that’s why it stops talking.

When I build a solution and there are errors that’s shown in the error list there’s a looong silence before NVDA starts talking again. That’s probably the compilation that kills it.

I’ve tried to lower the execution priority for the compiler and ide and increased the priority of NVDA but it tidn’t make any difference.


Kind regards


Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

31 aug. 2019 kl. 05:51 skrev Luke Davis <luke@...>:

You may want to search the archives, this question has come up before. I believe the answer was that it's fine to use 2019, but there was a small issue or two. I can't remember exactly.

Luke
On Fri, 30 Aug 2019, Tage Johansson wrote:

Do I need visual studio 2017 specificly or is it fine to use visual studio 2019?
Best regards,
Tage
--
Luke Davis
Moderator: the new NVDA Help mailing list! (https://groups.io/g/NVDAHelp)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)







The threshold snaps

Brian's Mail list account
 

I see this.
commit 7987169fa3cb2050b984f8d7640debd070482c59
Author: Michael Curran <mick@...>
Date: Mon 02 Sep 2019 09:40:16 +1000
Remove threshold and threshold_py3_staging from branches to automatically build in appveyor.yaml as work on these branches is complete.
Raw diff


_______________________________________________
I'm assuming this will mean somebody also cleans up the snapshot page. It might be nice to have try builds here when they are produced to try to fix odd errors like the crashing of explorer in windows 7 in the current stable.


bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users


NVDA try build crash

Brian's Mail list account
 

I have been running the build for stopping crashes in Explorer on windows 7 for some days now with no issues.
This I think is due to something else. I was running the accessible podcatcher from the webbie site, as its very convenient to get saved files from. Normally its fine, but a couple of times this morning it has nvda lock up as below. Since there was no sign of it ever coming back I rebooted a different version of nvda so I could get the log. Here it is.

IO - inputCore.InputManager.executeGesture (11:32:28.351):
Input: kb(desktop):downArrow
IO - speech.speak (11:32:28.365):
Speaking [LangChangeCommand ('en_GB'), 'Inside Health 11 of 17']
IO - inputCore.InputManager.executeGesture (11:32:31.343):
Input: kb(desktop):enter
IO - speech.speak (11:32:31.597):
Speaking [LangChangeCommand ('en_GB'), 'Frame1 list']
IO - speech.speak (11:32:31.610):
Speaking [LangChangeCommand ('en_GB'), 'Getting podcast, please wait. 1 of 1']
DEBUGWARNING - watchdog._watcher (11:32:41.948):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 221, in <module>
File "core.pyc", line 536, in main
File "wx\core.pyc", line 2134, in MainLoop
File "gui\__init__.pyc", line 997, in Notify
File "core.pyc", line 506, in run
File "queueHandler.pyc", line 83, in pumpAll
File "queueHandler.pyc", line 46, in flushQueue
File "queue.pyc", line 107, in empty

DEBUGWARNING - RPC process 1828 (dwm.exe) (11:32:56.453):
Thread 5532, build\x86_64\remote\injection.cpp, inproc_winEventCallback, 66:
SetWindowsHookEx with WH_GETMESSAGE failed, GetLastError returned 5

DEBUGWARNING - RPC process 1828 (dwm.exe) (11:32:56.454):
Thread 5532, build\x86_64\remote\injection.cpp, inproc_winEventCallback, 69:
SetWindowsHookEx with WH_CALLWNDPROC failed, GetLastError returned 5

WARNING - watchdog._watcher (11:32:56.949):
Core frozen in stack:
File "nvda.pyw", line 221, in <module>
File "core.pyc", line 536, in main
File "wx\core.pyc", line 2134, in MainLoop
File "gui\__init__.pyc", line 997, in Notify
File "core.pyc", line 506, in run
File "queueHandler.pyc", line 83, in pumpAll
File "queueHandler.pyc", line 46, in flushQueue
File "queue.pyc", line 107, in empty

WARNING - watchdog._watcher (11:33:11.950):
Core frozen in stack:
File "nvda.pyw", line 221, in <module>
File "core.pyc", line 536, in main
File "wx\core.pyc", line 2134, in MainLoop
File "gui\__init__.pyc", line 997, in Notify
File "core.pyc", line 506, in run
File "queueHandler.pyc", line 83, in pumpAll
File "queueHandler.pyc", line 46, in flushQueue
File "queue.pyc", line 107, in empty

No indication of me using the command to terminate it, it just sulked for nearly a minute then one supposes the task was closed by windows and the new copy rebooted in again.

Brian


bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users


Re: Visual studio version

Brian's Mail list account
 

I suppose you could prove it by using jaws demo and see if it works differently?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Karl-Otto Rosenqvist" <Karl-otto@...>
To: <nvda-devel@groups.io>
Sent: Saturday, August 31, 2019 9:35 AM
Subject: Re: [nvda-devel] Visual studio version


Hi!
I’m using NVDA with both Visual Studio 2017 and 2019 and it works quite well.
The most annoying thing is that Visual Studio compiles your code in the background and that takes quite a lot of processing power so NVDA stops talking sometimes.
This occurs when moving in the solution tree with the keyboard and when a file is selected Visual Studio automatically opens it in the editor which seems to be a heavy task. It’s probably NVDA that processes the text in the file that’s beeing shown in the editor and that’s why it stops talking.

When I build a solution and there are errors that’s shown in the error list there’s a looong silence before NVDA starts talking again. That’s probably the compilation that kills it.

I’ve tried to lower the execution priority for the compiler and ide and increased the priority of NVDA but it tidn’t make any difference.


Kind regards


Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

31 aug. 2019 kl. 05:51 skrev Luke Davis <luke@...>:

You may want to search the archives, this question has come up before. I believe the answer was that it's fine to use 2019, but there was a small issue or two. I can't remember exactly.

Luke
On Fri, 30 Aug 2019, Tage Johansson wrote:

Do I need visual studio 2017 specificly or is it fine to use visual studio 2019?
Best regards,
Tage
--
Luke Davis
Moderator: the new NVDA Help mailing list! (https://groups.io/g/NVDAHelp)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)



Re: Visual studio version

Karl-Otto Rosenqvist
 

Hi!
I’m using NVDA with both Visual Studio 2017 and 2019 and it works quite well.
The most annoying thing is that Visual Studio compiles your code in the background and that takes quite a lot of processing power so NVDA stops talking sometimes.
This occurs when moving in the solution tree with the keyboard and when a file is selected Visual Studio automatically opens it in the editor which seems to be a heavy task. It’s probably NVDA that processes the text in the file that’s beeing shown in the editor and that’s why it stops talking.

When I build a solution and there are errors that’s shown in the error list there’s a looong silence before NVDA starts talking again. That’s probably the compilation that kills it.

I’ve tried to lower the execution priority for the compiler and ide and increased the priority of NVDA but it tidn’t make any difference.


Kind regards


Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

31 aug. 2019 kl. 05:51 skrev Luke Davis <luke@...>:

You may want to search the archives, this question has come up before. I believe the answer was that it's fine to use 2019, but there was a small issue or two. I can't remember exactly.

Luke
On Fri, 30 Aug 2019, Tage Johansson wrote:

Do I need visual studio 2017 specificly or is it fine to use visual studio 2019?
Best regards,
Tage
--
Luke Davis
Moderator: the new NVDA Help mailing list! (https://groups.io/g/NVDAHelp)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)



Re: Visual studio version

Luke Davis
 

You may want to search the archives, this question has come up before. I believe the answer was that it's fine to use 2019, but there was a small issue or two. I can't remember exactly.

Luke

On Fri, 30 Aug 2019, Tage Johansson wrote:

Do I need visual studio 2017 specificly or is it fine to use visual studio 2019?
Best regards,
Tage
--
Luke Davis
Moderator: the new NVDA Help mailing list! (https://groups.io/g/NVDAHelp)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)


Visual studio version

Tage Johansson <frans.tage@...>
 

Hello,

Do I need visual studio 2017 specificly or is it fine to use visual studio 2019?


Best regards,

Tage


Re: WX.Menu item help text: where is it used?

Brian's Mail list account
 

Well this ere machine is running XP and I have another machine also running it and two more as well. They are not used really on line or in most dangerous environments but do have to run legacy software, and are unupdatable so while they still work, why not?
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!

----- Original Message -----
From: "Luke Davis" <luke@...>
To: <nvda-devel@groups.io>
Sent: Friday, August 30, 2019 8:05 AM
Subject: Re: [nvda-devel] WX.Menu item help text: where is it used?


On Fri, 30 Aug 2019, Brian's Mail list account via Groups.Io wrote:

Why are you using such an old version of nvda, are you using XP?
I knew someone was going to ask me that.:) I was testing add-on compatibility with old versions of NVDA. So I had one of them running when I was looking into that method call. A translations team member asked me to fix a missing translator comment for the text in that call, and it got me wondering where the text was actually going to be used.

I am working on various add-ons that I would like to have available both in 2019.3, and back as far as 2017.3 for those poor souls (or the stubborn holdouts) still using XP or Vista.

Luke

--
Luke Davis
Moderator: the new NVDA Help mailing list! (NVDAHelp+subscribe@groups.io)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)


Re: WX.Menu item help text: where is it used?

Luke Davis
 

On Fri, 30 Aug 2019, Brian's Mail list account via Groups.Io wrote:

Why are you using such an old version of nvda, are you using XP?
I knew someone was going to ask me that.:) I was testing add-on compatibility with old versions of NVDA. So I had one of them running when I was looking into that method call. A translations team member asked me to fix a missing translator comment for the text in that call, and it got me wondering where the text was actually going to be used.

I am working on various add-ons that I would like to have available both in 2019.3, and back as far as 2017.3 for those poor souls (or the stubborn holdouts) still using XP or Vista.

Luke

--
Luke Davis
Moderator: the new NVDA Help mailing list! (NVDAHelp+subscribe@groups.io)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)


Re: WX.Menu item help text: where is it used?

Brian's Mail list account
 

Why are you using such an old version of nvda, are you using XP?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Luke Davis" <luke@...>
To: <nvda-devel@groups.io>
Sent: Friday, August 30, 2019 3:22 AM
Subject: [nvda-devel] WX.Menu item help text: where is it used?


Hello

Perhaps a stupid question, but if I call something like:

gui.mainFrame.sysTrayIcon.preferencesMenu.Append(wx.ID_ANY, _("&menuItemName..."), _("Some descriptive text"))

where will "Some descriptive text" be used?

WX calls this "help", so I thought I would find it in a mouse hover or tooltip of some kind, but in attempting this with both the keyboard and the actual mouse, in NVDA 2017.3, I can not get anything spoken.

The docs for WX.Menu 4.1.0 say:

An optional help string associated with the item. By default, the handler for the wxEVT_MENU_HIGHLIGHT event
displays this string in the status line.

Which helps me not at all.

Thanks

--
Luke Davis
Moderator: the new NVDA Help mailing list! (NVDAHelp+subscribe@groups.io)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)


WX.Menu item help text: where is it used?

Luke Davis
 

Hello

Perhaps a stupid question, but if I call something like:

gui.mainFrame.sysTrayIcon.preferencesMenu.Append(wx.ID_ANY, _("&menuItemName..."), _("Some descriptive text"))

where will "Some descriptive text" be used?

WX calls this "help", so I thought I would find it in a mouse hover or tooltip of some kind, but in attempting this with both the keyboard and the actual mouse, in NVDA 2017.3, I can not get anything spoken.

The docs for WX.Menu 4.1.0 say:

An optional help string associated with the item. By default, the handler for the wxEVT_MENU_HIGHLIGHT event
displays this string in the status line.

Which helps me not at all.

Thanks

--
Luke Davis
Moderator: the new NVDA Help mailing list! (NVDAHelp+subscribe@groups.io)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)


Recommended way of "hiding" certain elements #3030-advice

Toni Barth
 

Hello NVDA Developers,
 
i'm developing an add-on right now to enhance the usability of an application. This application contains at least one table with several cells, but some of those cells, even though they are navigatable by NVDA, contain unimportant information, like the text 'None' or just an icon. I thus wanted to "hide" those cells for the user and tried several ways to do so. I overlayed the table row and override _get_children(), removing the certain children from the list, but I noticed that _get_children() never seems to get executed. I also tried adding states to the specific cells like controlTypes.STATE_INVISIBLE or controlTypes.STATE_UNAVAILABLE, but nothing helped. I also tried moving the focus manually whenever the cell is focused by using event_gainFocus(), but even this seems to mess up things even further.
 
Do you have an idea how to remove those cells from keyboard navigation (not navigator, but at least from tab/arrow keys navigation)?
 
Thanks for your help :).
 
Best Regards.
 
Toni Barth


Re: And finally, for now.

Brian's Mail list account
 

OK then what about this little problem on another windows 7 machine?



Hi folks. I just installed the 3 try version of nvda to stop the explorer crash in windows 7, and of course its too early to tell the outcome of that. However when Windows 7 Home Premium boots up it firstly takes a long time, 11 seconds according to the log, even though the same settings and add ons here at home do not have any issues. Here are the parts of the log that look like issues.

Initializing UIA support
DEBUGWARNING - RPC process 1824 (dwm.exe) (13:01:53.380):
Thread 3364, build\x86_64\remote\injection.cpp, inproc_winEventCallback, 66:
SetWindowsHookEx with WH_GETMESSAGE failed, GetLastError returned 5

DEBUGWARNING - RPC process 1824 (dwm.exe) (13:01:53.381):
Thread 3364, build\x86_64\remote\injection.cpp, inproc_winEventCallback, 69:
SetWindowsHookEx with WH_CALLWNDPROC failed, GetLastError returned 5

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:01:53.629):
UIAutomation: IUIAutomation
DEBUG - core.main (13:01:55.351):

snip
NVDA initialized
DEBUG - core.main (13:01:58.660):
entering wx application main loop
DEBUGWARNING - watchdog._watcher (13:01:59.332):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 221, in <module>
File "core.pyc", line 536, in main
File "wx\core.pyc", line 2134, in MainLoop
File "gui\__init__.pyc", line 997, in Notify
File "core.pyc", line 505, in run
File "IAccessibleHandler.pyc", line 901, in pumpAll
File "IAccessibleHandler.pyc", line 624, in processGenericWinEvent
File "IAccessibleHandler.pyc", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyc", line 42, in getNVDAObjectFromEvent
File "IAccessibleHandler.pyc", line 342, in accessibleObjectFromEvent
File "oleacc.pyc", line 265, in AccessibleObjectFromEvent

DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (13:01:59.472):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
IO - speech.speak (13:01:59.529):
Speaking [LangChangeCommand ('en_GB'), 'NVDA']
IO - inputCore.InputManager.executeGesture (13:02:07.047):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:07.431):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:07.767):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:08.023):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:08.279):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:11.087):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:11.439):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:11.734):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:13.415):
Input: kb(desktop):alt+tab
IO - speech.speak (13:02:13.900):
Speaking [LangChangeCommand ('en_GB'), 'Desktop icon 2 of 2']
IO - speech.speak (13:02:14.174):
Speaking [LangChangeCommand ('en_GB'), 'FolderView list']

As you will note we have the guest appearence of a very old problem from the past, a blank nvda window focussed after boot up of the machine. If I then reboot nvda things seem to work as normal.
Is this a problem that anyone else has had, could it be a windows issue??
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Leonard de Ruijter" <@leonardder>
To: <nvda-devel@groups.io>
Sent: Thursday, August 29, 2019 8:23 AM
Subject: Re: [nvda-devel] And finally, for now.


They have been introduced by the vision framework, I added some
additional debug statements to the window creation there. Nothing to
worry about. These issues were already there, they just weren't logged.



Re: Does alpha snap auto update on windows 7?

ChrisLM
 

Hi, this is an output on Windows version 6.1.7601 service pack 1 workstation with NVDA alpha-18474,2a130565:

{'pendingUpdateAPIVersion': (0, 0, 0), 'pendingUpdateVersionTuple': None, 'dontRemindVersion': 'alpha-18474,2a130565', 'lastCheck': 1567065986.9906137, 'pendingUpdateFile': None, 'pendingUpdateVersion': None, 'pendingUpdateBackCompatToAPIVersion': (0, 0, 0)}


Chris.

In reply to Leonard de Ruijter, 29/08/2019 09:13:

Could you guys please provide the output of the following in a python
console?

import updateCheck; print(updateCheck.state)


Re: And finally, for now.

 

They have been introduced by the vision framework, I added some additional debug statements to the window creation there. Nothing to worry about. These issues were already there, they just weren't logged.


And finally, for now.

Brian's Mail list account
 

On the log produced by the python 3 snapshot we have some log entries near the start which are odd.
DEBUG - windowUtils._rawWindowProc (08:00:49.894):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - windowUtils._rawWindowProc (08:00:49.894):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - windowUtils._rawWindowProc (08:00:49.894):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - windowUtils._rawWindowProc (08:00:49.895):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - core.main (08:00:49.897):
etc.
JUst wondered what they were.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users