toggle quoted messageShow quoted text
Well, I dont think what I proposed is something illogical.
As you also stated that, some addon can use the manifest trick
to make it usable at the current version, so this is already an
solution to my issue above.
Some user who do not have coding knowledge at least can help to
test if a addon is working in new nvda by changing the manifest
.ini, and if it is working, they can inform the community about
To move forward, those can also help to edit the manifest and
post to the community the edited version of addon, cause not
everyone may have the ability to do so.
If this is not possible, at least please make a detailed
instruction to all the user if they wanna do the manifest trick.
Brian Vogel 於 9/9/2021 22:58 寫道:
On Thu, Sep 9, 2021
at 01:41 AM, William wrote:
Can we have a mechanism to make these addons being
maintained, even if the developer ignored it or forget to update
You do realize that what you propose is a logical impossibility,
If all the necessary maintenance is amounts to doing what's
proposed later, that is updating the manifest and doing testing
with the current version of NVDA, then the developer (whether the
original one or someone else) has updated what needs to be
The problem is that there are some add-ons that have been
abandoned by their original developer and have not, at least as
yet, been picked up by someone else. If and when they do, then
that person or those persons will again be maintaining the add-on.
While I commend those willing to try editing the manifest files as
a workaround, that's precisely what it is if no one is maintaining
the actual code. Eventually, a manifest tweak will not be
enough. Right now it is for certain add-ons, but that will not
last as time marches on. Someone else has to pick up maintenance
on the code if it is to remain viable over the long term.
Brian - Windows
10, 64-Bit, Version 21H1, Build 19043
Nothing in all the world
is more dangerous than sincere ignorance and conscientious
~Martin Luther King,