Closed Neurrone closed 3 weeks ago
Hi @Neurrone. The code was updated to python 3.11, and the add-on supports NVDA halpa versions. But the compatibility was not updated yet, because the alhpas of NVDA can change the api. I will think if update the compatibility version is a good idea. I will close this issue once the compatibility versions are updated in the manifest.
In my opinion, we shouldn't update the compatibility flags until at least the first 2024.1 beta. NV Access has indicated that 2024.1 will have a particularly long development cycle, even skipping 2023.4 this year, so I feel like at this stage it's too early to update the manifest. If there's enough demand, we could perhaps release a prerelease update, indicating that while it does work with 2024.1 right now, the manifest hasn't yet been updated because compatibility with 2024.1 is not guaranteed at this stage.
Makes sense. I'll try updating to the latest snapshot to see if it still works.
A related question: does this support Wasapi? I saw someone asking about it 2 months ago in #100
The betas have been out for a while now, though I'm not personally using them. Does this work with those? If so, I think the APIs we're using should be stable enough to declare compatibility. If not, at least they can force load.
At least on my site is working properly. Using with NVDA 2024.1Beta10.
Could this add-on be updated to support version 2024.1? Alpha snapshots have incremented the add-on version to 2024.1.