Date   
Re: Project : Standalone Element List

James Scholes
 

NVDA is open source, you're very welcome to obtain the code and read through it for yourself. I'm not sure how much it will help; NVDA is written in Python and browser extensions are not.

Regards,

James Scholes

On 27/05/2019 at 7:13 am, Jai Javeria wrote:
Dear Sir
I plan to make an extension on web browsers for this.
Yes, it is for sighted persons, who want to have an overview of the webpage. Especially for persons with low vision who have tunnel vision.
If you could give me some insights.
Thanks and regards
Jai Javeria
Undergrad Student
IIT Delhi
On Thu, May 23, 2019 at 9:52 PM Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io <mailto:blueyonder.co.uk@groups.io>> wrote:
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@... <mailto:bglists@...>
Sent via blueyonder.
Please address personal E-mail to:-
briang1@... <mailto:briang1@...>, putting
'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Jai Javeria" <jaijaveria16@...
<mailto:jaijaveria16@...>>
To: <nvda-devel@groups.io <mailto: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
>
>
>
>

Re: Project : Standalone Element List

Jai Javeria <jaijaveria16@...>
 

Dear Sir 

I plan to make an extension on web browsers for this. 
Yes, it is for sighted persons, who want to have an overview of the webpage. Especially for persons with low vision who have tunnel vision.

If you could give me some insights.

Thanks and regards
Jai Javeria
Undergrad Student
IIT Delhi
 


On Thu, May 23, 2019 at 9:52 PM Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
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
>
>
>
>




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

Brian's Mail list account
 


At the moment if it gets fixed I cannot test it as my main computer died on Friday, suspect SSD death, so until I get it back and reconfigured I'm stuck in Windows xp and so cannot test any snapshots or add ons etc, sadly.
 
Bah humbug. 
Does not help that its a bank holiday Monday tomorrow either! 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 -----
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



Can we reclass an unknown object?

Tom Kingston
 

I have a check list (a list box with check boxes on each list item) which is a custom control. Is there a way to tell NVDA to treat this like a list box? If not, any help on how I should tackle this would be greatly appreciated.

Regards,
Tom

Re: API reference guide for NVDA

DaVid
 

Yes, good api documentation is lacking in NVDA I think. But the code
usually is easy to read and learn things. Also you can see another
add-ons code to get examples.
When I used NVDA first times many years ago... I quickly developed a
synth driver, I learned python by developing it, I came from C. I
wasn't an expert (just a high school teenager) and I'm not an expert
yet.
Also I'm not good in english language, another barrier for me.
Another screen readers have good documentation, but you can't see
their source code. Well commented and clean Source code is better than
documentation, ideally we should have both... But NVDA is free, and
the developers have their priorities.
The world is not perfect, but I just saying that develop for NVDA is
easy even for unexperienced developers.

When I am developing an add-on, I usually look at the related code for
my add-on. If I need to work with the keyboard then keyboardHandler,
gestures, ETC... If need to work with audio then read nvwave, tones,
ETC...
If I need to implement a COM interface I can see examples already in
the NVDA code. The same for MSAA, IA2, UIA, IPC...

Load NVDA in eclipse is a good way to read the code easily because you
can jump between code instructions. But if you don't want to use
eclipse or another ide, you can use windows explorer, notepad++ and
files finder to look for a specific code.
NVDA has a good code structure.

And the last resource, you can ask here and in another NVDA development lists.

Regards,
DaVid.

Re: API reference guide for NVDA

Andy B.
 

True. I am not a beginner to programming since I have a B.S. in the matter. However, no useful API reference for a completely unfamiliar API doesn’t lend help to anyone unless they’ve already used it for quite a while.

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

I think this advice would work for intermediate to advanced users, but not necessarily for beginners. Beginners may need to know certain top-level info about classes, methods, and example usage so they can experiment with things here and there.

Cheers,

Joseph

 

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

 

Just look into source code,the API doc does not provide much information.

On 2019/5/25 10:00, Andy B. wrote:

What should I do in the meantime?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Hopefully, before 2019.2 comes out, but can’t guarantee it all the way.

Cheers,

Joseph

 

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

 

Will they fix it?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Regarding API docs, that’s something I agree. At the moment, after introduction of abstract methods and some more recent commits in 2019.1 development cycle, it isn’t possible to build API docs from source code, something NV Access people were notified.

As for discussing this, I think this list would be fine.

Cheers,

Joseph

 

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

 

Hi again,

 

I read the addons developer guide for 19.1.1 and the design/internals documents for NVDA itself. I know Python well enough to build things. However, the lack of an NVDA API reference guide gets new addon developers stuck. The developer guides are good enough to get people started with simple things, but once someone gets past that, there is no more guidance. We need to come up with something other than experimenting around with API calls because it is a large waste of time to a point. I would like to continue talking about this problem. Where should we continue?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Typically, I and others recommend people to learn Python first, but since some did learn Python and are proficient at it, we usually recommend reading the NVDA development guide, and the add-on development guide for certain tasks not covered in the NVDA dev guide.

I do realize that this is the same answer you may have received on add-ons list, which demonstrates that we may need to think critically about the current state of API documentation and surrounding literature.

Cheers,

Joseph

 

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

 

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,

I think this advice would work for intermediate to advanced users, but not necessarily for beginners. Beginners may need to know certain top-level info about classes, methods, and example usage so they can experiment with things here and there.

Cheers,

Joseph

 

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

 

Just look into source code,the API doc does not provide much information.

On 2019/5/25 10:00, Andy B. wrote:

What should I do in the meantime?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Hopefully, before 2019.2 comes out, but can’t guarantee it all the way.

Cheers,

Joseph

 

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

 

Will they fix it?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Regarding API docs, that’s something I agree. At the moment, after introduction of abstract methods and some more recent commits in 2019.1 development cycle, it isn’t possible to build API docs from source code, something NV Access people were notified.

As for discussing this, I think this list would be fine.

Cheers,

Joseph

 

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

 

Hi again,

 

I read the addons developer guide for 19.1.1 and the design/internals documents for NVDA itself. I know Python well enough to build things. However, the lack of an NVDA API reference guide gets new addon developers stuck. The developer guides are good enough to get people started with simple things, but once someone gets past that, there is no more guidance. We need to come up with something other than experimenting around with API calls because it is a large waste of time to a point. I would like to continue talking about this problem. Where should we continue?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Typically, I and others recommend people to learn Python first, but since some did learn Python and are proficient at it, we usually recommend reading the NVDA development guide, and the add-on development guide for certain tasks not covered in the NVDA dev guide.

I do realize that this is the same answer you may have received on add-ons list, which demonstrates that we may need to think critically about the current state of API documentation and surrounding literature.

Cheers,

Joseph

 

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

 

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

Larry Wang
 

Just look into source code,the API doc does not provide much information.

On 2019/5/25 10:00, Andy B. wrote:

What should I do in the meantime?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Hopefully, before 2019.2 comes out, but can’t guarantee it all the way.

Cheers,

Joseph

 

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

 

Will they fix it?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Regarding API docs, that’s something I agree. At the moment, after introduction of abstract methods and some more recent commits in 2019.1 development cycle, it isn’t possible to build API docs from source code, something NV Access people were notified.

As for discussing this, I think this list would be fine.

Cheers,

Joseph

 

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

 

Hi again,

 

I read the addons developer guide for 19.1.1 and the design/internals documents for NVDA itself. I know Python well enough to build things. However, the lack of an NVDA API reference guide gets new addon developers stuck. The developer guides are good enough to get people started with simple things, but once someone gets past that, there is no more guidance. We need to come up with something other than experimenting around with API calls because it is a large waste of time to a point. I would like to continue talking about this problem. Where should we continue?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Typically, I and others recommend people to learn Python first, but since some did learn Python and are proficient at it, we usually recommend reading the NVDA development guide, and the add-on development guide for certain tasks not covered in the NVDA dev guide.

I do realize that this is the same answer you may have received on add-ons list, which demonstrates that we may need to think critically about the current state of API documentation and surrounding literature.

Cheers,

Joseph

 

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

 

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,

In the meantime, you can view the 2018.4 API docs located on my website at:

https://www.josephsl.net/files/nvdadocs/dev/

Although it is not that recent, it is quite comparable to current API set we’ve got.

Cheers,

Joseph

 

 

 

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

 

What should I do in the meantime?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Hopefully, before 2019.2 comes out, but can’t guarantee it all the way.

Cheers,

Joseph

 

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

 

Will they fix it?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Regarding API docs, that’s something I agree. At the moment, after introduction of abstract methods and some more recent commits in 2019.1 development cycle, it isn’t possible to build API docs from source code, something NV Access people were notified.

As for discussing this, I think this list would be fine.

Cheers,

Joseph

 

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

 

Hi again,

 

I read the addons developer guide for 19.1.1 and the design/internals documents for NVDA itself. I know Python well enough to build things. However, the lack of an NVDA API reference guide gets new addon developers stuck. The developer guides are good enough to get people started with simple things, but once someone gets past that, there is no more guidance. We need to come up with something other than experimenting around with API calls because it is a large waste of time to a point. I would like to continue talking about this problem. Where should we continue?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Typically, I and others recommend people to learn Python first, but since some did learn Python and are proficient at it, we usually recommend reading the NVDA development guide, and the add-on development guide for certain tasks not covered in the NVDA dev guide.

I do realize that this is the same answer you may have received on add-ons list, which demonstrates that we may need to think critically about the current state of API documentation and surrounding literature.

Cheers,

Joseph

 

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

 

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

Andy B.
 

What should I do in the meantime?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Hopefully, before 2019.2 comes out, but can’t guarantee it all the way.

Cheers,

Joseph

 

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

 

Will they fix it?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Regarding API docs, that’s something I agree. At the moment, after introduction of abstract methods and some more recent commits in 2019.1 development cycle, it isn’t possible to build API docs from source code, something NV Access people were notified.

As for discussing this, I think this list would be fine.

Cheers,

Joseph

 

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

 

Hi again,

 

I read the addons developer guide for 19.1.1 and the design/internals documents for NVDA itself. I know Python well enough to build things. However, the lack of an NVDA API reference guide gets new addon developers stuck. The developer guides are good enough to get people started with simple things, but once someone gets past that, there is no more guidance. We need to come up with something other than experimenting around with API calls because it is a large waste of time to a point. I would like to continue talking about this problem. Where should we continue?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Typically, I and others recommend people to learn Python first, but since some did learn Python and are proficient at it, we usually recommend reading the NVDA development guide, and the add-on development guide for certain tasks not covered in the NVDA dev guide.

I do realize that this is the same answer you may have received on add-ons list, which demonstrates that we may need to think critically about the current state of API documentation and surrounding literature.

Cheers,

Joseph

 

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

 

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,

Hopefully, before 2019.2 comes out, but can’t guarantee it all the way.

Cheers,

Joseph

 

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

 

Will they fix it?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Regarding API docs, that’s something I agree. At the moment, after introduction of abstract methods and some more recent commits in 2019.1 development cycle, it isn’t possible to build API docs from source code, something NV Access people were notified.

As for discussing this, I think this list would be fine.

Cheers,

Joseph

 

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

 

Hi again,

 

I read the addons developer guide for 19.1.1 and the design/internals documents for NVDA itself. I know Python well enough to build things. However, the lack of an NVDA API reference guide gets new addon developers stuck. The developer guides are good enough to get people started with simple things, but once someone gets past that, there is no more guidance. We need to come up with something other than experimenting around with API calls because it is a large waste of time to a point. I would like to continue talking about this problem. Where should we continue?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Typically, I and others recommend people to learn Python first, but since some did learn Python and are proficient at it, we usually recommend reading the NVDA development guide, and the add-on development guide for certain tasks not covered in the NVDA dev guide.

I do realize that this is the same answer you may have received on add-ons list, which demonstrates that we may need to think critically about the current state of API documentation and surrounding literature.

Cheers,

Joseph

 

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

 

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

Andy B.
 

Will they fix it?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Regarding API docs, that’s something I agree. At the moment, after introduction of abstract methods and some more recent commits in 2019.1 development cycle, it isn’t possible to build API docs from source code, something NV Access people were notified.

As for discussing this, I think this list would be fine.

Cheers,

Joseph

 

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

 

Hi again,

 

I read the addons developer guide for 19.1.1 and the design/internals documents for NVDA itself. I know Python well enough to build things. However, the lack of an NVDA API reference guide gets new addon developers stuck. The developer guides are good enough to get people started with simple things, but once someone gets past that, there is no more guidance. We need to come up with something other than experimenting around with API calls because it is a large waste of time to a point. I would like to continue talking about this problem. Where should we continue?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Typically, I and others recommend people to learn Python first, but since some did learn Python and are proficient at it, we usually recommend reading the NVDA development guide, and the add-on development guide for certain tasks not covered in the NVDA dev guide.

I do realize that this is the same answer you may have received on add-ons list, which demonstrates that we may need to think critically about the current state of API documentation and surrounding literature.

Cheers,

Joseph

 

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

 

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,

Regarding API docs, that’s something I agree. At the moment, after introduction of abstract methods and some more recent commits in 2019.1 development cycle, it isn’t possible to build API docs from source code, something NV Access people were notified.

As for discussing this, I think this list would be fine.

Cheers,

Joseph

 

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

 

Hi again,

 

I read the addons developer guide for 19.1.1 and the design/internals documents for NVDA itself. I know Python well enough to build things. However, the lack of an NVDA API reference guide gets new addon developers stuck. The developer guides are good enough to get people started with simple things, but once someone gets past that, there is no more guidance. We need to come up with something other than experimenting around with API calls because it is a large waste of time to a point. I would like to continue talking about this problem. Where should we continue?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Typically, I and others recommend people to learn Python first, but since some did learn Python and are proficient at it, we usually recommend reading the NVDA development guide, and the add-on development guide for certain tasks not covered in the NVDA dev guide.

I do realize that this is the same answer you may have received on add-ons list, which demonstrates that we may need to think critically about the current state of API documentation and surrounding literature.

Cheers,

Joseph

 

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

 

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

Andy B.
 

Hi again,

 

I read the addons developer guide for 19.1.1 and the design/internals documents for NVDA itself. I know Python well enough to build things. However, the lack of an NVDA API reference guide gets new addon developers stuck. The developer guides are good enough to get people started with simple things, but once someone gets past that, there is no more guidance. We need to come up with something other than experimenting around with API calls because it is a large waste of time to a point. I would like to continue talking about this problem. Where should we continue?

 

 

Sent from Mail for Windows 10

 

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

 

Hi,

Typically, I and others recommend people to learn Python first, but since some did learn Python and are proficient at it, we usually recommend reading the NVDA development guide, and the add-on development guide for certain tasks not covered in the NVDA dev guide.

I do realize that this is the same answer you may have received on add-ons list, which demonstrates that we may need to think critically about the current state of API documentation and surrounding literature.

Cheers,

Joseph

 

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

 

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,

Typically, I and others recommend people to learn Python first, but since some did learn Python and are proficient at it, we usually recommend reading the NVDA development guide, and the add-on development guide for certain tasks not covered in the NVDA dev guide.

I do realize that this is the same answer you may have received on add-ons list, which demonstrates that we may need to think critically about the current state of API documentation and surrounding literature.

Cheers,

Joseph

 

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

 

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

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