Date   

Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

Tyler Wood
 

Hi,

Hopefully this will get fixed soon. I will, too, be staying back as this is used pretty regularly when I use NVDA.



On 07-Jun-2018 10:17 PM, Richard Wells wrote:

I use it regularly with users. If this is not fixed before new release, I will need to stay back until they get it working. It is too important to my work.


On 6/7/2018 4:17 PM, Ervin, Glenn wrote:

I’ve never gotten it to work, I’ve tried several times since it came out.

Glenn

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sarah k Alawami
Sent: Thursday, June 07, 2018 12:58 PM
To: nvda list list
Subject: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

 

I  Actually did not take part in the  crowd funding  as I didn't believe this add on would ever happen, and I knew one of the devs so perosnally did not crowd fund it, I just will not go thee, not here.

 

Anyway yeah any way to get hold of the devs of the remote add on and ask them to please fix? At least for some  of us who use it. I only used it once and that was this year.

 

Here's hoping for a fix eh?



On Jun 7, 2018, at 10:23 AM, Mallard <mallard@...> wrote:

 

Considering that, unlike other add-ons, we all crowdfunded the development of this very add-on, I'd hope something is done about it very soon,





Il 07/06/2018 18:14, Joseph Lee ha scritto:


Hi all,

The below notice is considered critical:

It’s happening again: with the introduction of wxPython 4 in next snapshots, users of NVDA Remote add-on are having startup issues related to missing attribute in wxPython 4.

I propose the following solutions:

 * I highly recommend releasing Remote add-on 2.2 to fix this issue.
 * Perhaps adding a statement on nvdaremote.com website explaining
   that Remote add-on should be disabled if using recent NVDA next
   snapshots.
 * The community should release an updated version of this add-on
   with permission from add-on authors and maintainers.

Thanks.

Cheers,

Joseph




 




Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

Richard Wells
 

I use it regularly with users. If this is not fixed before new release, I will need to stay back until they get it working. It is too important to my work.


On 6/7/2018 4:17 PM, Ervin, Glenn wrote:

I’ve never gotten it to work, I’ve tried several times since it came out.

Glenn

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sarah k Alawami
Sent: Thursday, June 07, 2018 12:58 PM
To: nvda list list
Subject: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

 

I  Actually did not take part in the  crowd funding  as I didn't believe this add on would ever happen, and I knew one of the devs so perosnally did not crowd fund it, I just will not go thee, not here.

 

Anyway yeah any way to get hold of the devs of the remote add on and ask them to please fix? At least for some  of us who use it. I only used it once and that was this year.

 

Here's hoping for a fix eh?



On Jun 7, 2018, at 10:23 AM, Mallard <mallard@...> wrote:

 

Considering that, unlike other add-ons, we all crowdfunded the development of this very add-on, I'd hope something is done about it very soon,





Il 07/06/2018 18:14, Joseph Lee ha scritto:


Hi all,

The below notice is considered critical:

It’s happening again: with the introduction of wxPython 4 in next snapshots, users of NVDA Remote add-on are having startup issues related to missing attribute in wxPython 4.

I propose the following solutions:

 * I highly recommend releasing Remote add-on 2.2 to fix this issue.
 * Perhaps adding a statement on nvdaremote.com website explaining
   that Remote add-on should be disabled if using recent NVDA next
   snapshots.
 * The community should release an updated version of this add-on
   with permission from add-on authors and maintainers.

Thanks.

Cheers,

Joseph




 



Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

 

On Thu, Jun 7, 2018 at 10:34 am, Adriani Botez wrote:
My statement applies in case it is known that the addon causes the conflict and not the implementation of WX 4 in NVDA
Add-ons/extensions, in any setting that uses same, follow the core code - not the other way around.   The core functions cannot and will not stand still, and the add-ons sometimes cannot, either.

'Twas ever thus.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     Explanations exist; they have existed for all time; there is always a well-known solution to every human problem — neat, plausible, and wrong.

          ~ H.L. Mencken, AKA The Sage of Baltimore

 

 


Re: Add-on compatibility notice: NvDA Remote Support add-on2.1 is not compatible with wxPython 4, new release recommended

David Moore
 

Hi all!

I use NVDA remote add-on all the time!

I have helped many people use NVDA with this add-on.

I pray that there is a fix soon. This would be a tragedy if this add-on did not work anymore!

David Moore

Sent from Mail for Windows 10

 

From: Jackie
Sent: Thursday, June 7, 2018 6:33 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on2.1 is not compatible with wxPython 4, new release recommended

 

I love it. I use it all the time. I was glad to participate in the

crowd funding.

 

On 6/7/18, Ervin, Glenn <glenn.ervin@...> wrote:

> I’ve never gotten it to work, I’ve tried several times since it came out.

> Glenn

> From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sarah k

> Alawami

> Sent: Thursday, June 07, 2018 12:58 PM

> To: nvda list list

> Subject: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on

> 2.1 is not compatible with wxPython 4, new release recommended

> I  Actually did not take part in the  crowd funding  as I didn't believe

> this add on would ever happen, and I knew one of the devs so perosnally did

> not crowd fund it, I just will not go thee, not here.

> Anyway yeah any way to get hold of the devs of the remote add on and ask

> them to please fix? At least for some  of us who use it. I only used it once

> and that was this year.

> Here's hoping for a fix eh?

> On Jun 7, 2018, at 10:23 AM, Mallard

> <mallard@...<mailto:mallard@...>> wrote:

> Considering that, unlike other add-ons, we all crowdfunded the development

> of this very add-on, I'd hope something is done about it very soon,

> Il 07/06/2018 18:14, Joseph Lee ha scritto:

> Hi all,

> The below notice is considered critical:

> It’s happening again: with the introduction of wxPython 4 in next snapshots,

> users of NVDA Remote add-on are having startup issues related to missing

> attribute in wxPython 4.

> I propose the following solutions:

>  * I highly recommend releasing Remote add-on 2.2 to fix this issue.

>  * Perhaps adding a statement on nvdaremote.com<http://nvdaremote.com>

> website explaining

>    that Remote add-on should be disabled if using recent NVDA next

>    snapshots.

>  * The community should release an updated version of this add-on

>    with permission from add-on authors and maintainers.

> Thanks.

> Cheers,

> Joseph

 

 

--

Remember! Friends Help Friends Be Cybersafe

Jackie McBride

Helping Cybercrime Victims 1 Person at a Time

https://brighter-vision.com

 

 

 


Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

Jackie
 

I love it. I use it all the time. I was glad to participate in the
crowd funding.

On 6/7/18, Ervin, Glenn <glenn.ervin@...> wrote:
I’ve never gotten it to work, I’ve tried several times since it came out.
Glenn


From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sarah k
Alawami
Sent: Thursday, June 07, 2018 12:58 PM
To: nvda list list
Subject: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on
2.1 is not compatible with wxPython 4, new release recommended

I Actually did not take part in the crowd funding as I didn't believe
this add on would ever happen, and I knew one of the devs so perosnally did
not crowd fund it, I just will not go thee, not here.

Anyway yeah any way to get hold of the devs of the remote add on and ask
them to please fix? At least for some of us who use it. I only used it once
and that was this year.

Here's hoping for a fix eh?


On Jun 7, 2018, at 10:23 AM, Mallard
<mallard@...<mailto:mallard@...>> wrote:

Considering that, unlike other add-ons, we all crowdfunded the development
of this very add-on, I'd hope something is done about it very soon,





Il 07/06/2018 18:14, Joseph Lee ha scritto:


Hi all,

The below notice is considered critical:

It’s happening again: with the introduction of wxPython 4 in next snapshots,
users of NVDA Remote add-on are having startup issues related to missing
attribute in wxPython 4.

I propose the following solutions:

* I highly recommend releasing Remote add-on 2.2 to fix this issue.
* Perhaps adding a statement on nvdaremote.com<http://nvdaremote.com>
website explaining
that Remote add-on should be disabled if using recent NVDA next
snapshots.
* The community should release an updated version of this add-on
with permission from add-on authors and maintainers.

Thanks.

Cheers,

Joseph





--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com


Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

Ervin, Glenn
 

I’ve never gotten it to work, I’ve tried several times since it came out.

Glenn

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sarah k Alawami
Sent: Thursday, June 07, 2018 12:58 PM
To: nvda list list
Subject: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

 

I  Actually did not take part in the  crowd funding  as I didn't believe this add on would ever happen, and I knew one of the devs so perosnally did not crowd fund it, I just will not go thee, not here.

 

Anyway yeah any way to get hold of the devs of the remote add on and ask them to please fix? At least for some  of us who use it. I only used it once and that was this year.

 

Here's hoping for a fix eh?



On Jun 7, 2018, at 10:23 AM, Mallard <mallard@...> wrote:

 

Considering that, unlike other add-ons, we all crowdfunded the development of this very add-on, I'd hope something is done about it very soon,





Il 07/06/2018 18:14, Joseph Lee ha scritto:


Hi all,

The below notice is considered critical:

It’s happening again: with the introduction of wxPython 4 in next snapshots, users of NVDA Remote add-on are having startup issues related to missing attribute in wxPython 4.

I propose the following solutions:

 * I highly recommend releasing Remote add-on 2.2 to fix this issue.
 * Perhaps adding a statement on nvdaremote.com website explaining
   that Remote add-on should be disabled if using recent NVDA next
   snapshots.
 * The community should release an updated version of this add-on
   with permission from add-on authors and maintainers.

Thanks.

Cheers,

Joseph




 


portable HTML editor with auto-complete function

 

Hi list,
which program you can recommand for editing HTML files with autocomplete bzw. auto tagging so that the system or program writes the close tag of e.g. "<ol>" automatically? For Linux users we use bluefish based on GTK framework. When I write "<ol>" the program writes for a complete tag the string "</ol>" automatically.
Is e.g. notepad++ able to do that? I am searching for a portable app.
Greetings,
Wolfram


Re: end of the line for nvda skype group

Sarah k Alawami
 

Check out zoom. I use it for all of my business meetings and I have not touched team talk since. You can do screen sharing (yes  that is accessible) ) and moe with it. Other  users can call in by phone if they want to or need to. I really love it.

On Jun 7, 2018, at 2:56 AM, Shaun Everiss <sm.everiss@...> wrote:

It looks like its not completely the end.

It appears for 7 and 8 users we will have to just not install the skype classic update.

For 10 users, it appears microsoft have left us alone.

Previded we can get the skype classic program, ms doesn't ask us to switch over to the universal.

So at least for the moment they are leaving us alone who knows how long that is but still.

I have not as yet tried this.

The nvda skype group didn't have much traffic and I was thinking of pulling out anyway.

Skype isnot a real issue for me as I hardly use it.

Skype web via miranda works for text, now if I can use it to call skype then fine I guess.

There is zello but I have never figured it out as such.

On the other side those of us on android and ios devices will still be able to use skype,.

This seems to effect desktops, that is windows, mac and linux only.

For group chats there is teamtalk, and tthub.org are offering competitive rates right now.

I am interested though in some kind of voip or sip app that is easy to use, accessible and can use as a protocol skype calls, messages, groups and file shares which are the only things I ever use.

If that can be done and if I can login with my skype account then fine.

Right now skype classic still works.

Eventually that may die but who knows.

The skype interface with miranda ng is a bit different, I will have to get used to it but right now well.

I don't use skype enough to justify upgrading to anything new, I barely use that much of skype's power as it is.




On 6/7/2018 9:00 PM, Brian's Mail list account via Groups.Io wrote:
I have to say its not been used here for almost a year now.
I find it irritating that such a simple system is not being made available in a basic form for low tech users and without the flashy front end changes every fortnight. Skype always had a reputation of bringing out improvements that broke it, and it seems this has not stopped with Microsoft owning it, sadly.
So what else is out there for desktop machines for good quality audio over the internet free?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Shaun Everiss" <sm.everiss@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, June 06, 2018 8:31 PM
Subject: [nvda] end of the line for nvda skype group


Hi all of you.

Pulling out of nvda skype group now because of 1, skypes uncertain future and 2. the fact I hardly contribute to it, I will shift all my conversational contributions to this list from now on if I havn't allready.

I will still use skype classic for family, but due to things as they stand I may have to remove skype from my contact and other info, it will be email for internationals only, skype if they need, but I will no longer advertise.

Microsoft has lost another user, skype classic interface is easy to understand, the new one I just don't care for.

Its a pitty its got to end this way but I may as well cut my losses right now rather than having to bother with things going bang.

I will have to either search for another solution or start paying high charges for international calls because skype new versions are inaccessible.

Way to go ms.

Can't skype classic just be pulled from the update loop and still be kept active?













Re: Addint a Desktop Shortcut for Programs or Apps under Windows 10

Sarah k Alawami
 

That's actually how I was trained. I was not trained in any short cut keys. I had to find them on my own.

Take care

On Jun 7, 2018, at 7:36 AM, Ervin, Glenn <glenn.ervin@...> wrote:

I don’t make folders often enough to have known that command.
We have so many things to remember as it is in our daily lives including all the passwords and changing systems that we have to draw the line sometimes.
On the desktop and elsewhere, I just found it easier to unselect anything and use the applications key to go to “new” and then enter on “Folder”.
 
Glenn
 
 
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Wednesday, June 06, 2018 7:54 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Addint a Desktop Shortcut for Programs or Apps under Windows 10
 
I expect to see such commands documented when moving threw menus and submenus.  It should not be necessary for a skilled user, who learns a lot about Windows and programs by looking through menus and dialogs to have to look at a commands sheet when it is expected that accelerator or shortcut commands will be shown in menus. 
 
Also, material that I consider to be among the best produced doesn't mention this command.  I doubt that more than perhaps ten or twenty percent of blind users know this command.
 
Gene
----- Oreiginal Message -----
Sent: Wednesday, June 06, 2018 7:48 PM
Subject: Re: [nvda] Addint a Desktop Shortcut for Programs or Apps under Windows 10
 
On Wed, Jun 6, 2018 at 05:32 pm, Gene wrote:
I'm not surprised. 
Well, I still am.   CTRL+SHIFT+N has been on Microsoft issued keyboard shortcuts lists for a very long time now.

If you go to the Keyboard Shortcuts in Windowswebpage, as it exists today, it shows up whether you choose All Products, Windows 7, Windows 8.1, or Windows 10 from the dropdown for Product Version at the top of the page.

They've also been calling these keyboard shortcuts for as long as I can remember now, but I do recall the "accelerator command" terminology in the mists of memory.  I think that went out as of Windows XP, but can't be certain.  It may have been with the introduction of Windows 7.
 
-- 
Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  
     Explanations exist; they have existed for all time; there is always a well-known solution to every human problem — neat, plausible, and wrong.
          ~ H.L. Mencken, AKA The Sage of Baltimore

 

 



Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

Sarah k Alawami
 

I  Actually did not take part in the  crowd funding  as I didn't believe this add on would ever happen, and I knew one of the devs so perosnally did not crowd fund it, I just will not go thee, not here.

Anyway yeah any way to get hold of the devs of the remote add on and ask them to please fix? At least for some  of us who use it. I only used it once and that was this year.

Here's hoping for a fix eh?

On Jun 7, 2018, at 10:23 AM, Mallard <mallard@...> wrote:

Considering that, unlike other add-ons, we all crowdfunded the development of this very add-on, I'd hope something is done about it very soon,





Il 07/06/2018 18:14, Joseph Lee ha scritto:

Hi all,

The below notice is considered critical:

It’s happening again: with the introduction of wxPython 4 in next snapshots, users of NVDA Remote add-on are having startup issues related to missing attribute in wxPython 4.

I propose the following solutions:

 * I highly recommend releasing Remote add-on 2.2 to fix this issue.
 * Perhaps adding a statement on nvdaremote.com website explaining
   that Remote add-on should be disabled if using recent NVDA next
   snapshots.
 * The community should release an updated version of this add-on
   with permission from add-on authors and maintainers.

Thanks.

Cheers,

Joseph





Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

 

Hi,

Will need to test that this weekend. There is a more urgent problem I just confirmed that I’m debugging at the moment.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of The Wolf
Sent: Thursday, June 7, 2018 10:57 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

 

will this effect dictation bridge as well?

 

On 6/7/2018 9:14 AM, Joseph Lee wrote:

Hi all,

 

The below notice is considered critical:

 

It’s happening again: with the introduction of wxPython 4 in next snapshots, users of NVDA Remote add-on are having startup issues related to missing attribute in wxPython 4.

 

I propose the following solutions:

 

  • I highly recommend releasing Remote add-on 2.2 to fix this issue.
  • Perhaps adding a statement on nvdaremote.com website explaining that Remote add-on should be disabled if using recent NVDA next snapshots.
  • The community should release an updated version of this add-on with permission from add-on authors and maintainers.

 

Thanks.

Cheers,

Joseph



-- 
check out my song on youtube
https://youtu.be/YeWgx2LRu7Y
 


Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

 

will this effect dictation bridge as well?


On 6/7/2018 9:14 AM, Joseph Lee wrote:

Hi all,

 

The below notice is considered critical:

 

It’s happening again: with the introduction of wxPython 4 in next snapshots, users of NVDA Remote add-on are having startup issues related to missing attribute in wxPython 4.

 

I propose the following solutions:

 

  • I highly recommend releasing Remote add-on 2.2 to fix this issue.
  • Perhaps adding a statement on nvdaremote.com website explaining that Remote add-on should be disabled if using recent NVDA next snapshots.
  • The community should release an updated version of this add-on with permission from add-on authors and maintainers.

 

Thanks.

Cheers,

Joseph


-- 
check out my song on youtube
https://youtu.be/YeWgx2LRu7Y


WG: [nvda-addons] Invitation: a three-part seminar on introduciton to NVDA tech support for trainers

Adriani Botez
 

 

 

Von: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> Im Auftrag von Joseph Lee
Gesendet: Montag, 4. Juni 2018 17:36
An: 'NVDA screen reader development' <nvda-devel@...>
Betreff: [nvda-addons] Invitation: a three-part seminar on introduciton to NVDA tech support for trainers

 

Dear NVDA community,

 

At the 2018 NVDACon, I hosted a session about product technical support. I talked about what tech support really is and how it works, along with applying general principles to NVDA community and gave three reasons – product, people, movement – why people should invest time in future-proofing NVDA through tech support. Given that many of you met NVDA through user forums and other tech support venues, I proposed during the session a three-part seminar on introduction to NVDA tech support. I’d like to announce that this seminar will be held this summer, likely towards end of June. Due to facility issues, we won’t be using TeamTalk for this, but I’d be happy to conduct this over Zoom (which is accessible, by the way).

 

The overall purpose of this seminar is to equip individuals to provide more effective tech support for NVDA users. Anyone interested in providing such a service, especially certified NVDA experts around the world and organizations seeking to provide localized tech support are highly encouraged to attend this seminar series. The seminar series will take place over the course of three Saturdays (start date and how to join the seminar will be communicated to you soon) and will involve hands-on demonstrations and mock scenarios.

 

Seminar outline:

 

  • Day 1: introduction to technical support and deeper overview of NVDA concepts

 

In this seminar, you’ll be introduced to what tech support is and how it works, as well as a deeper overview of NVDA concepts you need to know for tech support such as object navigation, review cursor, user interface and other topics.

 

  • Day 2: Recognize and troubleshoot common problems and tech support etiquette

 

In this seminar, we’ll dive into common problems users encounter, as well as how to troubleshoot these and common steps to take when troubleshooting various issues, including dealing with add-ons, problem reproduction and others. We’ll also learn how to make impact on users through etiquette when providing tech support.

 

  • Day 3: deciphering NVDA logs and additional tech support resources

 

In this seminar, we’ll learn how to read and understand NVDA log files, including different log levels, where log files are stored, as well as common errors seen in logs. We’ll also talk about additional tech support resources for users.

 

  • Day 4 (optional): dealing with add-ons

 

This seminar, if requested by high demand, will look at what exactly NVDA add-ons are and how to spot issues when using them. Topics include how to enable or disable individual or all add-ons at once, troubleshooting issues related to add-on conflicts, gesture assignments, and communicating with add-on authors.

 

  • Additional training seminars if requested.

 

If anyone is interested in this seminar series, please do let me know privately (email or Twitter will do; if using Twitter, my handle is joslee).

 

Thanks.

Cheers,

Joseph


Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

Adriani Botez
 

My statement applies in case it is known that the addon causes the conflict and not the implementation of WX 4 in NVDA.

 

Best

Adriani

 

 

 

Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Adriani Botez
Gesendet: Donnerstag, 7. Juni 2018 19:33
An: nvda@nvda.groups.io; 'NVDA screen reader development' <nvda-devel@...>
Betreff: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

 

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.

 

 

Best

Adriani

 

 

Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Joseph Lee
Gesendet: Donnerstag, 7. Juni 2018 19:08
An: nvda@nvda.groups.io; 'NVDA screen reader development' <nvda-devel@...>
Betreff: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

 

Hi Jonathan,

I think multiple factors are involved:

  • Need to move to Python 3: we’re researching foundations to move to Python 3 in the end, and wxPython 4 is the last dependency we need at this point.
  • wxPython 4: this version changes internals a bit, thus we ran into problems that we didn’t expect. Earlier this week I reported a problem where if you open a settings dialog and close it, NVDA won’t let you open others. This was fixed yesterday.
  • Attitudes from add-on authors about keeping up to date: we have add-ons that were written with old technology in mind, and it takes a bit of work to update the code to use newer interfaces and assumptions. Ideally add-on authors should do this themselves, but sometimes the community finds itself having to either locate the author or do the work ourselves. For the last twelve months, I’ve been telling the add-ons community to prepare for a day like this: making sure their add-on code works reliably with wxPython 4.
  • Inadequate preparations: we’re not adequately prepared enough as a community to help people affected by cases like Remote add-on, mostly having to do with attitudes and assumptions. I admit that I’m not free from taking the blame for the state of the add-ons community when it comes to preparing for wxPython 4, let alone Python 3 transition in the future. To me, if users cannot use their add-ons due to issues with wxPython 4 and Python 3, then I take it as a personal failure.

 

Cheers,

Joseph

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Cohn, Jonathan
Sent: Thursday, June 7, 2018 9:45 AM
To: nvda@nvda.groups.io; '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.

 

Thanks,

 

Jonathan Cohn

  


Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

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.

 

 

Best

Adriani

 

 

Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Joseph Lee
Gesendet: Donnerstag, 7. Juni 2018 19:08
An: nvda@nvda.groups.io; 'NVDA screen reader development' <nvda-devel@...>
Betreff: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

 

Hi Jonathan,

I think multiple factors are involved:

  • Need to move to Python 3: we’re researching foundations to move to Python 3 in the end, and wxPython 4 is the last dependency we need at this point.
  • wxPython 4: this version changes internals a bit, thus we ran into problems that we didn’t expect. Earlier this week I reported a problem where if you open a settings dialog and close it, NVDA won’t let you open others. This was fixed yesterday.
  • Attitudes from add-on authors about keeping up to date: we have add-ons that were written with old technology in mind, and it takes a bit of work to update the code to use newer interfaces and assumptions. Ideally add-on authors should do this themselves, but sometimes the community finds itself having to either locate the author or do the work ourselves. For the last twelve months, I’ve been telling the add-ons community to prepare for a day like this: making sure their add-on code works reliably with wxPython 4.
  • Inadequate preparations: we’re not adequately prepared enough as a community to help people affected by cases like Remote add-on, mostly having to do with attitudes and assumptions. I admit that I’m not free from taking the blame for the state of the add-ons community when it comes to preparing for wxPython 4, let alone Python 3 transition in the future. To me, if users cannot use their add-ons due to issues with wxPython 4 and Python 3, then I take it as a personal failure.

 

Cheers,

Joseph

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Cohn, Jonathan
Sent: Thursday, June 7, 2018 9:45 AM
To: nvda@nvda.groups.io; '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.

 

Thanks,

 

Jonathan Cohn

  


Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

Mallard
 

Considering that, unlike other add-ons, we all crowdfunded the development of this very add-on, I'd hope something is done about it very soon,

Il 07/06/2018 18:14, Joseph Lee ha scritto:

Hi all,

The below notice is considered critical:

It’s happening again: with the introduction of wxPython 4 in next snapshots, users of NVDA Remote add-on are having startup issues related to missing attribute in wxPython 4.

I propose the following solutions:

* I highly recommend releasing Remote add-on 2.2 to fix this issue.
* Perhaps adding a statement on nvdaremote.com website explaining
that Remote add-on should be disabled if using recent NVDA next
snapshots.
* The community should release an updated version of this add-on
with permission from add-on authors and maintainers.

Thanks.

Cheers,

Joseph


Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

 

Hi Jonathan,

I think multiple factors are involved:

  • Need to move to Python 3: we’re researching foundations to move to Python 3 in the end, and wxPython 4 is the last dependency we need at this point.
  • wxPython 4: this version changes internals a bit, thus we ran into problems that we didn’t expect. Earlier this week I reported a problem where if you open a settings dialog and close it, NVDA won’t let you open others. This was fixed yesterday.
  • Attitudes from add-on authors about keeping up to date: we have add-ons that were written with old technology in mind, and it takes a bit of work to update the code to use newer interfaces and assumptions. Ideally add-on authors should do this themselves, but sometimes the community finds itself having to either locate the author or do the work ourselves. For the last twelve months, I’ve been telling the add-ons community to prepare for a day like this: making sure their add-on code works reliably with wxPython 4.
  • Inadequate preparations: we’re not adequately prepared enough as a community to help people affected by cases like Remote add-on, mostly having to do with attitudes and assumptions. I admit that I’m not free from taking the blame for the state of the add-ons community when it comes to preparing for wxPython 4, let alone Python 3 transition in the future. To me, if users cannot use their add-ons due to issues with wxPython 4 and Python 3, then I take it as a personal failure.

 

Cheers,

Joseph

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Cohn, Jonathan
Sent: Thursday, June 7, 2018 9:45 AM
To: nvda@nvda.groups.io; '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.

 

Thanks,

 

Jonathan Cohn

  


Re: Latest next, cannot add entries to a dictionnary

 

Hi,
I'll take a look, as I can confirm this problem.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michel Such
Sent: Thursday, June 7, 2018 10:02 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Latest next, cannot add entries to a dictionnary

It is next 15184,0771d5d7



Michel Such

Le 07/06/2018 à 18:48, Joseph Lee a écrit :
Hi,
Which next snapshot build do you have?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michel
Such
Sent: Thursday, June 7, 2018 9:44 AM
To: nvda@nvda.groups.io
Subject: [nvda] Latest next, cannot add entries to a dictionnary

Hi all,


I guess it comes from migration to WXPython 4.01 which needs some adjustments, bu I just noticed that at this point it is impossible to add something to a pronunciation dictionnary.


Another thing I'm not completely sure of, it seems that, when closing some dialogs, the window which contained them remains on screen but is nomore accessible.

I suppose that because my wife looked at my sreen and told me I had 6
or
7 NVDA Windows on it.



Re: Latest next, cannot add entries to a dictionnary

Michel Such
 

It is next 15184,0771d5d7



Michel Such

Le 07/06/2018 à 18:48, Joseph Lee a écrit :
Hi,
Which next snapshot build do you have?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michel Such
Sent: Thursday, June 7, 2018 9:44 AM
To: nvda@nvda.groups.io
Subject: [nvda] Latest next, cannot add entries to a dictionnary

Hi all,


I guess it comes from migration to WXPython 4.01 which needs some adjustments, bu I just noticed that at this point it is impossible to add something to a pronunciation dictionnary.


Another thing I'm not completely sure of, it seems that, when closing some dialogs, the window which contained them remains on screen but is nomore accessible.

I suppose that because my wife looked at my sreen and told me I had 6 or
7 NVDA Windows on it.



Re: Latest next, cannot add entries to a dictionnary

 

Hi,
Which next snapshot build do you have?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michel Such
Sent: Thursday, June 7, 2018 9:44 AM
To: nvda@nvda.groups.io
Subject: [nvda] Latest next, cannot add entries to a dictionnary

Hi all,


I guess it comes from migration to WXPython 4.01 which needs some adjustments, bu I just noticed that at this point it is impossible to add something to a pronunciation dictionnary.


Another thing I'm not completely sure of, it seems that, when closing some dialogs, the window which contained them remains on screen but is nomore accessible.

I suppose that because my wife looked at my sreen and told me I had 6 or
7 NVDA Windows on it.



--


Michel Such