Date   
Re: API reference guide for NVDA

Andy B.
 

How does a new addon developer know what to use and when?

 

 

Sent from Mail for Windows 10

 

From: Joseph Lee
Sent: Friday, May 24, 2019 8:40 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] API reference guide for NVDA

 

Hi,

For the last few NVDA releases, I, Derek Riemer and several others provided API docs on our websites. At the moment the latest ones cannot be generated due to certain issues with recent commits.

Cheers,

Joseph

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Andy B.
Sent: Friday, May 24, 2019 5:32 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] API reference guide for NVDA

 

Hi,

 

Is there an up-to-date API reference guide for addon developers? It is difficult knowing what to use and where if there isn’t a developer’s guide out there. The guide should have documentation and sample usage for all classes, methods, attributes, and properties in the NVDA API. It should also answer some difficult to understand concepts such as ‘does object.location tuple consider padding, margins, and content area in its size/dimensions?’ and ‘Does the location tuple in web objects consider the entire desktop and browser window, or only the viewport dimensions?’

 

Thanks for your time and effort.

 

 

Sent from Mail for Windows 10

 

 

Re: API reference guide for NVDA

 

Hi,

For the last few NVDA releases, I, Derek Riemer and several others provided API docs on our websites. At the moment the latest ones cannot be generated due to certain issues with recent commits.

Cheers,

Joseph

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Andy B.
Sent: Friday, May 24, 2019 5:32 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] API reference guide for NVDA

 

Hi,

 

Is there an up-to-date API reference guide for addon developers? It is difficult knowing what to use and where if there isn’t a developer’s guide out there. The guide should have documentation and sample usage for all classes, methods, attributes, and properties in the NVDA API. It should also answer some difficult to understand concepts such as ‘does object.location tuple consider padding, margins, and content area in its size/dimensions?’ and ‘Does the location tuple in web objects consider the entire desktop and browser window, or only the viewport dimensions?’

 

Thanks for your time and effort.

 

 

Sent from Mail for Windows 10

 

API reference guide for NVDA

Andy B.
 

Hi,

 

Is there an up-to-date API reference guide for addon developers? It is difficult knowing what to use and where if there isn’t a developer’s guide out there. The guide should have documentation and sample usage for all classes, methods, attributes, and properties in the NVDA API. It should also answer some difficult to understand concepts such as ‘does object.location tuple consider padding, margins, and content area in its size/dimensions?’ and ‘Does the location tuple in web objects consider the entire desktop and browser window, or only the viewport dimensions?’

 

Thanks for your time and effort.

 

 

Sent from Mail for Windows 10

 

Re: Project : Standalone Element List

Brian's Mail list account
 

If its for embedding in web code then none of it I'd suggest otherwise I'm a bit confused as to what the purpose is, is this for thhe sighted?
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: "Jai Javeria" <jaijaveria16@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, May 22, 2019 5:35 AM
Subject: [nvda-devel] Project : Standalone Element List


Hello Everyone

I am a student from IIT Delhi, India and am currently working on a project
in our Assistech Labs (http://assistech.iitd.ernet.in/). The project
involves making an open source standalone elements list (to list page links
heading and landmarks) for use on web pages. I wanted to use the current
code of NVDA for that and make it standalone. Can someone tell me which
part of the code on Github corresponds to the element list functionality?

Thanking You
Jai Javeria
Undergrad Student
IIT Delhi


Question on overlay classes.

Tom Kingston
 

Hi,

I'm new to NVDA and Python, but not to programming. I'd just like to know if overlay classes are limited to objects that receive focus. They work fine when the object receives focus, however, when I insert an overlay class on a foreground window, it is inserted into clsList, but nothing in the class works and I get an error in the log file for any event.

The reason I'm trying to do this is because I'm writing an add-on for Sound forge. It is an audio editing and mastering suite. It has dozens of plug-in processor windows, most of which use the same window class. Within those windows I need to monitor name and value change for sliders and track bars respectively. Doing so with those events in the main appModule works fine. But of course they're firing on everything. So I have to filter them.

Here's the error I get in the log. This was while testing it in Notepad for the sake of simplicity.

WARNING - eventHandler._EventExecuter.next (22:03:27.665):
Could not execute function event_gainFocus defined in appModules.notepad module; kwargs: {}
Traceback (most recent call last):
File "eventHandler.pyo", line 100, in next
TypeError: event_gainFocus() takes exactly 3 arguments (1 given)
ERROR - eventHandler.executeEvent (22:03:27.665):
error executing event: gainFocus on <NVDAObjects.Dynamic_OpenDialogDialogIAccessibleWindowNVDAObject object at 0x054988F0> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 107, in next
File "extensionPoints\util.pyo", line 175, in callWithSupportedKwargs
TypeError: Parameter required for handler not provided: obj

Thanks much,
Tom

Project : Standalone Element List

Jai Javeria <jaijaveria16@...>
 

Hello Everyone

I am a student from IIT Delhi, India and am currently working on a project in our Assistech Labs (http://assistech.iitd.ernet.in/). The project involves making an open source standalone elements list (to list page links heading and landmarks) for use on web pages. I wanted to use the current code of NVDA for that and make it standalone. Can someone tell me which part of the code on Github corresponds to the element list functionality? 

Thanking You
Jai Javeria
Undergrad Student
IIT Delhi

Re: SPAM-Kerio [nvda-devel] Should latest beta be giving errors with normal add ons?

Brian's Mail list account
 

Yes I know but I think the next upcoming release should still be OK after all all the cutting edge stuff is in threshold and very few add ons work there already, most do on alpha but not as many as beta. All theirs assumes you alter the manifest to allow them to be tested of course.
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: "Bill Dengler" <codeofdusk@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, May 22, 2019 5:02 PM
Subject: Re: SPAM-Kerio [nvda-devel] Should latest beta be giving errors with normal add ons?


There will be many more possibilities for this sort of thing one speech refactor lands.

Bill
On May 22, 2019, at 10:34, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:

I think reading between the lines on what Joseph has said about this add on is that it uses some unusual methods to achieve its aims. I have been emailing the author on the hotmail address given but nothing thus far.
I like this add on due to its stereo capabilities and sounds.
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" <leonard@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, May 22, 2019 12:07 PM
Subject: Re: SPAM-Kerio [nvda-devel] Should latest beta be giving errors with normal add ons?


Thanks for reporting this Brian. I will look into this either today or
tomorrow.


Op 20-5-2019 om 09:39 schreef Brian's Mail list account via Groups.Io:
I notice that whereas for some time now, say sounds manager 3D has
presented some python warnings. from this latest beta snap it has in
effect rendered the add on useless by not allowing it to put its gui
into the menus etc. Its complaining about not being able to import
things so one assumes it just gives up.

DEBUGWARNING - Python warning (08:16:11.428):

C:\nvda release
candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\backend\unspoken\mixer.py:30:
DeprecationWarning: integer argument expected, got float

ERROR - globalPluginHandler.listPlugins (08:16:11.427):

Error importing global plugin audioThemes

Traceback (most recent call last):

File "globalPluginHandler.pyc", line 23, in listPlugins

File "importlib\__init__.pyc", line 37, in import_module

File "C:\nvda release
candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py",
line 23, in <module>

File "C:\nvda release
candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\dialogs\manage_dg.py",
line 17, in <module>

ImportError: cannot import name VoiceSettingsSlider

DEBUG - core.main (08:16:11.446):







Is this deliberate or an accident.

Also as previously mentioned thhere are a number of warnings appearing
which seemingly do not actually seem to affect the use of nvda, but
are nothing to do with add ons as they tend to be still there with add
ons disabled.

Initializing core pump

DEBUG - core.main (08:16:11.447):

Initializing watchdog

DEBUG - core.main (08:16:11.447):

initializing updateCheck

INFO - core.main (08:16:11.447):

NVDA initialized

DEBUG - core.main (08:16:11.447):

entering wx application main loop

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalColumnNumber
(08:16:11.483):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1160, in
_get_presentationalColumnNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalRowNumber
(08:16:11.484):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1111, in
_get_presentationalRowNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

IO - speech.speak (08:16:11.484):

Speaking [LangChangeCommand ('en_GB'), u'Inbox - Outlook Express -
Brians lineone account']

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalColumnNumber
(08:16:11.486):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1160, in
_get_presentationalColumnNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalRowNumber
(08:16:11.486):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1111, in
_get_presentationalRowNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

IO - speech.speak (08:16:11.486):

Speaking [LangChangeCommand ('en_GB'), u'Outlook Express Message List
list']



Now this pops up all over the place with different appications and
sometimes with nothing running at all, and I'm a at a bit of a loss on
what to say if I raise it in a ticket.
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: SPAM-Kerio [nvda-devel] Should latest beta be giving errors with normal add ons?

Bill Dengler
 

There will be many more possibilities for this sort of thing one speech refactor lands.

Bill

On May 22, 2019, at 10:34, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:

I think reading between the lines on what Joseph has said about this add on is that it uses some unusual methods to achieve its aims. I have been emailing the author on the hotmail address given but nothing thus far.
I like this add on due to its stereo capabilities and sounds.
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" <leonard@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, May 22, 2019 12:07 PM
Subject: Re: SPAM-Kerio [nvda-devel] Should latest beta be giving errors with normal add ons?


Thanks for reporting this Brian. I will look into this either today or
tomorrow.


Op 20-5-2019 om 09:39 schreef Brian's Mail list account via Groups.Io:
I notice that whereas for some time now, say sounds manager 3D has
presented some python warnings. from this latest beta snap it has in
effect rendered the add on useless by not allowing it to put its gui
into the menus etc. Its complaining about not being able to import
things so one assumes it just gives up.

DEBUGWARNING - Python warning (08:16:11.428):

C:\nvda release
candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\backend\unspoken\mixer.py:30:
DeprecationWarning: integer argument expected, got float

ERROR - globalPluginHandler.listPlugins (08:16:11.427):

Error importing global plugin audioThemes

Traceback (most recent call last):

File "globalPluginHandler.pyc", line 23, in listPlugins

File "importlib\__init__.pyc", line 37, in import_module

File "C:\nvda release
candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py",
line 23, in <module>

File "C:\nvda release
candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\dialogs\manage_dg.py",
line 17, in <module>

ImportError: cannot import name VoiceSettingsSlider

DEBUG - core.main (08:16:11.446):







Is this deliberate or an accident.

Also as previously mentioned thhere are a number of warnings appearing
which seemingly do not actually seem to affect the use of nvda, but
are nothing to do with add ons as they tend to be still there with add
ons disabled.

Initializing core pump

DEBUG - core.main (08:16:11.447):

Initializing watchdog

DEBUG - core.main (08:16:11.447):

initializing updateCheck

INFO - core.main (08:16:11.447):

NVDA initialized

DEBUG - core.main (08:16:11.447):

entering wx application main loop

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalColumnNumber
(08:16:11.483):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1160, in
_get_presentationalColumnNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalRowNumber
(08:16:11.484):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1111, in
_get_presentationalRowNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

IO - speech.speak (08:16:11.484):

Speaking [LangChangeCommand ('en_GB'), u'Inbox - Outlook Express -
Brians lineone account']

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalColumnNumber
(08:16:11.486):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1160, in
_get_presentationalColumnNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalRowNumber
(08:16:11.486):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1111, in
_get_presentationalRowNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

IO - speech.speak (08:16:11.486):

Speaking [LangChangeCommand ('en_GB'), u'Outlook Express Message List
list']



Now this pops up all over the place with different appications and
sometimes with nothing running at all, and I'm a at a bit of a loss on
what to say if I raise it in a ticket.
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: SPAM-Kerio [nvda-devel] Should latest beta be giving errors with normal add ons?

Brian's Mail list account
 

I think reading between the lines on what Joseph has said about this add on is that it uses some unusual methods to achieve its aims. I have been emailing the author on the hotmail address given but nothing thus far.
I like this add on due to its stereo capabilities and sounds.
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" <leonard@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, May 22, 2019 12:07 PM
Subject: Re: SPAM-Kerio [nvda-devel] Should latest beta be giving errors with normal add ons?


Thanks for reporting this Brian. I will look into this either today or
tomorrow.


Op 20-5-2019 om 09:39 schreef Brian's Mail list account via Groups.Io:
I notice that whereas for some time now, say sounds manager 3D has
presented some python warnings. from this latest beta snap it has in
effect rendered the add on useless by not allowing it to put its gui
into the menus etc. Its complaining about not being able to import
things so one assumes it just gives up.

DEBUGWARNING - Python warning (08:16:11.428):

C:\nvda release
candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\backend\unspoken\mixer.py:30:
DeprecationWarning: integer argument expected, got float

ERROR - globalPluginHandler.listPlugins (08:16:11.427):

Error importing global plugin audioThemes

Traceback (most recent call last):

File "globalPluginHandler.pyc", line 23, in listPlugins

File "importlib\__init__.pyc", line 37, in import_module

File "C:\nvda release
candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py",
line 23, in <module>

File "C:\nvda release
candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\dialogs\manage_dg.py",
line 17, in <module>

ImportError: cannot import name VoiceSettingsSlider

DEBUG - core.main (08:16:11.446):







Is this deliberate or an accident.

Also as previously mentioned thhere are a number of warnings appearing
which seemingly do not actually seem to affect the use of nvda, but
are nothing to do with add ons as they tend to be still there with add
ons disabled.

Initializing core pump

DEBUG - core.main (08:16:11.447):

Initializing watchdog

DEBUG - core.main (08:16:11.447):

initializing updateCheck

INFO - core.main (08:16:11.447):

NVDA initialized

DEBUG - core.main (08:16:11.447):

entering wx application main loop

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalColumnNumber
(08:16:11.483):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1160, in
_get_presentationalColumnNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalRowNumber
(08:16:11.484):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1111, in
_get_presentationalRowNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

IO - speech.speak (08:16:11.484):

Speaking [LangChangeCommand ('en_GB'), u'Inbox - Outlook Express -
Brians lineone account']

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalColumnNumber
(08:16:11.486):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1160, in
_get_presentationalColumnNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_presentationalRowNumber
(08:16:11.486):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1111, in
_get_presentationalRowNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

IO - speech.speak (08:16:11.486):

Speaking [LangChangeCommand ('en_GB'), u'Outlook Express Message List
list']



Now this pops up all over the place with different appications and
sometimes with nothing running at all, and I'm a at a bit of a loss on
what to say if I raise it in a ticket.
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: Speaking ARIA Current Attribute

Jim Homme
 

Hi,

I was partly unclear when I asked the original question. I’m getting familiar on my own with the NVDA source, and wanted to try to read the code that populates the log. I was thinking that if I could find it in the log, I could somehow search for where the code puts it in. Apologies for being non-technical.

 

Jim

 

 

 

==========

Jim Homme

Digital Accessibility

Bender Consulting Services

412-787-8567

https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Reef Turner via Groups.Io
Sent: Wednesday, May 22, 2019 6:58 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Speaking ARIA Current Attribute

 

Not wanting to assume any level of familiarity, I'll just extend on a few things James said.

 

I am assuming you already have considered the logging level set in NVDA, if not look at NVDA general settings panel.

To get to the information that James is talking about, which we call "dev info", press NVDA+F1 this will also open the log viewer.

 

On Fri, 17 May 2019 at 23:17, James Scholes <james@...> wrote:

In the log viewer, you'll find the current page state in the
IAccessible2 attributes.  It's not listed in either the name or
description, because it's not a part of the name or description.  It's a
stateful attribute.

Think of a check box, for an example of a more familiar control.  You
wouldn't want the fact that it was checked or not checked to appear in
the description or name of the control, because then that would appear
to users as text.  Whether a check box is checked, not checked or
half-checked is a part of that control's state, and therefore NVDA
stores and speaks that state appropriately.  Same goes for current page
links, same page links, visited links, headings at a particular level,
and so on.

Regards,

James Scholes

On 17/05/2019 at 3:40 pm, Jim Homme wrote:
> Hi,
>
> By looking at the log I cannot figure out how to examine when NVDA
> speaks the aria-current attribute and I am wondering what other
> information I am missing when doing accessibility testing, so hopefully
> this is the right place to ask, because I am trying to start
> understanding the source and how to get information about what’s going
> on with how things work.
>
> With that preamble out of the way, here is what I did. I went to this page.
>
> https://www.gatsbyjs.org/tutorial/
>
> When I got there, one of the links  said “Current page,” so I tried to
> look in the log to see if I could see that piece of text in the two name
> and description lines. I did not see it.
>
> So next, I right clicked the link in Firefox and chose Inspect Element.
> Once I found the element, I right clicked it in the tree of code
> elements in the developer tools and copied the outer HTML, then brought
> it into my text editor to examine it. This is how I found the
> aria-current=”page” code, which I believe is making NVDA realize that
> the link is visually showing a sighted person that this is the current
> page.
>
> This brings up two questions. Where does NVDA speak this, and why is it
> not in either the name or description areas?
>
> Thanks.
>
>
> Jim
>
> ==========
>
> Jim Homme
>
> Digital Accessibility
>
> Bender Consulting Services
>
> 412-787-8567
>
> https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
>
>



 

--

Reef Turner
Software Developer 

 

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

Image removed by sender.

Re: SPAM-Kerio [nvda-devel] Should latest beta be giving errors with normal add ons?

 

Thanks for reporting this Brian. I will look into this either today or tomorrow.


Op 20-5-2019 om 09:39 schreef Brian's Mail list account via Groups.Io:

I notice that whereas for some time now, say sounds manager 3D has presented some  python warnings. from this latest beta snap it has in effect rendered the add on useless by not allowing it to  put its gui into the menus etc. Its complaining about not being able to import things so one assumes it just gives up.

DEBUGWARNING - Python warning (08:16:11.428):

C:\nvda release candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\backend\unspoken\mixer.py:30: DeprecationWarning: integer argument expected, got float

ERROR - globalPluginHandler.listPlugins (08:16:11.427):

Error importing global plugin audioThemes

Traceback (most recent call last):

File "globalPluginHandler.pyc", line 23, in listPlugins

File "importlib\__init__.pyc", line 37, in import_module

File "C:\nvda release candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py", line 23, in <module>

File "C:\nvda release candidate\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\dialogs\manage_dg.py", line 17, in <module>

ImportError: cannot import name VoiceSettingsSlider

DEBUG - core.main (08:16:11.446):







Is this deliberate or an accident.

Also as previously mentioned thhere are a number of warnings appearing which seemingly do not actually seem to affect the  use of nvda, but are nothing to do with add ons as they tend to be still there with add ons disabled.

Initializing core pump

DEBUG - core.main (08:16:11.447):

Initializing watchdog

DEBUG - core.main (08:16:11.447):

initializing updateCheck

INFO - core.main (08:16:11.447):

NVDA initialized

DEBUG - core.main (08:16:11.447):

entering wx application main loop

DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_presentationalColumnNumber (08:16:11.483):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1160, in _get_presentationalColumnNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_presentationalRowNumber (08:16:11.484):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1111, in _get_presentationalRowNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

IO - speech.speak (08:16:11.484):

Speaking [LangChangeCommand ('en_GB'), u'Inbox - Outlook Express - Brians lineone account']

DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_presentationalColumnNumber (08:16:11.486):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1160, in _get_presentationalColumnNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_presentationalRowNumber (08:16:11.486):

value None is not an int

Traceback (most recent call last):

File "NVDAObjects\IAccessible\__init__.pyc", line 1111, in _get_presentationalRowNumber

TypeError: int() argument must be a string or a number, not 'NoneType'

IO - speech.speak (08:16:11.486):

Speaking [LangChangeCommand ('en_GB'), u'Outlook Express Message List list']



Now this pops up all over the place with different appications and sometimes with nothing running at all, and I'm a at a bit of a loss on what to say if I raise it in a ticket.
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: Speaking ARIA Current Attribute

Reef Turner
 

Not wanting to assume any level of familiarity, I'll just extend on a few things James said.

I am assuming you already have considered the logging level set in NVDA, if not look at NVDA general settings panel.
To get to the information that James is talking about, which we call "dev info", press NVDA+F1 this will also open the log viewer.

On Fri, 17 May 2019 at 23:17, James Scholes <james@...> wrote:
In the log viewer, you'll find the current page state in the
IAccessible2 attributes.  It's not listed in either the name or
description, because it's not a part of the name or description.  It's a
stateful attribute.

Think of a check box, for an example of a more familiar control.  You
wouldn't want the fact that it was checked or not checked to appear in
the description or name of the control, because then that would appear
to users as text.  Whether a check box is checked, not checked or
half-checked is a part of that control's state, and therefore NVDA
stores and speaks that state appropriately.  Same goes for current page
links, same page links, visited links, headings at a particular level,
and so on.

Regards,

James Scholes

On 17/05/2019 at 3:40 pm, Jim Homme wrote:
> Hi,
>
> By looking at the log I cannot figure out how to examine when NVDA
> speaks the aria-current attribute and I am wondering what other
> information I am missing when doing accessibility testing, so hopefully
> this is the right place to ask, because I am trying to start
> understanding the source and how to get information about what’s going
> on with how things work.
>
> With that preamble out of the way, here is what I did. I went to this page.
>
> https://www.gatsbyjs.org/tutorial/
>
> When I got there, one of the links  said “Current page,” so I tried to
> look in the log to see if I could see that piece of text in the two name
> and description lines. I did not see it.
>
> So next, I right clicked the link in Firefox and chose Inspect Element.
> Once I found the element, I right clicked it in the tree of code
> elements in the developer tools and copied the outer HTML, then brought
> it into my text editor to examine it. This is how I found the
> aria-current=”page” code, which I believe is making NVDA realize that
> the link is visually showing a sighted person that this is the current
> page.
>
> This brings up two questions. Where does NVDA speak this, and why is it
> not in either the name or description areas?
>
> Thanks.
>
>
> Jim
>
> ==========
>
> Jim Homme
>
> Digital Accessibility
>
> Bender Consulting Services
>
> 412-787-8567
>
> https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
>
>





--
Reef Turner
Software Developer 
 


Re: Creating a keyboard layered mode such as inputhelpmode

David Moore
 

Hi!

It is on the NVDA add-on page, the one that comes up from the tools menu for getting add-ons.

At least it was there a few months ago.

Just check that page, and see if it is still there.

It has a stop watch, an alarm you can set, and you can set it to say the time as often as you want.

David Moore

 

                                                                Sent from Mail for Windows 10

 

From: Andy B.
Sent: Tuesday, May 21, 2019 5:47 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Creating a keyboard layered mode such as inputhelpmode

 

What clock? Do you have a link for it?

 

 

Sent from Mail for Windows 10

 

From: David Moore
Sent: Tuesday, May 21, 2019 5:10 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Creating a keyboard layered mode such as input helpmode

 

Hi!

What is the new add-on!

I am so curious to use add-ons that have the layered mode.

The only one I use now is the Clock.

Have a great one, and thanks so much, you guys, for making all of these great add-ons!

David Moore

 

                                                                Sent from Mail for Windows 10

 

From: Andy B.
Sent: Tuesday, May 21, 2019 12:13 AM
To: nvda-devel@groups.io
Subject: [nvda-devel] Creating a keyboard layered mode such as input help mode

 

Hi,

I am developing a new addon which requires the use of a layered mode such as input help mode. Can someone advise on how to create something similar in a global plugin?

 

 

 

Re: Creating a keyboard layered mode such as input helpmode

Andy B.
 

What clock? Do you have a link for it?

 

 

Sent from Mail for Windows 10

 

From: David Moore
Sent: Tuesday, May 21, 2019 5:10 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Creating a keyboard layered mode such as input helpmode

 

Hi!

What is the new add-on!

I am so curious to use add-ons that have the layered mode.

The only one I use now is the Clock.

Have a great one, and thanks so much, you guys, for making all of these great add-ons!

David Moore

 

                                                                Sent from Mail for Windows 10

 

From: Andy B.
Sent: Tuesday, May 21, 2019 12:13 AM
To: nvda-devel@groups.io
Subject: [nvda-devel] Creating a keyboard layered mode such as input help mode

 

Hi,

I am developing a new addon which requires the use of a layered mode such as input help mode. Can someone advise on how to create something similar in a global plugin?

 

 

Re: Creating a keyboard layered mode such as input help mode

David Moore
 

Hi!

What is the new add-on!

I am so curious to use add-ons that have the layered mode.

The only one I use now is the Clock.

Have a great one, and thanks so much, you guys, for making all of these great add-ons!

David Moore

 

                                                                Sent from Mail for Windows 10

 

From: Andy B.
Sent: Tuesday, May 21, 2019 12:13 AM
To: nvda-devel@groups.io
Subject: [nvda-devel] Creating a keyboard layered mode such as input help mode

 

Hi,

I am developing a new addon which requires the use of a layered mode such as input help mode. Can someone advise on how to create something similar in a global plugin?

 

Re: Assunto: [nvda-devel] Creating a keyboard layered mode such asinput help mode [nvda-devel] Creating a keyboard layered mode such as inputhelp mode

Andy B.
 

Hi Rui,

 

Thanks for this. I will check it out and try things out a little. Will get back with you in the event it doesn’t work.

 

 

Sent from Mail for Windows 10

 

From: Rui Fontes
Sent: Tuesday, May 21, 2019 10:06 AM
To: nvda-devel@groups.io
Subject: Re: Assunto: [nvda-devel] Creating a keyboard layered mode such asinput help mode [nvda-devel] Creating a keyboard layered mode such as inputhelp mode

 

Hello Andy!

 

Here a message about that...

 

Rui Fontes

 

 

-------- Mensagem reencaminhada --------

Assunto:           Re: [nvda-addons] Reflection concerning layered commands

Data:    Mon, 13 May 2019 08:46:39 +0200

De:       Abdel <abdelkrim.bensaid@...>

Responder-Para:          nvda-addons@nvda-addons.groups.io

Para:    nvda-addons@nvda-addons.groups.io

 

 

 

Hi Joseph,

 

Thank you for your tests and remarks.

 

At this point, the globalPlugin I sent does not call the finish method

separately from the layer command, as the Tyler finally_ function does.

 

The developer must therefore introduce the call of the finish method in

the script representing the layered command.

 

If the script representing the layered command can not contain the call

to the finish method, (eg: called from another module), you must either

use the Tyler finally_ function, or follow the syntax used in this new

attached globalPlugin, which supports this case.

 

In any case, I think that it is not really necessary to use the try /

finally clause used by the Tyler's finally_ function.

 

For add-on developers whose use layered commands, I think that a naming

convention for scripts should be used (eg: scriptlayerSomething).

 

This should make it easier to distinguish standard scripts from those

belonging to a layered command.

 

Of course, this would only apply if the layer command is introduced in

the add-on and does not come from an external module.

 

Thanks.

 

Kind regards,

Abdel.

 

Le 12/05/2019 à 18:47, Joseph Lee a écrit :

> Hi,

> In theory, it works.

> Tyler (if you are here), any thoughts?

> Cheers,

> Joseph

> *From:*nvda-addons@nvda-addons.groups.io

> <nvda-addons@nvda-addons.groups.io> *On Behalf Of *Abdel

> *Sent:* Sunday, May 12, 2019 5:25 AM

> *To:* nvda-addons@nvda-addons.groups.io

> *Subject:* Re: [nvda-addons] Reflection concerning layered commands

> Hi Luke, Derek, Joseph and all,

> I think I found the solution, the corrected globalPlugin is attached.

> The exception has been removed, I think we don't have a real need to

> use it.

> @Derek:

> Thank you for your suggestion, I put only one script to represent all

> the letters of the alphabet, from a to z.

> @Joseph:

> Can you confirm if this version is correct for you?

> Thanks again for your help.

> Kind regards,

> Abdel.

> Le 12/05/2019 à 06:23, derek riemer a écrit :

>     NVDA requires it. You are supposed to define all scripts as follows.

>     def script_something(self, gesture) even if you don't use the

>     gesture. NVDA passes the gesture in either way, and naming

>     something script_error, but then not making it accept a gesture

>     would really confuse things and could acause errors if someone

>     decided to bind a gesture to it.

>     On Sat, May 11, 2019 at 12:26 PM Luke Davis

>     <luke@... <mailto:luke@...>> wrote:

>         Hi Abdel

>         Perhaps I am missing some intricacy of the passing structure

>         here, but why are

>         you passing gesture to script_error? It never does anything

>         with it. Is this

>         future proofing? Or is there another reason I'm not understanding?

>         Unless script_error is just a placeholder for your actual next

>         step method as

>         you develop whatever this is?

>         def script_error(self, gesture):

>           tones.beep(120, 100)

>         Luke

>     --

>     Derek Riemer

>     Improving the world one byte at a time! ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖

>     •    Accessibility enthusiast.

>     •    Proud user of the NVDA screen reader.

>     •    Open source enthusiast.

>     •    Skier.

>     •    Personal website: https://derekriemer.com

 

 

 

 

Re: Assunto: [nvda-devel] Creating a keyboard layered mode such as input help mode [nvda-devel] Creating a keyboard layered mode such as input help mode

Rui Fontes
 

Hello Andy!

Here a message about that...

Rui Fontes


-------- Mensagem reencaminhada --------
Assunto: Re: [nvda-addons] Reflection concerning layered commands
Data: Mon, 13 May 2019 08:46:39 +0200
De: Abdel <abdelkrim.bensaid@...>
Responder-Para: nvda-addons@nvda-addons.groups.io
Para: nvda-addons@nvda-addons.groups.io



Hi Joseph,

Thank you for your tests and remarks.

At this point, the globalPlugin I sent does not call the finish method separately from the layer command, as the Tyler finally_ function does.

The developer must therefore introduce the call of the finish method in the script representing the layered command.

If the script representing the layered command can not contain the call to the finish method, (eg: called from another module), you must either use the Tyler finally_ function, or follow the syntax used in this new attached globalPlugin, which supports this case.

In any case, I think that it is not really necessary to use the try / finally clause used by the Tyler's finally_ function.

For add-on developers whose use layered commands, I think that a naming convention for scripts should be used (eg: scriptlayerSomething).

This should make it easier to distinguish standard scripts from those belonging to a layered command.

Of course, this would only apply if the layer command is introduced in the add-on and does not come from an external module.

Thanks.

Kind regards,
Abdel.

Le 12/05/2019 à 18:47, Joseph Lee a écrit :

Hi,

In theory, it works.

Tyler (if you are here), any thoughts?

Cheers,

Joseph

*From:*nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> *On Behalf Of *Abdel
*Sent:* Sunday, May 12, 2019 5:25 AM
*To:* nvda-addons@nvda-addons.groups.io
*Subject:* Re: [nvda-addons] Reflection concerning layered commands

Hi Luke, Derek, Joseph and all,

I think I found the solution, the corrected globalPlugin is attached.

The exception has been removed, I think we don't have a real need to use it.

@Derek:

Thank you for your suggestion, I put only one script to represent all the letters of the alphabet, from a to z.

@Joseph:

Can you confirm if this version is correct for you?

Thanks again for your help.

Kind regards,
Abdel.

Le 12/05/2019 à 06:23, derek riemer a écrit :

NVDA requires it. You are supposed to define all scripts as follows.

def script_something(self, gesture) even if you don't use the
gesture. NVDA passes the gesture in either way, and naming
something script_error, but then not making it accept a gesture
would really confuse things and could acause errors if someone
decided to bind a gesture to it.

On Sat, May 11, 2019 at 12:26 PM Luke Davis
<luke@... <mailto:luke@...>> wrote:

Hi Abdel

Perhaps I am missing some intricacy of the passing structure
here, but why are
you passing gesture to script_error? It never does anything
with it. Is this
future proofing? Or is there another reason I'm not understanding?
Unless script_error is just a placeholder for your actual next
step method as
you develop whatever this is?

def script_error(self, gesture):
  tones.beep(120, 100)

Luke


--

Derek Riemer
Improving the world one byte at a time! ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com


Re: how to start to lokk at sources of nvda

Roberto Burceni <roberto@...>
 

Hello Harnold,
Thank you for your email.
At this time I’m learning basics of python and this seems not so difficult. I’m already a developer but at this time only for web with php and I learned some years ago C language. So I hope to learn python qucly.
Thank you for your suggestions.
Best regards

Il giorno 20 mag 2019, alle ore 21:57, Arnold Loubriat <@DataTriny> ha scritto:

Hi Roberto and welcome,
If you are still beginning to learn Python, I would recommend that you first sharpen your programming skills before diving into NVDA's source code.
It is a fairly large code base and you will spend tons of hours finding where a particular feature is implemented.
When you feel that you have a good understanding of the Python programming language, I would suggest to take a quick look at Git and text searching tools (I personnally use ripgrep on Windows).
Finally, if you are interested in Braille in particular, you can have a look at liblouis as well as some display devices protocols.
But, as I said, make sure that you really know Python before going forward because NVDA's source code doesn't always make use of good practices. We are all trying to reach this goal and some pieces of the software are well designed, but it will take you a bit of experience to actually discover it.
Regards,

Arnold

Creating a keyboard layered mode such as input help mode

Andy B.
 

Hi,

I am developing a new addon which requires the use of a layered mode such as input help mode. Can someone advise on how to create something similar in a global plugin?

Re: how to start to lokk at sources of nvda

Arnold Loubriat
 

Hi Roberto and welcome,
If you are still beginning to learn Python, I would recommend that you first sharpen your programming skills before diving into NVDA's source code.
It is a fairly large code base and you will spend tons of hours finding where a particular feature is implemented.
When you feel that you have a good understanding of the Python programming language, I would suggest to take a quick look at Git and text searching tools (I personnally use ripgrep on Windows).
Finally, if you are interested in Braille in particular, you can have a look at liblouis as well as some display devices protocols.
But, as I said, make sure that you really know Python before going forward because NVDA's source code doesn't always make use of good practices. We are all trying to reach this goal and some pieces of the software are well designed, but it will take you a bit of experience to actually discover it.
Regards,

Arnold