Hi, That’s something else (let’s not discuss Add-on Updater issues in this thread please as it is a different topic altogether). Cheers, Joseph

Hi, As for Windows version info changes, it is a pull request and I’m not sure when it will be reviewed. But I’m assuming in Windows 10 App Essentials that changes are taking place (stashed it for now

Hello NVDA add-ons community, The following should be considered a major advisory and should be applied as soon as possible (this isn’t a critical advisory where you need to take immediate action): A

Hi, No - Add-on Updater doesn't know anything about individual add-ons, leaving Windows version checks to add-ons themselves or uses info provided by add-on manifests. Cheers, Joseph

Hi, I can change the install dialog for 21.03 (March). The current behavior is meant to test add-on compatibility with older releases, but it appears it needs to change (thanks for pointing this out).

Hi, It depends on which Windows 10 version the user is using. At the moment Windows 10 App Essentials will support Version 1909 or later, but that's about to change: upcoming 21.02 will require Window

Hello add-ons community, Please take note of Reef’s statements below. In addition, any add-on that uses C extensions (pyd files) will need to include Python 3.8 specific pyd files. I’ll make an announ

Hi all, The following might be useful for add-on authors as they look into improving their source code and/or are looking for subtle bugs: Although not advertised a lot, you can in fact tell Python th

Hi, Regarding Python 3 compliance: I recommend applying this recommendation from now on. Although other reviewers may not follow with this, any add-on to be reviewed by me will be required to be writt

Hello all, On behalf of NVDA add-ons community, I’m delighted to announce the immediate availability of NVDA Add-on Development Guide 2020.4: https://github.com/nvdaaddons/DevGuide/wiki/NVDA-Add-on-De

Hi Doug, At least for Windows 10 App Essentials, although I didn't really formalize it, my recommendation is for the client to use version 20.01, the latest version compatible with Windows 10 Version

Hi, Ah, thanks for clarifying many things for us (and for me, personally). Cheers, Joseph

Hi, I think mentioning this in dev guide would suffice, or perhaps add a list of things add-on authors should be aware of in the processes document. Cheers, Joseph

Hi, A better community directive title should be: Directive: do not override system environment variables without preserving old values A really elegant alternative is not using system path environmen

Hi all, The following NVDA Add-ons community directive applies to ALL add-ons going forward and will be applied when reviewing add-ons: You can query system environment variables by doing: import os o

Hi all, If not done already, ask Acapela to change the offending line in their add-on code. I remember NV Access talking about absolute paths, but not sure if the offending line is to blame or might b

Hi, One thing to note (for folks reviewing it): NVDA+H is taken by Control Usage Assistant. I'm willing to give up NVDA+H provided that the community believes it will be more useful to assign to the n

Hello everyone, A few weeks ago this forum had a discussion regarding lack of source code documentation for NVDA screen reader. As noted by a number of participants, lack of such documents hinders add

Hi all, NVDA Community Add-on Template 2020.4 is now available. You can grab it via Git at: https://github.com/nvdaaddons/addonTemplate Notable changes in 2020.4 include fixing bugs related to documen

Hello everyone, Four add-ons were updated to version 21.01: Enhanced Touch Gestures: dedicated touch support toggle command was removed from the add-on as NVDA provides one. As a result, NVDA 2020.3 o

#addonrelease