Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended
toggle quoted messageShow quoted text
My statement applies in case it is known that the addon causes the conflict and not the implementation of WX 4 in NVDA.
Von: firstname.lastname@example.org <email@example.com> Im Auftrag von Adriani Botez
I also see the responsibility to the addon authors who have been notified almost a year ago about this change. For a short time, it might throw NVDA a step backwards, but those are times where addon authors will be forced to do something for their addon to work.
Von: firstname.lastname@example.org <email@example.com> Im Auftrag von Joseph Lee
I think multiple factors are involved:
From: firstname.lastname@example.org <email@example.com> On Behalf Of Cohn, Jonathan
Sent: Thursday, June 7, 2018 9:45 AM
To: firstname.lastname@example.org; 'NVDA screen reader development' <nvda-devel@...>
Subject: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended
While I see this as essential in order to move to current versions of software / packages it is concerning that addons are breaking due to upgrading of the NVDA code base. I worked in an office where we developed 25 scripts for AT technologies a year and still had a back log of portions of applications that were not fully compliant with Windows accessibility API’s. If in addition to keeping up with Windows and application changes that occur regularily, addon developers have to do regular work on their stock of addons I could see this as a deterrent to wide spread adoption of NVDA. Is this a general problem in the Python community or just an issue from the transition to Python 3.