Hi, The latest version you'll get depends on the channel you are on, NVDA version (dev channel now reuiqres 2023.1 or later), and Windows version you've got (at least using Add-on Updater/community ad

#addonrelease

Hi, That I don't know as things are still being developed. Cheers, Joseph

Hi, The idea of translating add-ons in version 1.0 could be traced to the fact that it is the translations team and the workflow that actually powers community add-ons website. The infrastructure of t

Hi, I think what Brian V is referring to in terms of the "approval" process has to do with the old code review process. Before the advent of add-on store, when new add-on versions were released, someo

Hi, The reason for putting add-ons in community add-ons website is discoverability as addons.nvda-project.org is a little bit better known and can be accessed from NVDA itself (under add-ons manager/g

Hi, Another option is getting NVDA Recorder and other add-ons registered on community add-ons website to improve discoverability. We might as well invite authors of add-ons hosted on Spanish community

Hi, There are two things going on: Incompatible add-ons: NVDA will prevent you from installing incompatible add-ons, and in this case, you still can't browse the add-on store directly from Add-on Upda

Hi, Add-on Updater does not let you browse add-on store - it will check for updates to add-ons you have already installed if they are available from add-on store or other source of your choosing. You

Hi, Perhaps not through Add-on Updater, but through NVDA itself in the future when the add-on store client comes to life. Cheers, Joseph

Hi, At the moment anyone with a GitHub account can submit add-ons to add-on store if they have: Add-on name and version Download URL Code repository address (typically github.com URL) Publisher (typic

Hi, At least Vocalizer series distributed by Tiflotecnia are recorded in add-on store and on community add-ons website but we only provide download links for drivers, not the actual mechanism for purc

Hi, I once thought about it (multiple sources at once), but with the advent of add-on store, this became unnecessary. Cheers, Joseph

Hi, Try: Restart your computer, then try installing Add-on Updater. Open NVDA menu/Tools/Manage add-ons, select Install, navigate to downloads folder, select Add-on Updater package, and NVDA will inst

#addonrelease

Hello everyone, In addition to the release announcement, please read this post to the end as it includes important information on add-on release channels and requirements: Windows App Essentials 23.04

#addonrelease

Hi, I'm working on bringing Add-on Updater 23.04.1 to community add-ons website update source. Cheers, Joseph

#adminnotice

Hi, And via community add-ons website update source from Add-on Updater. Cheers, Joseph

Hi all, To add to this post: After selecting a different update source, you must say yes when prompted. Add-on Updater 23.04.1 is compatible with NVDA 2022.4 and later. If you are using NVDA 2022.4, u

#adminnotice

Hi, Last time I checked, add-on store does not have 2.6.2 (latest release), but I'm willing to offer it via Add-on Updater's community add-ons website update source soon. Cheers, Joseph

Hi, Answering severla questions at once: Changing add-on update source: you must be using Add-on Updater to change add-on update source. Add-on Updater not working with NVDA 2023.1: you might be using

#addonrelease

Hi all, Add-on Updater 23.04.1 is now available. This release can be fetched if you switch to NV Access add-on store update source, which, by the way, is no longer an experimental update source as see

#addonrelease