Date   

NVDA Developer Guide: Question about how to make addons using standard NotePad

Daniel Gartmann <lists@...>
 

Hi,

I tried to find information about how to make an add-on using the built-in Notepad application instead of having to install NotePad++.

The use case is as follows:
You go to another person’s computer to make NVDA behave better for that particular user in a specific situation.

Other screenreaders have built-in script editors e.g the JAWS Script Editor. But when using NVDA, we are told to use NotePad++.

It is, however, not possible to install NotePad++ if, for instance, you are in a corporate environment or some other restricted setting.

So. What is the procedure to make a .py file in Notepad and save it in the correct format?

Could it be included in the NVDA Developer guide?

Just a suggestion so that NVDA’s customizations can be made easier in more places.

Daniel


Re: focusHighlight 6.1

Noelia Ruiz
 

Let's add this tag to organize and find messages easily

Thanks

El 09/06/2019 a las 17:38, Noelia Ruiz via Groups.Io escribió:
Hi, I have updated the documentation on the website, in the translations repo.
Please, check if all is OK.
Cheers
El 09/06/2019 a las 14:42, Takuya Nishimoto escribió:
focusHighlight 6.1 is out.

Please update the community site and the add-on update tool regarding this.

download:

https://github.com/nvdajp/focusHighlight/releases/download/6.1/focusHighlight-6.1.nvda-addon

release page:

https://github.com/nvdajp/focusHighlight/releases/tag/6.1

## Changes for 6.1 ##

* New and updated translations.
* Addresses the issue with the latest development versions of NVDA.
* Focus Highlight category of NVDA Settings dialog is now available.
Note that it works only with NVDA 2018.3 or later.

When Focus Highlight category of NVDA Settings dialog is available,
following items can be used.

* Make focus mode the default: This checkbox is enabled by default.
When it is unchecked, this add-on behaves same as version 5.6 or
previous versions, i.e., if browse mode is not available for an app,
the focus is shown using the thick red rectangle.
* Focus in focus mode, Focus in browse mode, Navigator object: Each of
these groups contains Color, Thickness, and Style.
* Color: This edit field allows you to type the HTML color code, i.e.,
six-character hexadecimal number. For example, "ffffff" is white,
"ff0000" is red, and so on. Note that "000000" can not be used.
* Thickness: This edit field allows you to type the thickness of the
box. You can enter a value between 1 and 30.
* Style: The choices are Solid, Dash, Dot, Dash dot, and Dash dot-dot.
* Restore defaults: This button allows you to reset your settings to
their original defaults.


--
Takuya Nishimoto
nishimotz@gmail.com



Re: focusHighlight 6.1

Noelia Ruiz
 

Hi, I have updated the documentation on the website, in the translations repo.
Please, check if all is OK.

Cheers

El 09/06/2019 a las 14:42, Takuya Nishimoto escribió:
focusHighlight 6.1 is out.
Please update the community site and the add-on update tool regarding this.
download:
https://github.com/nvdajp/focusHighlight/releases/download/6.1/focusHighlight-6.1.nvda-addon
release page:
https://github.com/nvdajp/focusHighlight/releases/tag/6.1
## Changes for 6.1 ##
* New and updated translations.
* Addresses the issue with the latest development versions of NVDA.
* Focus Highlight category of NVDA Settings dialog is now available.
Note that it works only with NVDA 2018.3 or later.
When Focus Highlight category of NVDA Settings dialog is available,
following items can be used.
* Make focus mode the default: This checkbox is enabled by default.
When it is unchecked, this add-on behaves same as version 5.6 or
previous versions, i.e., if browse mode is not available for an app,
the focus is shown using the thick red rectangle.
* Focus in focus mode, Focus in browse mode, Navigator object: Each of
these groups contains Color, Thickness, and Style.
* Color: This edit field allows you to type the HTML color code, i.e.,
six-character hexadecimal number. For example, "ffffff" is white,
"ff0000" is red, and so on. Note that "000000" can not be used.
* Thickness: This edit field allows you to type the thickness of the
box. You can enter a value between 1 and 30.
* Style: The choices are Solid, Dash, Dot, Dash dot, and Dash dot-dot.
* Restore defaults: This button allows you to reset your settings to
their original defaults.
--
Takuya Nishimoto
nishimotz@gmail.com


Defining events on objects.

Andy B.
 

Hi,


I need to change object.hasFocus to True whenever an object gains focus. Then change it to False when it loses focus. I read somewhere in the NVDA 2019 addon developer guide that you can define object level events. Unfortunately, the short explanation didn't do much for help. Does someone have an example of how this works? I also noticed that there is an event_gainFocus, but no event_loseFocus. How do you tell when something loses focus?


Re: Testing for root of dom in Firefox

Andy B.
 

Hi,


I figured this out. There is a treeInterceptor object called rootNVDAObject which gets the root element as an nvda object. It also has rootID and rootIdentifiers.

On 6/9/2019 7:32 AM, Alberto Buffolino wrote:
Andy B., il 08/06/2019 20.19, ha scritto:
Unfortunately, I have no way of checking for the root element in a web document. Does anyone have any ideas? I am strictly using Firefox at this time. It appears everything is a mozilla.Mozilla object... Any help would be appreciated because I am stuck.
Alberto:
Hi Andy,
I'm not sure if it's useful, but you can check the role, which should be controlTypes.ROLE_DOCUMENT.
Or investigating about ISimpleDOM, I think ISimpleDOMDocument interface would have a method to get document root object.
Alberto


Re: NVDA beep when power status changes?

DaVid
 

Hi, I created the add-on for sound notiffication (currently supports
beeping only) and I will send it for review after some testing.
Although I don't think it need a lot of review because basically I
copied the NVDA core functionality for this add-on and replaced voice
messages by thones.beep.

Regards,
DaVid.

2019-06-09 6:42 GMT-06:00, DaVid via Groups.Io <dhf360=gmail.com@groups.io>:

On windows, sighted people can see the power status led. On android
and iOs, those notiffications are by sound also, with the option to
disable them.

MessageWindow can't be subclassed, extending from
windowUtils.CustomWindow is the way to go with an add-on I think.
I don't wanted to duply a functionality in add-on, since it is already
in NVDA but with voice. If I create an add-on, I could add sound
notifffication but I can't disable voice notification.
The options for this setting could be:
Disabled: NVDA doesn't announce power status changes at all.
Voice.
Tones.
Voice and tones.

With default setting in voice.

Regards,
DaVid.




focusHighlight 6.1

Takuya Nishimoto
 

focusHighlight 6.1 is out.

Please update the community site and the add-on update tool regarding this.

download:

https://github.com/nvdajp/focusHighlight/releases/download/6.1/focusHighlight-6.1.nvda-addon

release page:

https://github.com/nvdajp/focusHighlight/releases/tag/6.1

## Changes for 6.1 ##

* New and updated translations.
* Addresses the issue with the latest development versions of NVDA.
* Focus Highlight category of NVDA Settings dialog is now available.
Note that it works only with NVDA 2018.3 or later.

When Focus Highlight category of NVDA Settings dialog is available,
following items can be used.

* Make focus mode the default: This checkbox is enabled by default.
When it is unchecked, this add-on behaves same as version 5.6 or
previous versions, i.e., if browse mode is not available for an app,
the focus is shown using the thick red rectangle.
* Focus in focus mode, Focus in browse mode, Navigator object: Each of
these groups contains Color, Thickness, and Style.
* Color: This edit field allows you to type the HTML color code, i.e.,
six-character hexadecimal number. For example, "ffffff" is white,
"ff0000" is red, and so on. Note that "000000" can not be used.
* Thickness: This edit field allows you to type the thickness of the
box. You can enter a value between 1 and 30.
* Style: The choices are Solid, Dash, Dot, Dash dot, and Dash dot-dot.
* Restore defaults: This button allows you to reset your settings to
their original defaults.


--
Takuya Nishimoto
nishimotz@gmail.com


Re: NVDA beep when power status changes?

DaVid
 

On windows, sighted people can see the power status led. On android
and iOs, those notiffications are by sound also, with the option to
disable them.

MessageWindow can't be subclassed, extending from
windowUtils.CustomWindow is the way to go with an add-on I think.
I don't wanted to duply a functionality in add-on, since it is already
in NVDA but with voice. If I create an add-on, I could add sound
notifffication but I can't disable voice notification.
The options for this setting could be:
Disabled: NVDA doesn't announce power status changes at all.
Voice.
Tones.
Voice and tones.

With default setting in voice.

Regards,
DaVid.


Re: Testing for root of dom in Firefox

Alberto Buffolino
 

Andy B., il 08/06/2019 20.19, ha scritto:
Unfortunately, I have no way of checking for the root element in a web document. Does anyone have any ideas? I am strictly using Firefox at this time. It appears everything is a mozilla.Mozilla object... Any help would be appreciated because I am stuck.
Alberto:
Hi Andy,
I'm not sure if it's useful, but you can check the role, which should be controlTypes.ROLE_DOCUMENT.
Or investigating about ISimpleDOM, I think ISimpleDOMDocument interface would have a method to get document root object.
Alberto


Re: NVDA beep when power status changes?

James Scholes
 

There are usually no wrong or right answers when it comes to scope. But in this case, consider how the behaviour works on other devices. On iOS, for example, the device will usually make a sound when charging begins, depending on the state of the mute switch. This occurs regardless of whether VoiceOver is running or not. If VoiceOver is running, the user will hear both the sound and spoken feedback from the screen reader.

I should note that I don’t have any feeling either way as to whether this functionality should be included in core or not. And when it comes to add-ons, almost anything goes as far as I’m concerned, especially if you are only creating the add-on for yourself. But understand that people are pushing back in this instance, because you specifically suggested that this be a core feature.

On 9 Jun 2019, at 08:24, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:

Yes I agree I think we do noted so many other noises which is why I liked the 3d sound add on which sadly needs fixing to work on the next version of nvda.
I really do like the fact that not only does it present different sounds for different objects, but it moves them about the screen to make the layout clearer too. It could be added to such an add on, It would be good for laptop users. I have my power scheme set to modified high performance these days.
IE nothing switches of and the processor runs flat out. Its amazing what it can do for latency on explorer.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message ----- From: "DaVid" <dhf360@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Saturday, June 08, 2019 11:56 PM
Subject: Re: [nvda-addons] NVDA beep when power status changes?


Perhaps you could consider this: Currently NVDA anounces the power
status changes with voice and braille message. Is this on the scope of
a screen reader? I guess yes, since NVDA does it.
What is the difference between play a sound or reproduce a voice message?
Both are signals that the user can perceive.
So which is ouside of the scope: The feature (NVDA already has it) or
the sound signal?

Regards,
DaVid.
2019-06-08 15:08 GMT-06:00, Luke Davis <luke@newanswertech.com>:
Personally I like the idea, but it seems outside the scope of a
screenreader.
For that reason I think it should be an addon, not in core.

Luke

On Sat, 8 Jun 2019, DaVid wrote:

Hi, I was developing an add-on to beep when the power status changes.
But it requires to subscribe to windows message events, is not hard to
do but NVDA already does it for the same event. The function that
receives the event can't be patched, I think. So I need to copy all
the code from that method and do my changes.
So I think that this feature could be implemented in the NVDA core,
with an option to enable or disable this behavior. Could be useful for
People like me, that usually don't wait a message to be spoken.
Some computers have this feature on the bios, but is not usual these
days.

What do you think about it?

Regards,
DaVid.








Re: Possible Bug in Addon Updater

Brian's Mail list account
 

Interestingly, I think there are times when windows simply forgets things or gets very confused. I've discovered that my long running saga of nvda not restarting after an update to add ons or itself is due to windows seeming to say files are locked for longer than one might think. Often waiting several seconds fixes it.

I guess we can never proof code against such behaviours.
Brian

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

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Sunday, June 09, 2019 3:29 AM
Subject: Re: [nvda-addons] Possible Bug in Addon Updater


Hi,
I think this may have to do with urllib library in use. If doing a third
check for add-on updates succeeds, then yes, it is a temporary connection
problem that urllib didn't know about.
At the moment I have suspended add-on development except for major and
critical issues in order to concentrate on highest of highest of priority
work in NVDA (Python 3).
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Luke Davis
Sent: Saturday, June 8, 2019 7:23 PM
To: nvda-addons@groups.io
Subject: [nvda-addons] Possible Bug in Addon Updater

I have only observed this once, which could mean it was a fluke, but it
seems a tad buggish.

1. An addon Updater window automatically appeared at some point, showing an
update for Win Ten App Essentials.
2. Right before noticing that, I turned off my laptop WiFI (hotkey),
thinking I was actually turning it on.
3. Then I hit "Update" to install the update.
4. Since there was now no internet access, I got an error dialog, saying
that it couldn't update.
5. Once I turned WiFI back on, I ran the NVDA->Tools->Check for addon
updates.
6. It reported "No addon update available". That is what I consider the bug:
it "forgot" that there was an update it had just told me about, because it
was unable to download it.
(N.B. should probably say "No addon updates available".) 7. I restarted
NVDA, ran step 5 again, and got the usual update dialog, which allowed me to
update W10AE.

Log attached.

Luke






Re: NVDA beep when power status changes?

Brian's Mail list account
 

Yes I agree I think we do noted so many other noises which is why I liked the 3d sound add on which sadly needs fixing to work on the next version of nvda.
I really do like the fact that not only does it present different sounds for different objects, but it moves them about the screen to make the layout clearer too. It could be added to such an add on, It would be good for laptop users. I have my power scheme set to modified high performance these days.
IE nothing switches of and the processor runs flat out. Its amazing what it can do for latency on explorer.
Brian

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

----- Original Message -----
From: "DaVid" <dhf360@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Saturday, June 08, 2019 11:56 PM
Subject: Re: [nvda-addons] NVDA beep when power status changes?


Perhaps you could consider this: Currently NVDA anounces the power
status changes with voice and braille message. Is this on the scope of
a screen reader? I guess yes, since NVDA does it.
What is the difference between play a sound or reproduce a voice message?
Both are signals that the user can perceive.
So which is ouside of the scope: The feature (NVDA already has it) or
the sound signal?

Regards,
DaVid.
2019-06-08 15:08 GMT-06:00, Luke Davis <luke@newanswertech.com>:
Personally I like the idea, but it seems outside the scope of a
screenreader.
For that reason I think it should be an addon, not in core.

Luke

On Sat, 8 Jun 2019, DaVid wrote:

Hi, I was developing an add-on to beep when the power status changes.
But it requires to subscribe to windows message events, is not hard to
do but NVDA already does it for the same event. The function that
receives the event can't be patched, I think. So I need to copy all
the code from that method and do my changes.
So I think that this feature could be implemented in the NVDA core,
with an option to enable or disable this behavior. Could be useful for
People like me, that usually don't wait a message to be spoken.
Some computers have this feature on the bios, but is not usual these
days.

What do you think about it?

Regards,
DaVid.






Re: NVDA beep when power status changes?

Brian's Mail list account
 

The test here is what do sighted people get when this happens?
If they can see it happen then it might need a sound, otherwise maybe not.
Brian

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

----- Original Message -----
From: "Luke Davis" <luke@newanswertech.com>
To: "nvda-addons" <nvda-addons@nvda-addons.groups.io>
Sent: Saturday, June 08, 2019 10:08 PM
Subject: Re: [nvda-addons] NVDA beep when power status changes?


Personally I like the idea, but it seems outside the scope of a screenreader. For that reason I think it should be an addon, not in core.

Luke

On Sat, 8 Jun 2019, DaVid wrote:

Hi, I was developing an add-on to beep when the power status changes.
But it requires to subscribe to windows message events, is not hard to
do but NVDA already does it for the same event. The function that
receives the event can't be patched, I think. So I need to copy all
the code from that method and do my changes.
So I think that this feature could be implemented in the NVDA core,
with an option to enable or disable this behavior. Could be useful for
People like me, that usually don't wait a message to be spoken.
Some computers have this feature on the bios, but is not usual these days.

What do you think about it?

Regards,
DaVid.



Re: NVDA beep when power status changes?

derek riemer
 

Can you raise a ticket for us to export a hook from that function that allows addons to receive notifications about select windows events we already subscribe to?  You could also create a new WndProc in your addon, by subclassing MessageWindow. (That works in addons too). We don't export that for good reasons, we don't want people breaking NVDA's wndProc.

On Sat, Jun 8, 2019 at 4:56 PM DaVid <dhf360@...> wrote:
Perhaps you could consider this: Currently NVDA anounces the power
status changes with voice and braille message. Is this on the scope of
a screen reader? I guess yes, since NVDA does it.
What is the difference between play a sound or reproduce a voice message?
Both are signals that the user can perceive.
So which is ouside of the scope: The feature (NVDA already has it) or
the sound signal?

Regards,
DaVid.
2019-06-08 15:08 GMT-06:00, Luke Davis <luke@...>:
> Personally I like the idea, but it seems outside the scope of a
> screenreader.
> For that reason I think it should be an addon, not in core.
>
> Luke
>
> On Sat, 8 Jun 2019, DaVid wrote:
>
>> Hi, I was developing an add-on to beep when the power status changes.
>> But it requires to subscribe to windows message events, is not hard to
>> do but NVDA already does it for the same event. The function that
>> receives the event can't be patched, I think. So I need to copy all
>> the code from that method and do my changes.
>> So I think that this feature could be implemented in the NVDA core,
>> with an option to enable or disable this behavior. Could be useful for
>> People like me, that usually don't wait a message to be spoken.
>> Some computers have this feature on the bios, but is not usual these
>> days.
>>
>> What do you think about it?
>>
>> Regards,
>> DaVid.
>>
>>
>>
>>
>
>
>
>





--
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: Possible Bug in Addon Updater

 

Hi,
Uh oh, if it is fixed with a restart, than this might be something I may
need to look into.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Luke Davis
Sent: Saturday, June 8, 2019 7:58 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Possible Bug in Addon Updater

On Sat, 8 Jun 2019, Joseph Lee wrote:

I think this may have to do with urllib library in use. If doing a
third check for add-on updates succeeds, then yes, it is a temporary
connection
Only after restarting NVDA.

At the moment I have suspended add-on development except for major and
critical issues in order to concentrate on highest of highest of
priority work in NVDA (Python 3).
Well this is certainly not that, I just wanted to point it out as a
potential thing to know about. It's probably a corner case anyway.

Luke


Re: Possible Bug in Addon Updater

Luke Davis
 

On Sat, 8 Jun 2019, Joseph Lee wrote:

I think this may have to do with urllib library in use. If doing a third
check for add-on updates succeeds, then yes, it is a temporary connection
Only after restarting NVDA.

At the moment I have suspended add-on development except for major and
critical issues in order to concentrate on highest of highest of priority
work in NVDA (Python 3).
Well this is certainly not that, I just wanted to point it out as a potential thing to know about. It's probably a corner case anyway.

Luke


Re: Possible Bug in Addon Updater

 

Hi,
I think this may have to do with urllib library in use. If doing a third
check for add-on updates succeeds, then yes, it is a temporary connection
problem that urllib didn't know about.
At the moment I have suspended add-on development except for major and
critical issues in order to concentrate on highest of highest of priority
work in NVDA (Python 3).
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Luke Davis
Sent: Saturday, June 8, 2019 7:23 PM
To: nvda-addons@groups.io
Subject: [nvda-addons] Possible Bug in Addon Updater

I have only observed this once, which could mean it was a fluke, but it
seems a tad buggish.

1. An addon Updater window automatically appeared at some point, showing an
update for Win Ten App Essentials.
2. Right before noticing that, I turned off my laptop WiFI (hotkey),
thinking I was actually turning it on.
3. Then I hit "Update" to install the update.
4. Since there was now no internet access, I got an error dialog, saying
that it couldn't update.
5. Once I turned WiFI back on, I ran the NVDA->Tools->Check for addon
updates.
6. It reported "No addon update available". That is what I consider the bug:
it "forgot" that there was an update it had just told me about, because it
was unable to download it.
(N.B. should probably say "No addon updates available".) 7. I restarted
NVDA, ran step 5 again, and got the usual update dialog, which allowed me to
update W10AE.

Log attached.

Luke


Possible Bug in Addon Updater

Luke Davis
 

I have only observed this once, which could mean it was a fluke, but it seems a tad buggish.

1. An addon Updater window automatically appeared at some point, showing an update for Win Ten App Essentials.
2. Right before noticing that, I turned off my laptop WiFI (hotkey), thinking I was actually turning it on.
3. Then I hit "Update" to install the update.
4. Since there was now no internet access, I got an error dialog, saying that it couldn't update.
5. Once I turned WiFI back on, I ran the NVDA->Tools->Check for addon updates.
6. It reported "No addon update available". That is what I consider the bug: it "forgot" that there was an update it had just told me about, because it was unable to download it.
(N.B. should probably say "No addon updates available".)
7. I restarted NVDA, ran step 5 again, and got the usual update dialog, which allowed me to update W10AE.

Log attached.

Luke


Re: NVDA beep when power status changes?

DaVid
 

Perhaps you could consider this: Currently NVDA anounces the power
status changes with voice and braille message. Is this on the scope of
a screen reader? I guess yes, since NVDA does it.
What is the difference between play a sound or reproduce a voice message?
Both are signals that the user can perceive.
So which is ouside of the scope: The feature (NVDA already has it) or
the sound signal?

Regards,
DaVid.
2019-06-08 15:08 GMT-06:00, Luke Davis <luke@newanswertech.com>:

Personally I like the idea, but it seems outside the scope of a
screenreader.
For that reason I think it should be an addon, not in core.

Luke

On Sat, 8 Jun 2019, DaVid wrote:

Hi, I was developing an add-on to beep when the power status changes.
But it requires to subscribe to windows message events, is not hard to
do but NVDA already does it for the same event. The function that
receives the event can't be patched, I think. So I need to copy all
the code from that method and do my changes.
So I think that this feature could be implemented in the NVDA core,
with an option to enable or disable this behavior. Could be useful for
People like me, that usually don't wait a message to be spoken.
Some computers have this feature on the bios, but is not usual these
days.

What do you think about it?

Regards,
DaVid.






Re: NVDA beep when power status changes?

 

Hi,
I'd say more towards a utility outside of NVDA.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Luke Davis
Sent: Saturday, June 8, 2019 2:08 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: Re: [nvda-addons] NVDA beep when power status changes?

Personally I like the idea, but it seems outside the scope of a
screenreader.
For that reason I think it should be an addon, not in core.

Luke

On Sat, 8 Jun 2019, DaVid wrote:

Hi, I was developing an add-on to beep when the power status changes.
But it requires to subscribe to windows message events, is not hard to
do but NVDA already does it for the same event. The function that
receives the event can't be patched, I think. So I need to copy all
the code from that method and do my changes.
So I think that this feature could be implemented in the NVDA core,
with an option to enable or disable this behavior. Could be useful for
People like me, that usually don't wait a message to be spoken.
Some computers have this feature on the bios, but is not usual these days.

What do you think about it?

Regards,
DaVid.



6561 - 6580 of 14888