From: Andy B.
Sent: Friday, July 26, 2019 9:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Using Alpha snapshot 18199 Python 3 and my experiences!

 

I will start providing logs to nvda-dev soon. Here is one to get you started…

 

NVDA latest alpha snapshot, Windows 10 1903, Chrome 75, EspeakNg.

 

1. In Chrome, go to www.google.com.
2. In the search field, type any search terms. I used “test”
3. Press enter to perform the search.

 

Actual results: Google.com in Chrome performs the search as expected. However, an error tone sounds after resuming browse mode. The log follows.

 

ERROR - eventHandler.executeEvent (21:17:37.321):

error executing event: typedCharacter on <NVDAObjects.Dynamic_EditableTextWithAutoSelectDetectionEditorIa2WebIAccessible object at 0x071BE770> with extra args of {'ch': '\r'}

Traceback (most recent call last):

  File "eventHandler.pyc", line 155, in executeEvent

  File "eventHandler.pyc", line 92, in __init__

  File "eventHandler.pyc", line 100, in next

  File "NVDAObjects\__init__.pyc", line 980, in event_typedCharacter

  File "speech\__init__.pyc", line 695, in speakTypedCharacters

  File "api.pyc", line 247, in isTypingProtected

  File "baseObject.pyc", line 46, in __get__

  File "baseObject.pyc", line 149, in _getPropertyViaCache

  File "NVDAObjects\__init__.pyc", line 854, in _get_isProtected

  File "baseObject.pyc", line 46, in __get__

  File "baseObject.pyc", line 149, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\ia2Web.pyc", line 58, in _get_states

  File "baseObject.pyc", line 46, in __get__

  File "baseObject.pyc", line 149, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\__init__.pyc", line 866, in _get_states

  File "comtypesMonkeyPatches.pyc", line 22, in __call__

_ctypes.COMError: (-2147467259, 'Unspecified error', (None, None, None, 0, None))

 

Expected results: NVDA should not sound an error after doing a Google search, and the log should not indicate any errors.

 

Sent from Mail for Windows 10

 

 

Hi,

For others also: if you do run into issues with add-ons, please contact add-on authors.

In regards to Windows 10 apps, at least my add-on should be seen as enabled.

In any case, we need a log please.

Cheers,

Joseph

 

 

Hi all!

I am using the Python three 18199 latest alpha snapshot.

Experiences so far!

It works better in the Win10 Mail app than it ever has.

I get many error sounds, but I ignore them.

With Google Chrome, is very sluggish and I hear many error sounds.

I am having trouble navigating by form field especially.

In many other Win10 apps, is very sluggish, and is shutting down and coming back on!

Some examples:

News app, One Note, Weather app, and the MS store.

I am using one core voices, because decktalk add-on no longer works.

Some of the English eSpeak voices are not as clear.

In the settings app, it is not giving as much info and I have to press NVDA+Tab a lot to get that info.

These are my experiences so far.

I just want people to know what I have found so far!

Over all, it is working very well for Python 3.

This is very promising.

I can’t wait to get a lot of my add-ons back.

David Moore

 

Sent from Mail for Windows 10

 

From: Joseph Lee
Sent: Friday, July 26, 2019 9:19 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Using Alpha snapshot 18199 Python 3 and my experiences!

 

Hi,

For others also: if you do run into issues with add-ons, please contact add-on authors.

In regards to Windows 10 apps, at least my add-on should be seen as enabled.

In any case, we need a log please.

Cheers,

Joseph

 

 

Hi all!

I am using the Python three 18199 latest alpha snapshot.

Experiences so far!

It works better in the Win10 Mail app than it ever has.

I get many error sounds, but I ignore them.

With Google Chrome, is very sluggish and I hear many error sounds.

I am having trouble navigating by form field especially.

In many other Win10 apps, is very sluggish, and is shutting down and coming back on!

Some examples:

News app, One Note, Weather app, and the MS store.

I am using one core voices, because decktalk add-on no longer works.

Some of the English eSpeak voices are not as clear.

In the settings app, it is not giving as much info and I have to press NVDA+Tab a lot to get that info.

These are my experiences so far.

I just want people to know what I have found so far!

Over all, it is working very well for Python 3.

This is very promising.

I can’t wait to get a lot of my add-ons back.

David Moore

 

Sent from Mail for Windows 10

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of David Moore
Sent: Friday, July 26, 2019 5:58 PM
To: nvda@nvda.groups.io
Subject: [nvda] Using Alpha snapshot 18199 Python 3 and my experiences!

 

Hi all!

I am using the Python three 18199 latest alpha snapshot.

Experiences so far!

It works better in the Win10 Mail app than it ever has.

I get many error sounds, but I ignore them.

With Google Chrome, is very sluggish and I hear many error sounds.

I am having trouble navigating by form field especially.

In many other Win10 apps, is very sluggish, and is shutting down and coming back on!

Some examples:

News app, One Note, Weather app, and the MS store.

I am using one core voices, because decktalk add-on no longer works.

Some of the English eSpeak voices are not as clear.

In the settings app, it is not giving as much info and I have to press NVDA+Tab a lot to get that info.

These are my experiences so far.

I just want people to know what I have found so far!

Over all, it is working very well for Python 3.

This is very promising.

I can’t wait to get a lot of my add-ons back.

David Moore

 

Sent from Mail for Windows 10

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of David Moore
Sent: 26 July 2019 21:32
To: nvda@nvda.groups.io
Subject: Re: [nvda] Is there an ad-on for Duxbury or one coming?

 

I lost the use of Dux berry add-on as well.

Will there be an update?

David Moore

 

Sent from Mail for Windows 10

 

 

I may have been on this list several years ago but had forgotten all about it. I am glad to be back on it once again.

 

I read the guidelines but they were a little confusing to me as it seemed to say something different in two different sections. If I am out of line with my question just let me know.

 

I use NVDA all of the time on my laptop and would love to use it for all of the programs that I have to use. Are there any plans or is there already and ad-on that I do not know about for Duxbury?

 

Thank you so much for any assistance that you can give me.

 

Betsy in Georgia

From: Betsy Grenevitch
Sent: Friday, July 26, 2019 9:02 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Is there an ad-on for Duxbury or one coming?

 

I may have been on this list several years ago but had forgotten all about it. I am glad to be back on it once again.

 

I read the guidelines but they were a little confusing to me as it seemed to say something different in two different sections. If I am out of line with my question just let me know.

 

I use NVDA all of the time on my laptop and would love to use it for all of the programs that I have to use. Are there any plans or is there already and ad-on that I do not know about for Duxbury?

 

Thank you so much for any assistance that you can give me.

 

Betsy in Georgia

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Sent: Friday, July 26, 2019 8:16 AM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda] Various add-on updates: Easy Table Navigator, Enhanced Touch Gestures, Golden Cursor, Screen Curtain and others #AddonRelease

 

Hi all,

The add-ons listed below will get updates in about an hour or so:

• Easy Table Navigator
• Enhanced Touch Gestures
• Golden Cursor
• Object location Tones
• ObjPad
• SystrayList
• Virtual Review

 

Most of these resolves compatibility flags issue so people using alpha snapshots can test these add-ons. All of them are Python 3 compatible.

 

About the big announcement I hinted at: up next.

Cheers,

Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of zahra
Sent: Friday, July 26, 2019 8:01 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Community notice: upcoming NVDA 2019.3 and community add-ons

hi joseph.
you mentioned that addons for python3 should use utf8 without bom.
what encoding addons for python2 use now?

On 7/26/19, Joseph Lee <joseph.lee22590@gmail.com> wrote:

Hi NVDA community,

I'm Joseph Lee, a volunteer code contributor for NVDA screen reader
project and the chief investigator for Python 3 work. First, I would
like to thank my colleagues at NV Access and beyond for achieving a
milestone in Python 3
work: alpha snapshots (master branch in source code) being powered by
Python 3.

To the matter at hand: NVDA 2019.3 (Threshold, scheduled for later
this
year) will feature backwards incompatible changes, including speech
refactor and Python 3. Because of this, many community add-ons
(including add-ons hosted on addons.nvda-project.org) will need to be
modified to take advantage of these changes, especially when it comes
to supporting Python 3.
Because Python 2 to 3 transition is a huge undertaking, I expect
add-ons community will take several weeks to months (or longer) to
transition vast majority of add-ons to Python 3, and collaboration is
a key to success in this endeavor.

The following is a set of steps members of the community should take:



For add-on authors:

1. Prepare your mindset for Python 3 by reading several porting guides.
The official one can be found at
https://docs.python.org/3/howto/pyporting.html. Another useful one
(titled Conservative Python 3 Porting Guide) can be found at
https://portingguide.readthedocs.io/en/latest/.
2. If you haven't done so, please install Python 3.7 so you can
experiment with differences between Python 2 and 3.
3. Once you are comfortable with Python 3, please test your add-on(s)
with latest NVDA alpha snapshots, preferably with build 18195 or
later. If you need to keep using current add-ons or need to compare
Python 2 versus 3, please use a portable copy of NVDA to test your
add-ons.
4. Make necessary changes. It is up to you in regards to supporting
older NVDA releases or not; if yes, you must write code compatible
with both Python 2 and 3, otherwise please use Python 3.
5. After testing your add-ons, please release a Python 3 version of
your add-on(s) for testing. You can either use development channel or
a separate package. As you do so, please send a notice to the NVDA
community regarding your add-ons and their compatibility with upcoming NVDA release.
6. Please listen to feedback and make changes based on what users are
saying.
7. I advise completing Python 3 transition work for add-ons by end of
this year, or by 2019.3 RC if possible. Although it won't be a while
before beta comes out, targeting release candidate ensures changes can
be made based on feedback from beta testers.
8. Keep listening to feedback after NvDA 2019.3 stable is released and
make necessary changes if any.



For users:

1. If you are adventurous, please test alpha snapshots as a portable
copy. I don't advise using an install copy for now until your favorite
add-ons are declared compatible.
2. Please send feedback to add-on authors if you find issues with
add-ons. An announcement has been posted on community add-ons website
detailing compatible add-ons, issues with incompatible add-ons, and
contact information for authors. The announcement can be found at
https://addons.nvda-project.org/addons/nvdapy3.en.html.
3. When authors announce add-on compatibility notices, please read
those notices and take note of issues.



Frequently asked questions:



Q. Can I make an add-on "compatible" by editing the manifest file?

No. Although it'll give you a sense of "assurance" that your add-on
will be considered "compatible" by NVDA, you will need to obtain a
version of an add-on compatible with Python 3, speech refactor, and other changes.



Q. I need to report issues with add-ons not found on community add-ons
website.

For these (especially speech synthesizer add-ons), you must contact
the authors listed under Add-ons Manager.



Q. I am using an add-on that is declared compatible, yet NVDA won't
load due to an error about configobj.

This is caused by manifest file encoding. Add-ons must now use UTF-8
(without BOM). Vocalizer (add-on 2.x) is affected by this bug and
possibly others.



Q. When starting NVDA, I get a runtime error and it becomes silent.

The most likely cause is an add-on that uses a C extension (.pyd)
module that won't work properly on Python 3. Disabling the add-on will
allow NVDA to proceed with startup. For add-ons affected by this,
authors must now compile C extensions with Visual Studio 2017, the
compiler used to compile Python 3.7.



Q. What about add-ons noted as end of life?

Please contact add-on authors about their plans to support Python 3.
One such add-on is Control Usage Assistant, and I (Joseph Lee) will
make an announcement about it very soon.



Thank you. And with that, let Python 3 porting begin!

Cheers,

Joseph

--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali

On 7/26/19, Joseph Lee <joseph.lee22590@gmail.com> wrote:

Hi NVDA community,

I'm Joseph Lee, a volunteer code contributor for NVDA screen reader project
and the chief investigator for Python 3 work. First, I would like to thank
my colleagues at NV Access and beyond for achieving a milestone in Python 3
work: alpha snapshots (master branch in source code) being powered by
Python
3.

To the matter at hand: NVDA 2019.3 (Threshold, scheduled for later this
year) will feature backwards incompatible changes, including speech
refactor
and Python 3. Because of this, many community add-ons (including add-ons
hosted on addons.nvda-project.org) will need to be modified to take
advantage of these changes, especially when it comes to supporting Python
3.
Because Python 2 to 3 transition is a huge undertaking, I expect add-ons
community will take several weeks to months (or longer) to transition vast
majority of add-ons to Python 3, and collaboration is a key to success in
this endeavor.

The following is a set of steps members of the community should take:



For add-on authors:

1. Prepare your mindset for Python 3 by reading several porting guides.
The official one can be found at
https://docs.python.org/3/howto/pyporting.html. Another useful one (titled
Conservative Python 3 Porting Guide) can be found at
https://portingguide.readthedocs.io/en/latest/.
2. If you haven't done so, please install Python 3.7 so you can
experiment with differences between Python 2 and 3.
3. Once you are comfortable with Python 3, please test your add-on(s)
with latest NVDA alpha snapshots, preferably with build 18195 or later. If
you need to keep using current add-ons or need to compare Python 2 versus
3,
please use a portable copy of NVDA to test your add-ons.
4. Make necessary changes. It is up to you in regards to supporting
older NVDA releases or not; if yes, you must write code compatible with
both
Python 2 and 3, otherwise please use Python 3.
5. After testing your add-ons, please release a Python 3 version of
your add-on(s) for testing. You can either use development channel or a
separate package. As you do so, please send a notice to the NVDA community
regarding your add-ons and their compatibility with upcoming NVDA release.
6. Please listen to feedback and make changes based on what users are
saying.
7. I advise completing Python 3 transition work for add-ons by end of
this year, or by 2019.3 RC if possible. Although it won't be a while before
beta comes out, targeting release candidate ensures changes can be made
based on feedback from beta testers.
8. Keep listening to feedback after NvDA 2019.3 stable is released and
make necessary changes if any.



For users:

1. If you are adventurous, please test alpha snapshots as a portable
copy. I don't advise using an install copy for now until your favorite
add-ons are declared compatible.
2. Please send feedback to add-on authors if you find issues with
add-ons. An announcement has been posted on community add-ons website
detailing compatible add-ons, issues with incompatible add-ons, and contact
information for authors. The announcement can be found at
https://addons.nvda-project.org/addons/nvdapy3.en.html.
3. When authors announce add-on compatibility notices, please read
those notices and take note of issues.



Frequently asked questions:



Q. Can I make an add-on "compatible" by editing the manifest file?

No. Although it'll give you a sense of "assurance" that your add-on will be
considered "compatible" by NVDA, you will need to obtain a version of an
add-on compatible with Python 3, speech refactor, and other changes.



Q. I need to report issues with add-ons not found on community add-ons
website.

For these (especially speech synthesizer add-ons), you must contact the
authors listed under Add-ons Manager.



Q. I am using an add-on that is declared compatible, yet NVDA won't load
due
to an error about configobj.

This is caused by manifest file encoding. Add-ons must now use UTF-8
(without BOM). Vocalizer (add-on 2.x) is affected by this bug and possibly
others.



Q. When starting NVDA, I get a runtime error and it becomes silent.

The most likely cause is an add-on that uses a C extension (.pyd) module
that won't work properly on Python 3. Disabling the add-on will allow NVDA
to proceed with startup. For add-ons affected by this, authors must now
compile C extensions with Visual Studio 2017, the compiler used to compile
Python 3.7.



Q. What about add-ons noted as end of life?

Please contact add-on authors about their plans to support Python 3. One
such add-on is Control Usage Assistant, and I (Joseph Lee) will make an
announcement about it very soon.



Thank you. And with that, let Python 3 porting begin!

Cheers,

Joseph

On Jul 25, 2019, at 2:41 PM, Curtis Delzer <curtis@...> wrote:

which version of k1000 do you have?

Curtis Delzer 
HS
K 6 V F O
Rialto, CA

curtis@...

On 7/17/2019 8:09 PM, Robert Doc Wright godfearer wrote:

I wish I could help. Since January I have not been able to install my copy of Kurzweild. They say I have to upgrade. As if I have an extra $200 just laying around.

 

                                                                                                                                If all I have left in this world is God, I have everything!                                                                                                                                                                                                                                                                                                                                                Sent from Mail for Windows 10

 

From: Luke Davis
Sent: Wednesday, July 17, 2019 1:51 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and Kurzweil 1000

 

I know nothing about K1000, but just as a wild suggestion, have you tried

switching between focus and browse modes? NVDA+space

 

On Tue, 16 Jul 2019, Sile via Groups.Io wrote:

 

> I have just discovered that, under windows 10, I cannot navigate files

> scanned by Kurzweil 1000 using the standard cursor keys. The cursor just sits

> at the first letter on the first line of the file.

> 

> This used to work under Windows 7 with NVDA - is anyone else having this

> issue?

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Friday, July 26, 2019 8:06 AM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda] Community notice: upcoming NVDA 2019.3 and community add-ons

 

Hi NVDA community,

I’m Joseph Lee, a volunteer code contributor for NVDA screen reader project and the chief investigator for Python 3 work. First, I would like to thank my colleagues at NV Access and beyond for achieving a milestone in Python 3 work: alpha snapshots (master branch in source code) being powered by Python 3.

To the matter at hand: NVDA 2019.3 (Threshold, scheduled for later this year) will feature backwards incompatible changes, including speech refactor and Python 3. Because of this, many community add-ons (including add-ons hosted on addons.nvda-project.org) will need to be modified to take advantage of these changes, especially when it comes to supporting Python 3. Because Python 2 to 3 transition is a huge undertaking, I expect add-ons community will take several weeks to months (or longer) to transition vast majority of add-ons to Python 3, and collaboration is a key to success in this endeavor.

The following is a set of steps members of the community should take:

 

For add-on authors:

1. Prepare your mindset for Python 3 by reading several porting guides. The official one can be found at https://docs.python.org/3/howto/pyporting.html. Another useful one (titled Conservative Python 3 Porting Guide) can be found at https://portingguide.readthedocs.io/en/latest/.
2. If you haven’t done so, please install Python 3.7 so you can experiment with differences between Python 2 and 3.
3. Once you are comfortable with Python 3, please test your add-on(s) with latest NVDA alpha snapshots, preferably with build 18195 or later. If you need to keep using current add-ons or need to compare Python 2 versus 3, please use a portable copy of NVDA to test your add-ons.
4. Make necessary changes. It is up to you in regards to supporting older NVDA releases or not; if yes, you must write code compatible with both Python 2 and 3, otherwise please use Python 3.
5. After testing your add-ons, please release a Python 3 version of your add-on(s) for testing. You can either use development channel or a separate package. As you do so, please send a notice to the NVDA community regarding your add-ons and their compatibility with upcoming NVDA release.
6. Please listen to feedback and make changes based on what users are saying.
7. I advise completing Python 3 transition work for add-ons by end of this year, or by 2019.3 RC if possible. Although it won’t be a while before beta comes out, targeting release candidate ensures changes can be made based on feedback from beta testers.
8. Keep listening to feedback after NvDA 2019.3 stable is released and make necessary changes if any.

 

For users:

1. If you are adventurous, please test alpha snapshots as a portable copy. I don’t advise using an install copy for now until your favorite add-ons are declared compatible.
2. Please send feedback to add-on authors if you find issues with add-ons. An announcement has been posted on community add-ons website detailing compatible add-ons, issues with incompatible add-ons, and contact information for authors. The announcement can be found at https://addons.nvda-project.org/addons/nvdapy3.en.html.
3. When authors announce add-on compatibility notices, please read those notices and take note of issues.

 

Frequently asked questions:

 

Q. Can I make an add-on “compatible” by editing the manifest file?

No. Although it’ll give you a sense of “assurance” that your add-on will be considered “compatible” by NVDA, you will need to obtain a version of an add-on compatible with Python 3, speech refactor, and other changes.

 

Q. I need to report issues with add-ons not found on community add-ons website.

For these (especially speech synthesizer add-ons), you must contact the authors listed under Add-ons Manager.

 

Q. I am using an add-on that is declared compatible, yet NVDA won’t load due to an error about configobj.

This is caused by manifest file encoding. Add-ons must now use UTF-8 (without BOM). Vocalizer (add-on 2.x) is affected by this bug and possibly others.

 

Q. When starting NVDA, I get a runtime error and it becomes silent.

The most likely cause is an add-on that uses a C extension (.pyd) module that won’t work properly on Python 3. Disabling the add-on will allow NVDA to proceed with startup. For add-ons affected by this, authors must now compile C extensions with Visual Studio 2017, the compiler used to compile Python 3.7.

 

Q. What about add-ons noted as end of life?

Please contact add-on authors about their plans to support Python 3. One such add-on is Control Usage Assistant, and I (Joseph Lee) will make an announcement about it very soon.

 

Thank you. And with that, let Python 3 porting begin!

Cheers,

Joseph

----- Original Message -----
From: "Jaffar Sidek" <jaffar.sidek10@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, July 25, 2019 11:58 PM
Subject: [nvda] NVDA, beyond screen reading

Hi all. All of us use NVDA extensively for those basic computer tasks like emailing, word processing, surfing the web and so on. But there are some of you I'm sure who would like to do more with your pcs, in company with NVDA. I'm sure that there are some among you, for example who would like to branch out, into something else you are really good at and make a decent living out of it. like making music? music production? or programming? and why not? NVDA has come a long way since it started way back years ago. No more is it a screen reader that plays second fiddle to the more established JFW. Window eyes has come and gone, unjustly consigned to the whims of Father Time. But with the undaunting efforts of the main developers and the community, NVDA is now a formidable tool that can be employed for more serious pursuits like Music production and Computer Programming. I want to concentrate however on music making because there are a lot of talented blind folks who would like to make music, perhaps as a hobby or as a form of livelihood but do not know how to go about it, and In particular, i want to sportlight Reaper, a most versatile Digital Audio Workstation (DAW), which also allows for MIDI recording..


You can get Reaper from its website,

http://reaper.fm/download.php

or download it here and install it as a fully functional trial,

https://www.dropbox.com/s/zpw1xyen2ynbeay/reaper5981_x64-install.exe?dl=1

Then download and install Osara, an NVDA extension which enhances NVDA's capability to almost fully access the Reaper application.

https://www.dropbox.com/s/zpw1xyen2ynbeay/reaper5981_x64-install.exe?dl=1

You have now got a computer which also acts as a music work station, allowing you to record and edit midi, as well as record and edit audio. How cool is that?

As a demo to put forward my point, here's a piece of music I wrote for a school's music educational program and was paid for it.

https://www.dropbox.com/s/0xcy5lhusgftiff/Kangaroo%20Playtime.mp3?dl=0

The music is not put here to show of my limited skill but rather to show you what you can do if you venture to use NVDA as broadly as you can and not limit it's limitless capabilities.

Now having turned your pc into a music work Station, Consult the Reaper wiki, at https://reaperaccessibility.com/index.php/Main_Page and go make music. You can also join the reaper mailing list for help and questions. The address is listed on the wiki.


This is part of a paper on Computer accessibility I was invited to present by our local I T government department to a group of blind and sighted university students a week ago. I only included the music part of the presentation here as many blind people want to make something out of their music talent but don't know how. Hope the moderators won't mind. Cheers!