If we do this, the naming of flags is important. Since last tested version only checks an API version (how confusing is that?), it should be changed to something more relevant. Last API version would

This brings up a point I am trying to make... New add-on developers may not have any idea where to look for the documentation on last tested version. The goal of any software is to be as self-document

Taking time is OK, as long as the initiative is widely documented and published. Andy Borka Accessibility Engineer

The last tested version is a supported version because a developer will most likely not release an add-on with a nonexistent version of NVDA, or leave last tested version set to an NVDA version in whi

Hi, What happens if someone fails to look at the add-on template or the add-on development guide? The flag still needs a clear path of communication of its purpose. Changing the name does this. Andy B

Thanks on the naming problem. We can educate the public, but keep in mind that the public's first impression of add-on development will come from looking at sources of the user's favorite add-ons. Sin

To remain consistent and reliable, it is better to change it, even if not required. Besides, NVDA developers can force a new api version at any time. Better to declare supported versions right away. A

Who tests the add-on against the stated NVDA version? The add-on owners, NVDA add-on community, or NVDA developers? Andy Borka Accessibility Engineer

Either way, someone has to declare supported NVDA versions. Each add-on manifest will have to declare minimum NVDA version and maximum NVDA version. Otherwise, how is the server going to know what the

I think maximum NVDA version should be required because we are talking about a range of NVDA versions. It makes it clear to developers and users, if included in add-on manager, that this add-on suppor

Well, not really. If I want to release add-on builds for testers, I have to set the last tested version flag to the current prerelease of NVDA. This isn't a problem, but the flag's name is misleading

Why don't we change lastTestedNVDAVersion to maximumSupportedNVDABersion to align with the minimumSupportedNVDAVersion flag? The purpose is much more clearly stated and is self-documenting. After all,

Try and keep the technical stuff away from the typical user. As you said, they could care less, or not understand anything about Python. They just want something that works without problems. Andy Bork

Noted for the next release… Andy Borka Accessibility Engineer

Hi, The NVDA add-on, Developer toolkit, is now available for download. You can find it here: https://github.com/ajborka/nvda_developer_toolkit/releases/tag/2020.1.1. This version improves Unicode supp

Hi, When I open Outlook 365, I get the following error in the log window: ERROR - RPC process 6260 (nvda_slave.exe) (07:15:05.269): __main__.main: slave error Traceback (most recent call last): File "

Hi, I get the following in the NVDA log when pressing control+r to reply to an email: ERROR - scriptHandler.executeScript (17:01:40.127): error executing script: <bound method GlobalCommands.script_re

Hi, I am developing an add-on that requests the formatting information of the currently focused item. Right now, NVDA requests a textInfos object from the current review position. However, my add-on s

Hi, This makes sense. However, it brings up another interesting problem. How will add-on authors reliably get their add-on releases to the add-on files repo? Currently, it takes someone with read/writ

Hi, I get the following errors when opening Outlook 365. ERROR - RPC process 3724 (nvda_slave.exe) (07:21:40.151): __main__.main: slave error Traceback (most recent call last): File "nvda_slave.pyw",