1. nvda@nvda.groups.io
   Date   
Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

The Wolf
 

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

Joseph Lee
 

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

Joseph Lee
 

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

Joseph Lee
 

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
Re: Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

Jonathan COHN
 

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

  
Latest next, cannot add entries to a dictionnary

Michel Such
 

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
Re: Problem with last "NVDA next" and "Remote Support

Ângelo Abrantes
 

Hi,
I downloaded it today, about an hour ago.

I think after that there have not been updates yet.
Thanks
Ângelo Abrantes

Às 17:06 de 07-06-2018, Joseph Lee escreveu:

Hi,
And there has been no update since then? Looks like another community ad-on compatibility notice is in order...
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ângelo Abrantes
Sent: Thursday, June 7, 2018 8:56 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Problem with last "NVDA next" and "Remote Support

Version 2.1, downloaded today from "remote support" page.

Thanks.

Ângelo Abrantes


Às 16:45 de 07-06-2018, Joseph Lee escreveu:
Hi,
Which version of this add-on do you have? The below log is a well-known problem, and I thought add-on authors would have released an updated version to fix this.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ângelo
Abrantes
Sent: Thursday, June 7, 2018 8:40 AM
To: nvda@nvda.groups.io
Subject: [nvda] Problem with last "NVDA next" and "Remote Support

Hi,


Here's a part of my log file:


"DEBUG - addonHandler.Addon.__init__ (16:33:01.305):
Using manifest translation from
C:\Users\Angelo\AppData\Roaming\nvda\addons\systrayList\locale\pt_PT\m
anifest.ini ERROR - globalPluginHandler.initialize (16:33:01.361):
Error initializing global plugin <class
'globalPlugins.remoteClient.GlobalPlugin'>
Traceback (most recent call last):
File "globalPluginHandler.pyc", line 32, in initialize
File
"C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remo
teClient\__init__.py",
line 56, in __init__
File
"C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remo
teClient\__init__.py",
line 104, in create_menu
AttributeError: 'MenuItem' object has no attribute 'SetCheckable'
DEBUG - addonHandler.Addon.__init__ (16:33:01.382):
Using manifest translation from
C:\Users\Angelo\AppData\Roaming\nvda\addons\poeditMadeEasy\locale\en\m
anifest.ini
DEBUG - core.main (16:33:01.413):
Initializing core pump
DEBUG - core.main (16:33:01.413):
Initializing watchdog
DEBUG - core.main (16:33:01.414):
initializing updateCheck
INFO - core.main (16:33:01.414):
NVDA initialized"


Thanks

Ângelo Abrantes


---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus
Add-on compatibility notice: NvDA Remote Support add-on 2.1 is not compatible with wxPython 4, new release recommended

Joseph Lee
 

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: Problem with last "NVDA next" and "Remote Support

Joseph Lee
 

Hi,
And there has been no update since then? Looks like another community ad-on compatibility notice is in order...
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ângelo Abrantes
Sent: Thursday, June 7, 2018 8:56 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Problem with last "NVDA next" and "Remote Support

Version 2.1, downloaded today from "remote support" page.

Thanks.

Ângelo Abrantes


Às 16:45 de 07-06-2018, Joseph Lee escreveu:
Hi,
Which version of this add-on do you have? The below log is a well-known problem, and I thought add-on authors would have released an updated version to fix this.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ângelo
Abrantes
Sent: Thursday, June 7, 2018 8:40 AM
To: nvda@nvda.groups.io
Subject: [nvda] Problem with last "NVDA next" and "Remote Support

Hi,


Here's a part of my log file:


"DEBUG - addonHandler.Addon.__init__ (16:33:01.305):
Using manifest translation from
C:\Users\Angelo\AppData\Roaming\nvda\addons\systrayList\locale\pt_PT\m
anifest.ini ERROR - globalPluginHandler.initialize (16:33:01.361):
Error initializing global plugin <class
'globalPlugins.remoteClient.GlobalPlugin'>
Traceback (most recent call last):
File "globalPluginHandler.pyc", line 32, in initialize
File
"C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remo
teClient\__init__.py",
line 56, in __init__
File
"C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remo
teClient\__init__.py",
line 104, in create_menu
AttributeError: 'MenuItem' object has no attribute 'SetCheckable'
DEBUG - addonHandler.Addon.__init__ (16:33:01.382):
Using manifest translation from
C:\Users\Angelo\AppData\Roaming\nvda\addons\poeditMadeEasy\locale\en\m
anifest.ini
DEBUG - core.main (16:33:01.413):
Initializing core pump
DEBUG - core.main (16:33:01.413):
Initializing watchdog
DEBUG - core.main (16:33:01.414):
initializing updateCheck
INFO - core.main (16:33:01.414):
NVDA initialized"


Thanks

Ângelo Abrantes


---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus
Re: Problem with last "NVDA next" and "Remote Support

Ângelo Abrantes
 

Version 2.1, downloaded today from "remote support" page.

Thanks.

Ângelo Abrantes


Às 16:45 de 07-06-2018, Joseph Lee escreveu:

Hi,
Which version of this add-on do you have? The below log is a well-known problem, and I thought add-on authors would have released an updated version to fix this.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ângelo Abrantes
Sent: Thursday, June 7, 2018 8:40 AM
To: nvda@nvda.groups.io
Subject: [nvda] Problem with last "NVDA next" and "Remote Support

Hi,


Here's a part of my log file:


"DEBUG - addonHandler.Addon.__init__ (16:33:01.305):
Using manifest translation from
C:\Users\Angelo\AppData\Roaming\nvda\addons\systrayList\locale\pt_PT\manifest.ini
ERROR - globalPluginHandler.initialize (16:33:01.361):
Error initializing global plugin <class 'globalPlugins.remoteClient.GlobalPlugin'>
Traceback (most recent call last):
File "globalPluginHandler.pyc", line 32, in initialize
File
"C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py",
line 56, in __init__
File
"C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py",
line 104, in create_menu
AttributeError: 'MenuItem' object has no attribute 'SetCheckable'
DEBUG - addonHandler.Addon.__init__ (16:33:01.382):
Using manifest translation from
C:\Users\Angelo\AppData\Roaming\nvda\addons\poeditMadeEasy\locale\en\manifest.ini
DEBUG - core.main (16:33:01.413):
Initializing core pump
DEBUG - core.main (16:33:01.413):
Initializing watchdog
DEBUG - core.main (16:33:01.414):
initializing updateCheck
INFO - core.main (16:33:01.414):
NVDA initialized"


Thanks

Ângelo Abrantes


---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus
Re: Problem with last "NVDA next" and "Remote Support

Joseph Lee
 

Hi,
Which version of this add-on do you have? The below log is a well-known problem, and I thought add-on authors would have released an updated version to fix this.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ângelo Abrantes
Sent: Thursday, June 7, 2018 8:40 AM
To: nvda@nvda.groups.io
Subject: [nvda] Problem with last "NVDA next" and "Remote Support

Hi,


Here's a part of my log file:


"DEBUG - addonHandler.Addon.__init__ (16:33:01.305):
Using manifest translation from
C:\Users\Angelo\AppData\Roaming\nvda\addons\systrayList\locale\pt_PT\manifest.ini
ERROR - globalPluginHandler.initialize (16:33:01.361):
Error initializing global plugin <class 'globalPlugins.remoteClient.GlobalPlugin'>
Traceback (most recent call last):
File "globalPluginHandler.pyc", line 32, in initialize
File
"C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py",
line 56, in __init__
File
"C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py",
line 104, in create_menu
AttributeError: 'MenuItem' object has no attribute 'SetCheckable'
DEBUG - addonHandler.Addon.__init__ (16:33:01.382):
Using manifest translation from
C:\Users\Angelo\AppData\Roaming\nvda\addons\poeditMadeEasy\locale\en\manifest.ini
DEBUG - core.main (16:33:01.413):
Initializing core pump
DEBUG - core.main (16:33:01.413):
Initializing watchdog
DEBUG - core.main (16:33:01.414):
initializing updateCheck
INFO - core.main (16:33:01.414):
NVDA initialized"


Thanks

Ângelo Abrantes


---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus
Problem with last "NVDA next" and "Remote Support

Ângelo Abrantes
 

Hi,


Here's a part of my log file:


"DEBUG - addonHandler.Addon.__init__ (16:33:01.305):
Using manifest translation from C:\Users\Angelo\AppData\Roaming\nvda\addons\systrayList\locale\pt_PT\manifest.ini
ERROR - globalPluginHandler.initialize (16:33:01.361):
Error initializing global plugin <class 'globalPlugins.remoteClient.GlobalPlugin'>
Traceback (most recent call last):
  File "globalPluginHandler.pyc", line 32, in initialize
  File "C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py", line 56, in __init__
  File "C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py", line 104, in create_menu
AttributeError: 'MenuItem' object has no attribute 'SetCheckable'
DEBUG - addonHandler.Addon.__init__ (16:33:01.382):
Using manifest translation from C:\Users\Angelo\AppData\Roaming\nvda\addons\poeditMadeEasy\locale\en\manifest.ini
DEBUG - core.main (16:33:01.413):
Initializing core pump
DEBUG - core.main (16:33:01.413):
Initializing watchdog
DEBUG - core.main (16:33:01.414):
initializing updateCheck
INFO - core.main (16:33:01.414):
NVDA initialized"


Thanks

Ângelo Abrantes


---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus
NVDA and Google Play?

David Russell
 

Hi NVDA Group,

In April, I signed up for, and purchased two books to read from my
desktop on Google Play. All was well until last evening when I could
not access either title. It had been a couple weeks since I had read
one of the two titles there.

Everything appears "collapsed" contents, navigation, and any other
identified links when using the up or down arrow keys when in Google
Play itself.
When going to previous or next page in the document, NVDA reads, Oops
page cannot be opened - or something like that.
Of course, getting help from Google is near impossible. Trying to
refresh FireFox with the f5 key from both the address bar, and in
Google Play itself, does not change things.
Any ideas on how to make reading once again accessible?

Thanks in advance.
--
David Russell
david.sonofhashem@gmail.com
Re: Addint a Desktop Shortcut for Programs or Apps under Windows 10

Ervin, Glenn
 

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 -----

From: Brian Vogel

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 Windows webpage, 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: Path On Portable Copy

Ervin, Glenn
 

What I had to do was to group the folder by date, and at the bottom of the list was:
"today"
And I just deleted that, since the only thing I put in that folder that day was NVDA.
That was scary, not knowing all the things you are deleting, because on a portable drive, the way my computer is set up, there is no recycle bin.
Glenn

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian's Mail list account via Groups.Io
Sent: Wednesday, June 06, 2018 11:48 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Path On Portable Copy

No it never did this, it was a bit of an argument about whether it should or
not but it seems the result was inconclusive. personally I'd have preferred
that it defaulted to nvda, and gave the option to change it much like zip
does for extracting files, but I never did see this done.
Basically you can normally tell the files by their dates and times, so one
can easily remove them or more usefully copy them to a new folder called
nvda. At least then if it won't work you know you missed some!


Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Ervin, Glenn" <glenn.ervin@nebraska.gov>
To: <nvda@nvda.groups.io>
Sent: Tuesday, June 05, 2018 5:41 PM
Subject: [nvda] Path On Portable Copy


Hi,
I just tried to make a portable copy of NVDA, after updating my local copy.
I gave it the right drive path, but I did not specify \NVDA
This made a mess in my drive and I hope I only deleted the NVDA files in
order to re-do it.
I have made portable copies of NVDA many times before.
I thought that it automatically made the NVDA directory.
Did this change?
I would think that by default, it should create a folder called \NVDA.
Glenn
Glenn Ervin Orientation Counselor II
Norfolk Nebraska
402 370 3436
Cell: 402 992 0325
[NCBVI"AJC Email Logo]<../../../../Documents/NCBVI%22AJC%20Email%20Logo.png>
Welcome | NCBVI<https://ncbvi.nebraska.gov/>
40961 - 40980 of 82059