Date   

Re: New release of ToolbarsExplorer (fix for latest alpha versions)

Brian's Mail list account
 

I see no ships, erm downloads..
Care to let us non github users have a direct link? grin.
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: "Alberto Buffolino" <a.buffolino@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Sunday, February 07, 2021 6:08 PM
Subject: [nvda-addons] New release of ToolbarsExplorer (fix for latest alpha versions)


Hi all,
after a long, long time (August 2019), this my add-on has needed an update. I simply fixed a controlTypes constant (REASON_FOCUS), keeping compatibility with previous versions, and upgrading the add-on template.
I have kept the download link for dev version only, hosting it on my Github account, for the moment.
When add-on system will be ready, I'm happy to release a new stable, including any new translations if necessary.
So, from here (download link under README section) ‚Üď ūüôā
https://github.com/ABuffEr/toolbarsExplorer
Alberto




Re: New release of ToolbarsExplorer (fix for latest alpha versions)

Noelia Ruiz
 

Thanks Alberto, though I haven"t seen the dev version for now. You were interested in GitHubActions GitHub Actions. In case you know and have curiosity, I"m using them to add translations from nvdaaddons/stable branches to nvdaes/master branch of add-ons hosted on my GitHub account, using crontab and push events.Also, if you"re interested in the system, he"s being documented publicly in nvaccess/addon-store-submission and he has a pull request create by Reef simplifing the process, in case you want to read or comment there. Apologies if you are aware of this (smile). Cheers

Enviado desde mi iPhone

El 7 feb 2021, a las 19:08, Alberto Buffolino <a.buffolino@gmail.com> escribió:

ÔĽŅHi all,
after a long, long time (August 2019), this my add-on has needed an update. I simply fixed a controlTypes constant (REASON_FOCUS), keeping compatibility with previous versions, and upgrading the add-on template.
I have kept the download link for dev version only, hosting it on my Github account, for the moment.
When add-on system will be ready, I'm happy to release a new stable, including any new translations if necessary.
So, from here (download link under README section) ‚Üď ūüôā
https://github.com/ABuffEr/toolbarsExplorer
Alberto





New release of ToolbarsExplorer (fix for latest alpha versions)

Alberto Buffolino
 

Hi all,
after a long, long time (August 2019), this my add-on has needed an update. I simply fixed a controlTypes constant (REASON_FOCUS), keeping compatibility with previous versions, and upgrading the add-on template.
I have kept the download link for dev version only, hosting it on my Github account, for the moment.
When add-on system will be ready, I'm happy to release a new stable, including any new translations if necessary.
So, from here (download link under README section) ‚Üď ūüôā
https://github.com/ABuffEr/toolbarsExplorer
Alberto


Re: CursorLocator dev versions. Was: cursorLocator 1.4.1-dev with arabic translation #addonrelease

Noelia Ruiz
 

Hi again:

Version 1.5.1, with brazilian and european portuguese translations,
sent by √āngelo Miguel Abrantes.

Changes for 1.5.1-dev (PR #7)
‚ÄĘ Added brazilian and european portuguese translations.
Download:

https://github.com/nvdaes/cursorLocator/releases/download/1.5.1-dev/cursorLocator-1.5.1-dev.nvda-addon

Thanks.

2021-02-05 7:24 GMT+01:00, Noelia Ruiz via groups.io
<nrm1977=gmail.com@groups.io>:

Hello: Here's a new version fixing a bug reported by @Ibrahim-s:

Changes for 1.5-dev (PR #6)
‚ÄĘ Fixed line length when the cursor isn't placed on the last line in
programs like Notepad (issue #5).
https://github.com/nvdaes/cursorLocator/releases/download/1.5-dev/cursorLocator-1.5-dev.nvda-addon

Thanks.

2021-02-02 7:57 GMT+01:00, Ibrahim Hamadeh <ibra.hamadeh@hotmail.com>:
Hello Noelia
may be your remarks was mentioned in previous messages , and I missed
them
OK, I understand now your point
I have already changed manifest.ini and tested it
I am very grateful for your answer and your words.
Thank you for your dedication and efforts on this list
regards
ibrahim
On 2/2/2021 7:11 AM, Noelia Ruiz wrote:
Hi Ibrahim, happy to see you again. I have tested the add-on with NVDA
2004beta4, so, for security, I set the minimum NVDA's version to
2020.4 for testing. I think that the add-on may work even with NVDA
2018.2, but since I'm not tested it, I decided to encourage testers to
use NVDA2004 betas for testing. Anyway, you can change the
manifest.ini file in case you want to test with NVDA 2020.3, but since
we are encouraged to test betas of NVDA, I think you may want to test
it with the last beta.
Also, here is cursorLocator 1.4.3-dev. In addition to previous
translations, this is translated into French,thanks to Rèmy Ruiz.
(@BlindHelp on GitHub).
Thanks

https://github.com/nvdaes/cursorLocator/releases/download/1.4.3-dev/cursorLocator-1.4.3-dev.nvda-add





.










Resources to learn writing addon for apps

William
 

Hi,

I wanna learn to write specific addon o make specific windows software accessible.

What resources are recommended for me?

Thanks,

William


Re: CursorLocator dev versions. Was: cursorLocator 1.4.1-dev with arabic translation #addonrelease

Noelia Ruiz
 

Hello: Here's a new version fixing a bug reported by @Ibrahim-s:

Changes for 1.5-dev (PR #6)
‚ÄĘ Fixed line length when the cursor isn't placed on the last line in
programs like Notepad (issue #5).
https://github.com/nvdaes/cursorLocator/releases/download/1.5-dev/cursorLocator-1.5-dev.nvda-addon

Thanks.

2021-02-02 7:57 GMT+01:00, Ibrahim Hamadeh <ibra.hamadeh@hotmail.com>:

Hello Noelia
may be your remarks was mentioned in previous messages , and I missed them
OK, I understand now your point
I have already changed manifest.ini and tested it
I am very grateful for your answer and your words.
Thank you for your dedication and efforts on this list
regards
ibrahim
On 2/2/2021 7:11 AM, Noelia Ruiz wrote:
Hi Ibrahim, happy to see you again. I have tested the add-on with NVDA
2004beta4, so, for security, I set the minimum NVDA's version to
2020.4 for testing. I think that the add-on may work even with NVDA
2018.2, but since I'm not tested it, I decided to encourage testers to
use NVDA2004 betas for testing. Anyway, you can change the
manifest.ini file in case you want to test with NVDA 2020.3, but since
we are encouraged to test betas of NVDA, I think you may want to test
it with the last beta.
Also, here is cursorLocator 1.4.3-dev. In addition to previous
translations, this is translated into French,thanks to Rèmy Ruiz.
(@BlindHelp on GitHub).
Thanks

https://github.com/nvdaes/cursorLocator/releases/download/1.4.3-dev/cursorLocator-1.4.3-dev.nvda-add





.






Re: IDEA Add-on Updater: Updating your own extensions outside the catalog,

Brian's Mail list account
 

Also of course the all important security issues need to be looked at in any new version, just in case the author has missed something.
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: Thursday, February 04, 2021 2:53 AM
Subject: Re: [nvda-addons] IDEA Add-on Updater: Updating your own extensions outside the catalog,


Hi,
Believe it or not I once thought about this idea in the past. Part of the
reason for the current state of Add-on Updater is that it relies on the
infrastructure provided by the community add-ons website. I hope we can
change that in the future once the supposed Add-on Store idea becomes a real
thing (but first, we need to find ways to make the add-on submission process
easier for everyone).
Cheers,
JOseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of alexey
Sent: Wednesday, February 3, 2021 5:48 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] IDEA Add-on Updater: Updating your own extensions
outside the catalog,

Hi. How can I force updates to add-ons that are not in the catalog?
I think it's an unnecessary task to write such a module for each of my add -
ons.
For example, update from my site or from Github?
This can be done like this:
In the manifest is specified:
update_url=https://mysite.example.org/update.json
File update.json contains:
{
"version":"2020.11.12",
"download_url": "https://mysite.example.org/myfile-v2020.11.12.nvda-addon"
}
Please consider this possibility in the future.









Re: Add-on version 21.02: Add-on Updater, Windows 10 App Essentials #addonrelease

Brian's Mail list account
 

Who maintains the add on I posted about just before your message? It is now fully broken in the latest alpha snap.
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: Wednesday, February 03, 2021 6:28 AM
Subject: [nvda-addons] Add-on version 21.02: Add-on Updater, Windows 10 App Essentials #AddonRelease


Hi all,

Version 21.02 of the following add-ons are now available (check for updates
in half an hour from now):

* Add-on Updater: Quick Dictionary update checking is now possible,
along with small tweaks to add-on update check mechanism.
* Windows 10 App Essentials: requires Windows 10 Version 2004 (May
2020 Update/build 19041) or later, and initial support for updated emoji
panel in Insider Preview build 21296 or later.



Special note on Add-on Updater: if everything goes as planned, the next
version of the add-on (21.03) will require NVDA 2020.4. This is in line with
support policy for this add-on: Add-on Updater requires latest stable
version of NVDA.

Cheers,

Joseph






Re: IDEA Add-on Updater: Updating your own extensions outside the catalog,

Noelia Ruiz
 

Hi Reef, thanks for mentioning GitHub cli. I had not tested it and
this is amazing, and we can even run gh pr checks to see if GitHub
Actions have been successful.
I¬°ve created a pull request since yesterday a new issue was created
for cursorLocator add-on, and I've used GitHub cli.
I may publish a post on the website created by me for spanish NVDA's
community, at nvdaes.github.io, mentioning this thread and your
suggestion.
About GitHub Actions to perform some checks, I find them very useful.
Anyway, I think that some type edit field for user comments should be
provided too.
Kind regards.

2021-02-04 5:30 GMT+01:00, Reef Turner <reef@nvaccess.org>:

Hi Alexey,

The proposal for the NVDA addon store submissions is intentionally aiming
to keep all metadata in a centralised location. This allows us and the
add-ons community to moderate it. The plan involves making the list of
add-ons available directly from NVDA, so NV Access must be cautious about
what will be available via that list.

For add-on authors who either dislike using or are unfamiliar with GitHub I
can recommend the Github CLI tool, which allows creating Pull requests from
the command line. I believe this will streamline the process for many
users.

I think we are basically at a stage where we can start accepting the json
metadata for add-ons to the store. And start offering it from NVDA. One
thing I'd like first is a published checklist for reviewing updates to the
json data.

To start with we can perform the checks manually, then I hope that some of
the people in our community who are experienced with Github Actions can
help to automate the checks. If all the checks are automated we will be
able to have a very rapid update process.

I should also point out, I expect that the add-ons website is updated to
use the same data source. However I believe that this will remain blocked
until we have a system in place for translating the metadata.

I hope this helps to explain the approach we are taking.

Reef Turner
Software Developer - NV Access


On Thu, 4 Feb 2021 at 11:34, alexey <aleks-samos@yandex.ru> wrote:

I think we should have
asked the community at the beginning to come up with a unique JSON for
the
update. Do if the "update_url" is not specified in the manifest, use some
default "
https://addons.nvda-project.org/files/update.php?file=mySuperScript",
did you ever think about this when you parsed the HTML code of the site
and the version numbers in the file name?
And if "update_url" is specified in the manifest, then it is already
checked, and since the JSON structure would be the same for everyone, the
next steps would be identical,
regardless of whether JSON is downloaded from the community site or from
any other third-party site.
I imagined it in my head and I think it's the perfect option!










Re: FYI: various hooks to get text

◊©◊ě◊ē◊ź◊ú ◊®◊ė◊Ď◊ô
 

Textractor
Thanks Alberto. Very interesting for me.
Shmuel

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Alberto Buffolino
Sent: Wednesday, February 3, 2021 10:38 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] FYI: various hooks to get text

Hi all,
recently, I discovered a project that tries to get text from
applications/games (primarily to translate it) in multiple, interesting
ways, concerning hooks to user32/gdi32/gdiplus DLL functions (see
engine.cc and pchooks.cc):
https://github.com/Artikash/Textractor
I have never seen these methods used in NVDA sources, neither in
add-ons, and I understand they are more like an hack than a standard
way... but may be of some interest in any case.
The game where I tested this project is a window with title and nothing
else, for NVDA. And Textractor is quite unconfortable and has issues in
the edit field where text is displayed, indeed, but this is another (QT)
problem.
Hth :)
Alberto


Re: IDEA Add-on Updater: Updating your own extensions outside the catalog,

 

Well I use github cli for some stuff in elektron forge but I also have github desktop which I use all the time.

Its easy to clone repos and stuff though I need to get their git links off the site first.

As for a centralised place, I do wander why all the centralised information couldn't be stored in ini files or text files.

Not sure how to do xml stuff but that is a commen way of storing all sorts of data.



On 4/02/2021 5:30 pm, Reef Turner wrote:
Hi Alexey,

The proposal for the NVDA addon store submissions is intentionally aiming to keep all metadata in a centralised location. This allows us and the add-ons community to moderate it. The plan involves making the list of add-ons available directly from NVDA, so NV Access must be cautious about what will be available via that list.

For add-on authors who either dislike using or are unfamiliar with GitHub I can recommend the Github CLI tool, which allows creating Pull requests from the command line. I believe this will streamline the process for many users.

I think we are basically at a stage where we can start accepting the json metadata for add-ons to the store. And start offering it from NVDA. One thing I'd like first is a published checklist for reviewing updates to the json data.

To start with we can perform the checks manually, then I hope that some of the people in our community who are experienced with Github Actions can help to automate the checks. If all the checks are automated we will be able to have a very rapid update process.

I should also point out, I expect that the add-ons website is updated to use the same data source. However I believe that this will remain blocked until we have a system in place for translating the metadata.

I hope this helps to explain the approach we are taking. 

Reef Turner
Software Developer - NV Access


On Thu, 4 Feb 2021 at 11:34, alexey <aleks-samos@...> wrote:
I think we should have
asked the community at the beginning to come up with a unique JSON for the update. Do if the "update_url" is not specified in the manifest, use some default "https://addons.nvda-project.org/files/update.php?file=mySuperScript",
did you ever think about this when you parsed the HTML code of the site and the version numbers in the file name?
And if "update_url" is specified in the manifest, then it is already checked, and since the JSON structure would be the same for everyone, the next steps would be identical,
regardless of whether JSON is downloaded from the community site or from any other third-party site.
I imagined it in my head and I think it's the perfect option!






Re: IDEA Add-on Updater: Updating your own extensions outside the catalog,

 

What about when you install addons, really should have a list of addons, and you can open one to hear its description then add to and get that.

You could always download addons  and such.

I'd also like the ability to have an account, add into what I need say addons I use a lot, then download a huge file for backup then only 1 file would install it all.

I wander if we could use ninite to install extras like addons since it will always get latest releases.

On 4/02/2021 4:34 pm, alexey wrote:
I think we should have
asked the community at the beginning to come up with a unique JSON for the update. Do if the "update_url" is not specified in the manifest, use some default "https://addons.nvda-project.org/files/update.php?file=mySuperScript",
did you ever think about this when you parsed the HTML code of the site and the version numbers in the file name?
And if "update_url" is specified in the manifest, then it is already checked, and since the JSON structure would be the same for everyone, the next steps would be identical,
regardless of whether JSON is downloaded from the community site or from any other third-party site.
I imagined it in my head and I think it's the perfect option!




.


Re: IDEA Add-on Updater: Updating your own extensions outside the catalog,

 

Well this is something we need to concidder.

I was thinking about taking an allready existing idea and adapt it to our needs.

Linux allready has repos of packages,

And an easy way to add extra repos.

The issue really should be who has access to addons infrastructure.

Something changed a bit ago which stopped part of this working.

Yes there are a few mirrors some with alegal stuff on them but not official.

There are more git repos than there are addons, and to add an addon to updater this needs to be done manually.

At this point it really needs to be that there is a central list where official addon authors have their addons, linux has official and unofficial repositories allready.

So all we need is a good package manager.

The nvda addon updater sounds nice, but maybe we need to take an allready established package manager and use that or at least something from that.

There should be things like the ability from nvda to switch between dev, alpha, beta and stable channels, and the ability to switch from addon channels etc easily enough.

As I said on the other thread, we really need to sort out the infrastructure or a way to get addons if for example it should fail.

At any rate, all we need is a mirror for official and one for unofficial.

Now we just need something to check releases and devs say once a day, maybe overnight, but have a way for a user to post directly and update their rrepo and also notify the updater manually, obviously they will need access to do that, but git access should be  good enough even if you then have google access on top of that and whatever security.

Then again, you could just say that every developer needs pgp or other key access both private or public for verification.

Thats a bit of an effort but what's 1 or 2 more packages when a usual source project usually has 30 or more packages.

I just ran updates on some source projects I am testing, I had to update several packages and I need to do some modifying of several files to have updated packages.

On 4/02/2021 3:53 pm, Joseph Lee wrote:
Hi,
Believe it or not I once thought about this idea in the past. Part of the
reason for the current state of Add-on Updater is that it relies on the
infrastructure provided by the community add-ons website. I hope we can
change that in the future once the supposed Add-on Store idea becomes a real
thing (but first, we need to find ways to make the add-on submission process
easier for everyone).
Cheers,
JOseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of alexey
Sent: Wednesday, February 3, 2021 5:48 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] IDEA Add-on Updater: Updating your own extensions
outside the catalog,

Hi. How can I force updates to add-ons that are not in the catalog?
I think it's an unnecessary task to write such a module for each of my add -
ons.
For example, update from my site or from Github?
This can be done like this:
In the manifest is specified:
update_url=https://mysite.example.org/update.json
File update.json contains:
{
"version":"2020.11.12",
"download_url": "https://mysite.example.org/myfile-v2020.11.12.nvda-addon"
}
Please consider this possibility in the future.









.


Re: IDEA Add-on Updater: Updating your own extensions outside the catalog,

Reef Turner
 

Hi Alexey,

The proposal for the NVDA addon store submissions is intentionally aiming to keep all metadata in a centralised location. This allows us and the add-ons community to moderate it. The plan involves making the list of add-ons available directly from NVDA, so NV Access must be cautious about what will be available via that list.

For add-on authors who either dislike using or are unfamiliar with GitHub I can recommend the Github CLI tool, which allows creating Pull requests from the command line. I believe this will streamline the process for many users.

I think we are basically at a stage where we can start accepting the json metadata for add-ons to the store. And start offering it from NVDA. One thing I'd like first is a published checklist for reviewing updates to the json data.

To start with we can perform the checks manually, then I hope that some of the people in our community who are experienced with Github Actions can help to automate the checks. If all the checks are automated we will be able to have a very rapid update process.

I should also point out, I expect that the add-ons website is updated to use the same data source. However I believe that this will remain blocked until we have a system in place for translating the metadata.

I hope this helps to explain the approach we are taking. 

Reef Turner
Software Developer - NV Access


On Thu, 4 Feb 2021 at 11:34, alexey <aleks-samos@...> wrote:
I think we should have
asked the community at the beginning to come up with a unique JSON for the update. Do if the "update_url" is not specified in the manifest, use some default "https://addons.nvda-project.org/files/update.php?file=mySuperScript",
did you ever think about this when you parsed the HTML code of the site and the version numbers in the file name?
And if "update_url" is specified in the manifest, then it is already checked, and since the JSON structure would be the same for everyone, the next steps would be identical,
regardless of whether JSON is downloaded from the community site or from any other third-party site.
I imagined it in my head and I think it's the perfect option!






Re: IDEA Add-on Updater: Updating your own extensions outside the catalog,

alexey <aleks-samos@...>
 

I think we should have
asked the community at the beginning to come up with a unique JSON for the update. Do if the "update_url" is not specified in the manifest, use some default "https://addons.nvda-project.org/files/update.php?file=mySuperScript",
did you ever think about this when you parsed the HTML code of the site and the version numbers in the file name?
And if "update_url" is specified in the manifest, then it is already checked, and since the JSON structure would be the same for everyone, the next steps would be identical,
regardless of whether JSON is downloaded from the community site or from any other third-party site.
I imagined it in my head and I think it's the perfect option!


Re: IDEA Add-on Updater: Updating your own extensions outside the catalog,

 

Hi,
Believe it or not I once thought about this idea in the past. Part of the
reason for the current state of Add-on Updater is that it relies on the
infrastructure provided by the community add-ons website. I hope we can
change that in the future once the supposed Add-on Store idea becomes a real
thing (but first, we need to find ways to make the add-on submission process
easier for everyone).
Cheers,
JOseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of alexey
Sent: Wednesday, February 3, 2021 5:48 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] IDEA Add-on Updater: Updating your own extensions
outside the catalog,

Hi. How can I force updates to add-ons that are not in the catalog?
I think it's an unnecessary task to write such a module for each of my add -
ons.
For example, update from my site or from Github?
This can be done like this:
In the manifest is specified:
update_url=https://mysite.example.org/update.json
File update.json contains:
{
"version":"2020.11.12",
"download_url": "https://mysite.example.org/myfile-v2020.11.12.nvda-addon"
}
Please consider this possibility in the future.


IDEA Add-on Updater: Updating your own extensions outside the catalog,

alexey <aleks-samos@...>
 

Hi. How can I force updates to add-ons that are not in the catalog?
I think it's an unnecessary task to write such a module for each of my
add - ons.
For example, update from my site or from Github?
This can be done like this:
In the manifest is specified:
update_url=https://mysite.example.org/update.json
File update.json contains:
{
"version":"2020.11.12",
"download_url": "https://mysite.example.org/myfile-v2020.11.12.nvda-addon"
}
Please consider this possibility in the future.


FYI: various hooks to get text

Alberto Buffolino
 

Hi all,
recently, I discovered a project that tries to get text from applications/games (primarily to translate it) in multiple, interesting ways, concerning hooks to user32/gdi32/gdiplus DLL functions (see engine.cc and pchooks.cc):
https://github.com/Artikash/Textractor
I have never seen these methods used in NVDA sources, neither in add-ons, and I understand they are more like an hack than a standard way... but may be of some interest in any case.
The game where I tested this project is a window with title and nothing else, for NVDA. And Textractor is quite unconfortable and has issues in the edit field where text is displayed, indeed, but this is another (QT) problem.
Hth :)
Alberto


placeMarkers 15.0 stable version available on the community website

Noelia Ruiz
 

Hi, Reef (NV Access) has made available this version on the add-ons website.

## Changes for 15.0 ##

* When reading with say all in browse mode, the specific find next and
specific find previous commands do not stop reading anymore if Allow
skim reading option is enabled, according to find next and find
previous commands from NVDA 2020.4.
* When the Specific search dialog is opened after running the Specific
find previous command, the Search previous option will be selected.


Note: these changes are based on code created by Cyrille, approved to
be included in NVDA 2020.4.
Also, the latest translation updates aren't included in this version.
I'll ask how to proceed so they can be included as soon as possible.

Please, see documentation an find download links for the add-on at

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

Be aware: though there are links for stable and dev versions, the two
links will download the stable version, since currently there's no dev
version to be tested on the website.
Enjoy!


Add-on version 21.02: Add-on Updater, Windows 10 App Essentials #addonrelease

 

Hi all,

Version 21.02 of the following add-ons are now available (check for updates in half an hour from now):

  • Add-on Updater: Quick Dictionary update checking is now possible, along with small tweaks to add-on update check mechanism.
  • Windows 10 App Essentials: requires Windows 10 Version 2004 (May 2020 Update/build 19041) or later, and initial support for updated emoji panel in Insider Preview build 21296 or later.

 

Special note on Add-on Updater: if everything goes as planned, the next version of the add-on (21.03) will require NVDA 2020.4. This is in line with support policy for this add-on: Add-on Updater requires latest stable version of NVDA.

Cheers,

Joseph

2681 - 2700 of 17255