This week's In-Process is out! Featuring the latest on NVDA 2024.1, add-on updates, the Microsoft FOSS Fund, Philanthropy Australia awards, an Interview with our GTO Gerald, and more! All available now at: nvaccess.org/post/in-process-2…

#NVDA #NVDAsr #News #Newsletter #Blog #Awards #Interview #FOSS #Community

This entry was edited (11 months ago)

David Goldfield reshared this.

in reply to NV Access

You know, this makes me think. It is entirely possible that an addon author will, accidentally or on purpose, declare an addon compatible when it actually isn't. It would be great if there was a way that bug reports could be automated such that certain failures could automatically reflag the addon as incompatible and send a note to the author, without you having to manually check everything.
in reply to Dave Taylor

@davetaylor2112 Interesting suggestion, and worth writing an issue for on: github.com/nvaccess/nvda/issue…

Because add-ons have the full power of Python at their disposal, checking for incompatibility would likely not be a trivial task, but definitely worth the question

in reply to Dave Taylor

@davetaylor2112 Talking with one of our developers today, I don't think there IS much we could do - the potential things to look out for would be too large. If anything, it would be better to do it on the code at the time the add-on is submitted to the store.

Re filing issues in general though - that's why we have a template, so it's aimed at being as simple to use as possible, just answer the questions as best you can.