Date   
Re: Recreating focused object after execution of NVDAObject.clearDynamicClassCache()

 

Lukasz,


So, just to make sure before I elaborate further. when I understand you correctly, you want the overlay class to be present as soon as you execute the script, and get rid of the overlay when you execute the script again or another script?


Regards,

Leonard

On 29-11-2019 12:23, Lukasz Golonka wrote:
This plugin works as follows:
There is a class with some overwritten gestures and methods which makes
translation from LaTeX to speech and braille working when caret moves.

In chooseNVDAObjectOverlayClasses it checks for type of control, and for
a value of a variable  signaling if translation should be active or not.
This variable is switchable by a user with a script which checks if
caret is in a edit field, and if it is sets the variable accordingly. It
also executes NVDAObject.clearDynamicClassCache(), so yes I want to recreate
object with caret unconditionally when this script executes.


On Fri, 29 Nov 2019 08:21:28 +0100
"Leonard de Ruijter" <alderuijter@...> wrote:

Dear Lukasz,


Honestly, it's not clear to me what you're trying to do, i.e. why do you want to recreate the focus object anyway? How do you distinguish the edit field you like to support from the one you want to ignore?



Regards,
Leonard

Op 29-11-2019 om 00:39 schreef Lukasz Golonka:

Hi all, At the moment I am improving a plugin which makes NVDA work with LaTeX_Access. In its previous version class in which all scripts are defined was added to MRO of each edit fields even if translation of LaTeX to more verbal form was disabled. The simplest approach to fix this seemed to execute NVDAObject.clearDynamicClassCache() after switching translation on or off, and it almost works. The only problem is that as long as focus is not moved the LaTeX_Access class is still active for the currently focused edit field. Is there any way of forcing focused object to recreate? Alternatively is there a better way to achieve what I want to do? 




Joseph Lee's add-ons and NVDA 2019.3: dev snapshots for Golden Cursor, Resource Monitor, SystrayList

 

Hi developers and add-ons community,

 

As part of moving my add-ons to NVDA 2019.3, the next phase has begun: development snapshots for three more add-ons will now require NVDA 2019.3 in any form:

 

  • Golden Cursor
  • Resource Monitor
  • SystrayList

 

The usual notices:

 

  • Some of them does not include development version download link on community add-ons website. To test development snapshots, you need to switch to dev channel via Add-on Updater (NVDA menu/Preferences/Settings/Add-on Updater/Prefer development releases).
  • Just like snapshots for StationPlaylist and Windows 10 App Essentials, these three additional add-on snapshots will require NVDA 2019.3 in any form.

 

Add-on changelog:

 

  • Golden Cursor: downgrading to 3.8 after installing today’s development snapshot is not supported nor recommended.
  • Resource Monitor: no more Python 2 version of psutil library.
  • SystrayList: as requested by Rui Fontes a few weeks ago, donation requests will no longer show up. Also, Windows XP specific workaround for fetching Taskbar icons has been removed.

 

In December, more development snapshot releases will continue with GoldWave and one or two additional add-ons. Thankfully, dev snapshots of Add-on Updater will not be released so updates to existing add-ons will not be impacted.

Cheers,

Joseph

Re: Recreating focused object after execution of NVDAObject.clearDynamicClassCache()

Lukasz Golonka <wulfryk1@...>
 

This plugin works as follows:
There is a class with some overwritten gestures and methods which makes
translation from LaTeX to speech and braille working when caret moves.

In chooseNVDAObjectOverlayClasses it checks for type of control, and for
a value of a variable signaling if translation should be active or not.
This variable is switchable by a user with a script which checks if
caret is in a edit field, and if it is sets the variable accordingly. It
also executes NVDAObject.clearDynamicClassCache(), so yes I want to recreate
object with caret unconditionally when this script executes.


On Fri, 29 Nov 2019 08:21:28 +0100
"Leonard de Ruijter" <@leonardder> wrote:

Dear Lukasz,


Honestly, it's not clear to me what you're trying to do, i.e. why do you want to recreate the focus object anyway? How do you distinguish the edit field you like to support from the one you want to ignore?



Regards,
Leonard

Op 29-11-2019 om 00:39 schreef Lukasz Golonka:

Hi all, At the moment I am improving a plugin which makes NVDA work with LaTeX_Access. In its previous version class in which all scripts are defined was added to MRO of each edit fields even if translation of LaTeX to more verbal form was disabled. The simplest approach to fix this seemed to execute NVDAObject.clearDynamicClassCache() after switching translation on or off, and it almost works. The only problem is that as long as focus is not moved the LaTeX_Access class is still active for the currently focused edit field. Is there any way of forcing focused object to recreate? Alternatively is there a better way to achieve what I want to do?

Re: Recreating focused object after execution of NVDAObject.clearDynamicClassCache()

 

Dear Lukasz,

Honestly, it's not clear to me what you're trying to do, i.e. why do you want to recreate the focus object anyway? How do you distinguish the edit field you like to support from the one you want to ignore?

Regards,
Leonard
Op 29-11-2019 om 00:39 schreef Lukasz Golonka:

Hi all,

At the moment I am improving a plugin which makes NVDA work with LaTeX_Access. In its previous version class in which all scripts are defined was added to MRO of each edit fields even if translation of LaTeX  to more verbal form was disabled. The simplest approach  to fix this seemed to execute NVDAObject.clearDynamicClassCache() after switching translation on or off, and it almost works. The only problem is that as long as focus is not moved the LaTeX_Access class is still active for the currently focused edit field.
Is there any way of forcing focused object to recreate? Alternatively is there a better way to achieve what I want to do?

Recreating focused object after execution of NVDAObject.clearDynamicClassCache()

Lukasz Golonka <wulfryk1@...>
 

Hi all,

At the moment I am improving a plugin which makes NVDA work with LaTeX_Access. In its previous version class in which all scripts are defined was added to MRO of each edit fields even if translation of LaTeX to more verbal form was disabled. The simplest approach to fix this seemed to execute NVDAObject.clearDynamicClassCache() after switching translation on or off, and it almost works. The only problem is that as long as focus is not moved the LaTeX_Access class is still active for the currently focused edit field.
Is there any way of forcing focused object to recreate? Alternatively is there a better way to achieve what I want to do?

--
Thanks for your help
Lukasz

Re: Community ad-ons process and website update: legacy add-ons

 

Hi,
Ah, thanks for catching it.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of James Scholes
Sent: Wednesday, November 27, 2019 3:17 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Community ad-ons process and website update:
legacy add-ons

Can I suggest a small wording update?

> The following add-ons are no longer actively developed or incompatible
with recent NvDA releases.

If you remove the "actively developed or" bit, you get:

> The following add-ons are no longer incompatible with recent NvDA
releases.

... which is obviously untrue.

Regards,

James Scholes

On 27/11/2019 at 1:13 am, Joseph Lee wrote:
Hi all,

The add-ons people have received numerous reports of incompatible
add-ons listed on community add-ons website, along with reports of at
least one add-on that wasn't maintained actively until recently. To
highlight these, a "legacy add-ons" section has been created at the
following page:

https://addons.nvda-project.org/legacy.en.html

For purposes of record keeping, a legacy add-on is an add-on that is
no longer actively maintained and/or incompatible with recent NVDA
releases. When a new add-on maintainer is found or the add-on becomes
compatible with recent NVDA releases, they will return to either
"stable" or "development" status depending on the status prior to
legacy declaration. Some add-ons will be removed after being declared
"legacy"
for some time if the add-on becomes unnecessary, mostly due to
features from the add-on becoming part of NVDA screen reader.

Thank you.

Cheers,

Joseph

Re: Community ad-ons process and website update: legacy add-ons

James Scholes
 

Can I suggest a small wording update?

The following add-ons are no longer actively developed or
incompatible with recent NvDA releases.

If you remove the "actively developed or" bit, you get:

The following add-ons are no longer incompatible with recent NvDA
releases.

... which is obviously untrue.

Regards,

James Scholes

On 27/11/2019 at 1:13 am, Joseph Lee wrote:
Hi all,
The add-ons people have received numerous reports of incompatible add-ons listed on community add-ons website, along with reports of at least one add-on that wasn’t maintained actively until recently. To highlight these, a “legacy add-ons” section has been created at the following page:
https://addons.nvda-project.org/legacy.en.html
For purposes of record keeping, a legacy add-on is an add-on that is no longer actively maintained and/or incompatible with recent NVDA releases. When a new add-on maintainer is found or the add-on becomes compatible with recent NVDA releases, they will return to either “stable” or “development” status depending on the status prior to legacy declaration. Some add-ons will be removed after being declared “legacy” for some time if the add-on becomes unnecessary, mostly due to features from the add-on becoming part of NVDA screen reader.
Thank you.
Cheers,
Joseph

Re: Community ad-ons process and website update: legacy add-ons

Noelia Ruiz
 

I will move there teamViewer too this weekend.CHEERCheers

Enviado desde mi iPhone

El 27 nov 2019, a las 16:08, Joseph Lee <@joslee> escribió:

Hi,
Only screen Curtain is shown for now because it was declared deprecated a
few days ago and this was reported to the community. There will be
additional add-ons added, pending notifications from add-on authors and the
community (NVDA Remote and Enhanced Aria, for instance), provided that:
1. We lost touch with add-on authors and nobody came forward to maintain
inactive add-ons.
2. Noted as incompatible with future NVDA releases (for now, 2019.3).

Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Wednesday, November 27, 2019 6:34 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Community ad-ons process and website update:
legacy add-ons

I could be being thick here, but all I see here is screen curtain.
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: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Wednesday, November 27, 2019 7:13 AM
Subject: [nvda-devel] Community ad-ons process and website update: legacy
add-ons


Hi all,



The add-ons people have received numerous reports of incompatible
add-ons listed on community add-ons website, along with reports of at
least one add-on that wasn't maintained actively until recently. To
highlight these, a "legacy add-ons" section has been created at the
following page:

https://addons.nvda-project.org/legacy.en.html



For purposes of record keeping, a legacy add-on is an add-on that is
no longer actively maintained and/or incompatible with recent NVDA
releases.
When a new add-on maintainer is found or the add-on becomes compatible
with recent NVDA releases, they will return to either "stable" or
"development"
status depending on the status prior to legacy declaration. Some
add-ons will be removed after being declared "legacy" for some time if
the add-on becomes unnecessary, mostly due to features from the add-on
becoming part of NVDA screen reader.



Thank you.

Cheers,

Joseph









Re: Community ad-ons process and website update: legacy add-ons

 

Hi,
Only screen Curtain is shown for now because it was declared deprecated a
few days ago and this was reported to the community. There will be
additional add-ons added, pending notifications from add-on authors and the
community (NVDA Remote and Enhanced Aria, for instance), provided that:
1. We lost touch with add-on authors and nobody came forward to maintain
inactive add-ons.
2. Noted as incompatible with future NVDA releases (for now, 2019.3).

Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Wednesday, November 27, 2019 6:34 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Community ad-ons process and website update:
legacy add-ons

I could be being thick here, but all I see here is screen curtain.
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: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Wednesday, November 27, 2019 7:13 AM
Subject: [nvda-devel] Community ad-ons process and website update: legacy
add-ons


Hi all,



The add-ons people have received numerous reports of incompatible
add-ons listed on community add-ons website, along with reports of at
least one add-on that wasn't maintained actively until recently. To
highlight these, a "legacy add-ons" section has been created at the
following page:

https://addons.nvda-project.org/legacy.en.html



For purposes of record keeping, a legacy add-on is an add-on that is
no longer actively maintained and/or incompatible with recent NVDA
releases.
When a new add-on maintainer is found or the add-on becomes compatible
with recent NVDA releases, they will return to either "stable" or
"development"
status depending on the status prior to legacy declaration. Some
add-ons will be removed after being declared "legacy" for some time if
the add-on becomes unnecessary, mostly due to features from the add-on
becoming part of NVDA screen reader.



Thank you.

Cheers,

Joseph




Re: Community ad-ons process and website update: legacy add-ons

Brian's Mail list account
 

I could be being thick here, but all I see here is screen curtain.
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: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Wednesday, November 27, 2019 7:13 AM
Subject: [nvda-devel] Community ad-ons process and website update: legacy add-ons


Hi all,



The add-ons people have received numerous reports of incompatible add-ons
listed on community add-ons website, along with reports of at least one
add-on that wasn't maintained actively until recently. To highlight these, a
"legacy add-ons" section has been created at the following page:

https://addons.nvda-project.org/legacy.en.html



For purposes of record keeping, a legacy add-on is an add-on that is no
longer actively maintained and/or incompatible with recent NVDA releases.
When a new add-on maintainer is found or the add-on becomes compatible with
recent NVDA releases, they will return to either "stable" or "development"
status depending on the status prior to legacy declaration. Some add-ons
will be removed after being declared "legacy" for some time if the add-on
becomes unnecessary, mostly due to features from the add-on becoming part of
NVDA screen reader.



Thank you.

Cheers,

Joseph



Community ad-ons process and website update: legacy add-ons

 

Hi all,

 

The add-ons people have received numerous reports of incompatible add-ons listed on community add-ons website, along with reports of at least one add-on that wasn’t maintained actively until recently. To highlight these, a “legacy add-ons” section has been created at the following page:

https://addons.nvda-project.org/legacy.en.html

 

For purposes of record keeping, a legacy add-on is an add-on that is no longer actively maintained and/or incompatible with recent NVDA releases. When a new add-on maintainer is found or the add-on becomes compatible with recent NVDA releases, they will return to either “stable” or “development” status depending on the status prior to legacy declaration. Some add-ons will be removed after being declared “legacy” for some time if the add-on becomes unnecessary, mostly due to features from the add-on becoming part of NVDA screen reader.

 

Thank you.

Cheers,

Joseph

Re: Refreshable Braille Display Help

Brian's Mail list account
 

I don't think the dectalk works in the new alpha version from what I recall, but it might be relatively simple to market so, sadly I do not have the hardware device any more so I cannot help much.
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: "derek riemer" <driemer.riemer@...>
To: <nvda-devel@groups.io>
Sent: Tuesday, November 26, 2019 1:35 AM
Subject: Re: [nvda-devel] Refreshable Braille Display Help


Sort of. There are also examples of speech synth drivers lying around.
Especially externally. Most are software, but there's a dectalk hardware
one somewhere.

On Mon, Nov 25, 2019 at 6:32 PM Travis Siegel <tsiegel@...> wrote:

Is this the same process for a speech synthesizer? I have built one, using
commercial parts, and would like to make it work with NVDA as well.

I need to rewire it before I can test it, (things came loose while it was
on the shelf, since it was originally built as a speech device for my wife,
who has a speech defect, but it can just as easily be used as an external
synthesizer with minimal reprogramming.
On 11/25/2019 8:25 PM, derek riemer wrote:

Have you downloaded the NVDA source yet? github.com/nvaccess/nvda
In there, under source/brailleDisplayDrivers are some examples. They
inherit from the braille.BrailleDisplayDriver class. Reading the nvda
design document on the wiki we point to and the developer guide are great
first resources. I also wrote this article which might help you at some
point. (it's a little out of date now).

https://derekriemer.com/posts/2017/02/14/introduction-to-nvda-development-the-basic-objects-explained/

On Mon, Nov 25, 2019 at 3:00 PM <just1brill@...> wrote:

We're using a Raspberry Pi, but we could configure it to use PySerial to
communicate to Windows. On the normal NVDA forum, we were suggested to make
a driver, so we've began on that. I'd appreciate any links to source codes
of drivers.

Thanks.


--
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






--
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: Refreshable Braille Display Help

derek riemer
 

Sort of. There are also examples of speech synth drivers lying around. Especially externally. Most are software, but there's a dectalk hardware one somewhere.

On Mon, Nov 25, 2019 at 6:32 PM Travis Siegel <tsiegel@...> wrote:

Is this the same process for a speech synthesizer? I have built one, using commercial parts, and would like to make it work with NVDA as well.

I need to rewire it before I can test it, (things came loose while it was on the shelf, since it was originally built as a speech device for my wife, who has a speech defect, but it can just as easily be used as an external synthesizer with minimal reprogramming.

On 11/25/2019 8:25 PM, derek riemer wrote:
Have you downloaded the NVDA source yet? github.com/nvaccess/nvda
In there, under source/brailleDisplayDrivers are some examples. They inherit from the braille.BrailleDisplayDriver class. Reading the nvda design document on the wiki we point to and the developer guide are great first resources. I also wrote this article which might help you at some point. (it's a little out of date now).

On Mon, Nov 25, 2019 at 3:00 PM <just1brill@...> wrote:
We're using a Raspberry Pi, but we could configure it to use PySerial to communicate to Windows. On the normal NVDA forum, we were suggested to make a driver, so we've began on that. I'd appreciate any links to source codes of drivers.

Thanks.


--
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






--
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: Refreshable Braille Display Help

Travis Siegel
 

Is this the same process for a speech synthesizer? I have built one, using commercial parts, and would like to make it work with NVDA as well.

I need to rewire it before I can test it, (things came loose while it was on the shelf, since it was originally built as a speech device for my wife, who has a speech defect, but it can just as easily be used as an external synthesizer with minimal reprogramming.

On 11/25/2019 8:25 PM, derek riemer wrote:
Have you downloaded the NVDA source yet? github.com/nvaccess/nvda
In there, under source/brailleDisplayDrivers are some examples. They inherit from the braille.BrailleDisplayDriver class. Reading the nvda design document on the wiki we point to and the developer guide are great first resources. I also wrote this article which might help you at some point. (it's a little out of date now).

On Mon, Nov 25, 2019 at 3:00 PM <just1brill@...> wrote:
We're using a Raspberry Pi, but we could configure it to use PySerial to communicate to Windows. On the normal NVDA forum, we were suggested to make a driver, so we've began on that. I'd appreciate any links to source codes of drivers.

Thanks.


--
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: Refreshable Braille Display Help

derek riemer
 

Have you downloaded the NVDA source yet? github.com/nvaccess/nvda
In there, under source/brailleDisplayDrivers are some examples. They inherit from the braille.BrailleDisplayDriver class. Reading the nvda design document on the wiki we point to and the developer guide are great first resources. I also wrote this article which might help you at some point. (it's a little out of date now).

On Mon, Nov 25, 2019 at 3:00 PM <just1brill@...> wrote:
We're using a Raspberry Pi, but we could configure it to use PySerial to communicate to Windows. On the normal NVDA forum, we were suggested to make a driver, so we've began on that. I'd appreciate any links to source codes of drivers.

Thanks.



--
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: Refreshable Braille Display Help

just1brill@...
 

We're using a Raspberry Pi, but we could configure it to use PySerial to communicate to Windows. On the normal NVDA forum, we were suggested to make a driver, so we've began on that. I'd appreciate any links to source codes of drivers.

Thanks.

Re: Refreshable Braille Display Help

derek riemer
 

How do you communicate with windows? We use pySerial for our communications. I have not written a braille display driver, but i can tell you where to find the source code for various drivers.


On Mon, Nov 25, 2019 at 12:15 PM <just1brill@...> wrote:
Hello,
We are a group of students entering our country's top science exhibition, doing our project on refreshable braile displays, as we were interested in the idea of making the computer more accessible to all. We came across NVDA and found out it was perfect for what we stood for and needed.

But, we are having trouble making our board compatible with NVDA and was wondering if anybody could guide us on how it could be done or if it can be done at all. I understand this may be quite a complex topic, especially over messaging, but even help on where to turn to for advice would be great. We understand that other displays have been made compatible also.

The board is recognised by Windows (as of Win10 Ver 1903 Build 18362.476).

I understand that a project like this would not be in developers interest, as it won't be comercially available, but any help at all would be greatly appreciated and would be extremely beneficial.

Thanks



--
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




Refreshable Braille Display Help

just1brill@...
 

Hello,
We are a group of students entering our country's top science exhibition, doing our project on refreshable braile displays, as we were interested in the idea of making the computer more accessible to all. We came across NVDA and found out it was perfect for what we stood for and needed.

But, we are having trouble making our board compatible with NVDA and was wondering if anybody could guide us on how it could be done or if it can be done at all. I understand this may be quite a complex topic, especially over messaging, but even help on where to turn to for advice would be great. We understand that other displays have been made compatible also.

The board is recognised by Windows (as of Win10 Ver 1903 Build 18362.476).

I understand that a project like this would not be in developers interest, as it won't be comercially available, but any help at all would be greatly appreciated and would be extremely beneficial.

Thanks

FW: [nvda-addons] Extended Winamp and others with no recent author presence: emergency Python 3 compatibility releases to go out this week, community maintenance

 

 

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via Groups.Io
Sent: Monday, November 25, 2019 9:16 AM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Extended Winamp and others with no recent author presence: emergency Python 3 compatibility releases to go out this week, community maintenance

 

Hi al,

 

Important notice for users of Extended Winamp and other add-ons where we lost touch with add-on authors recently: starting today, updated versions of these add-ons will be released, all of them being emergency releases to make them work with future NVDA releases (in this case, Python 3 and beyond). We will try our best to release versions that are known to be compatible with old and new NVDA releases in order to ensure smooth transition.

 

Also, I advise community maintenance of at least Extended Winamp – I expect more add-ons to join community maintenance, seeing that we haven’t heard from authors in a while, especially at this very sensitive moment where the biggest concern is making sure add-ons circulating around NVDA community are ready for the future.

 

Thanks.

P.S. I’ll find Extended Winamp from the archive – I’ll post Beqa’s version since it was tested by several and found to be working.

Cheers,

Joseph

Add-on files proposal on add-on ID/name database lookup: withdrawing it

 

Hi all,

After going through community comments, I’m pulling out of the proposal sent last week regarding letting add-on files repo host add-on names to ID lookup mechanism. Until the new metadata database is ready, I’ll let Add-on Updater add-on carry this information.

Cheers,

Joseph