Date
1 - 4 of 4
Nvda beta - eloquence and vocalizer add on
|
Daniel McGee
hello all
During the beta cycle of a new nvda release, can the eloquence and vocalizer addon be used? If not, is there a way, to separat the: stable release to the: beta release? So that it doesn't mess up the licensing system of the add-on.
|
|
|
|
David Goldfield
I've used the Eloquence/Vocalizer addon with beta and RC builds with no difficulties. Of course, this assumes that you're not working with a beta which breaks compatibility with the addon.
toggle quoted messageShow quoted text
David Goldfield, Blindness Assistive Technology Specialist JAWS Certified, 2019 Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field. Email: tech-vi+subscribe@groups.io www.DavidGoldfield.org
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Daniel McGee Sent: Friday, September 10, 2021 9:45 AM To: nvda@nvda.groups.io Subject: [nvda] Nvda beta - eloquence and vocalizer add on hello all During the beta cycle of a new nvda release, can the eloquence and vocalizer addon be used? If not, is there a way, to separat the: stable release to the: beta release? So that it doesn't mess up the licensing system of the add-on.
|
|
|
|
Quentin Christensen
The only time it won't work is if the new release is a compatibility breaking release, like NVDA 2021.1 was. We don't do such a release every year, but if we do, it will be the first release of the year. Most importantly, if we do, we'll be sure to publicise it well in advance, as we have done previously - both here in the group, on our social media (Twitter and Facebook) and in our In-Process blog: https://www.nvaccess.org/category/in-process/ If you do attempt to install a new version which is incompatible with your existing add-ons, it will warn you of this and which add-ons are incompatible, before you update, and at that point you can decide to continue and disable those add-ons, or cancel and not go ahead with the update. Another option, is to create a portable version. A portable version lets you separate, as you suggested - your two versions of NVDA so you can keep using older add-ons if needed until they are updated to work with a new version of NVDA. There are a couple of caveats to using a portable copy, such as not being able to run it on the logon screen, and these are outlined in the user guide: https://www.nvaccess.org/files/nvda/documentation/userGuide.html#PortableAndTemporaryCopyRestrictions Kind regards Quentin.
On Sat, Sep 11, 2021 at 7:55 AM David Goldfield <david.goldfield@...> wrote: I've used the Eloquence/Vocalizer addon with beta and RC builds with no difficulties. Of course, this assumes that you're not working with a beta which breaks compatibility with the addon. --
Quentin Christensen Training and Support Manager Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess
|
|
|
|
Daniel McGee
Dear David and Quentin. Thank you both very much for your information. It was most informative and detailed. I do have one further question. Now that NVDA 2021.2 has been released, would it be advisable to, deactivate the add-on, update NVDA then reactivate the add-on again. Or is this unnecessary. Just do a straight update from the previous release of NVDA. u 13 Sep 2021, at 06:44, Quentin Christensen <quentin@...> wrote:
|
|
|