Hi everyone, I have made a YouTube video on how to make incompatible NVDA add-ons compatible with the latest NVDA release (2023.1). You can
watch the video here:
I hope you find this video helpful and informative. Please let me know what you think in the comments section of the video. thank you very much.

I did not review the video, but have to presume it presents the manifest edit workaround.  Be aware that this is a workaround and, if the add-on code is not being maintained, there will eventually come a point where it will not work.  That being said, it's still a great workaround when something is going to be updated but the actual update didn't make it out before the backward-compatibility-breaking NVDA release did.

See also: Editing an NVDA Add-On Manifest File as a Temporary Workaround – Admin Notice

 

--

Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881

Hi, yes this is exactly how I do it, but I tend to do it on a portable copy.
Several reasons for this, firstly it makes the add ons folder easier to find as its a sub directory of the configs one, and it also means that if the worst happens and it locks up your working copy of nvda, you are not in trouble, since its only a portable copy.
It also allows one to exhaustively test the system with the add on to make sure its not hiding an incompatibility that might bite you later on. When you are satisfied all is well then you can install it over the existing copy from the portable one.

Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.