Re: Here we go again!


Jackie
 

Carlos, if you're going to be using alpha builds, it's wise to use
that as a portable version. When you use an alpha, it means you're
agreeing to using a version which, by the very nature of the name,
says it's not nearly ready for primetime.

I don't care if it's NVDA, Jaws, Windows, or whatever--backward
compatibility can only be maintained for so long. But in the case of
alpha builds, the situation is very much one of use at your own risk,
caveat emptor, etc, to whit, you shouldn't expect addons, especially
those not written by NVDA developers, to work, and if they do, take it
as a gift. In other words, use for testing, but certainly not for your
everyday work.

On 10/20/21, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,

To summarize Brian's points, if you are using alpha builds, you are on your
own and are responsible for providing timely feedback. In anticipation of
follow-up questions about delaying backward breaking changes like this, I
can tell you that these changes were planned in advance - it happens that
our move to Python 3 is helping us realize this plan in a more effective
way. Regarding add-ons, all I can say at this time is that authors are aware
of changes and they are looking into it (I expect authors will make
statements about their add-ons once 2022.1 beta is released).

Cheers,

Joseph





--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@freelists.org with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com

Join nvda@nvda.groups.io to automatically receive all group messages.