On 9/21/18, Brooke Staley <bamills888@gmail.com> wrote:

Hi

We have been finding it stops intermittently and the only way to restart is
by restarting the computer. We are using newest version of nvda and excel
2016. We are finding it is happening more so with charts

Thanks

On 21 Sep 2018, at 2:50 pm, Quentin Christensen <quentin@nvaccess.org>
wrote:

Is it something you can reproduce? IE - open a particular file, navigate
to a chart, move to the second element in the chart, NVDA stops talking.
Or does it happen regularly (eg every 5 minutes) but not doing a specific
thing?

Does it happen with any Excel file or a particular one? Also which
version of Excel / Windows / NVDA are you using?

It could be any number of things, but if you have a specific file that
always exhibits the behaviour, and a copy of your NVDA log, if you email
them both to info@nvaccess.org with a description of how to reproduce the
issue, I can have a look and see if I can find anything.

Regards

Quentin.

On Fri, Sep 21, 2018 at 2:02 PM <bamills888@gmail.com> wrote:
Hi
We have been working within excel but every now and then NVDA will stop
talking and we don't know why? We are usually in the charting section. Is
there an easy fix we can put in or a shortcut we can use to get nvda
working again?

Thanks

B.

--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Friday, September 21, 2018 3:52 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] FW: [nvda-addons] Project Pylennium: updates, proposing
start of Python 3 pre-transition activities

Hi, I'd just like to clarify that no actual release of nvda powered by the
new compiler is going to occur until all code runs on windows 7sp1.
Also what is the attitude these days to a 64 bit version on nvda itself, as
I feel such a move may well impact on some of the current bottlenecks in
processor core usage and other issues.
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: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 1:46 AM
Subject: [nvda] FW: [nvda-addons] Project Pylennium: updates, proposing
start of Python 3 pre-transition activities

Hi everyone,

Although the below post is a bit technical, please keep an eye on it.
You won't feel the impact of what I outline regarding Python 3
transition for a while, but when it does, please listen to notices
from NV Access and add-on authors regarding Python 3. And no, wxPython
4 is not the same thing as Python 3.

Thanks.



From: nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io>
On Behalf Of Joseph Lee
Sent: Thursday, September 20, 2018 5:43 PM
To: 'NVDA screen reader development'
<nvda-devel@lists.sourceforge.net>
Subject: [nvda-addons] Project Pylennium: updates, proposing start of
Python
3 pre-transition activities



Dear NVDA development and add-ons communities:



This is Joseph Lee, a student at California State University, Los
Angeles and a long-time NVDA add-on author and code contributor. I'd
like to announce some important updates regarding Project Pylennium.



For a while, some NVDA developers (mostly third-party contributors)
have been working on how to bring Project Pylennium - Python 3
transition - to life. After much discussion, NV Access and other
developers agreed to wait until a stable NVDA version powered by
wxPython 4.0.3 (Phoenix) is released before working on this project.
Now that NVDA 2018.3.x (powered by wxPython
4) has been released, it is time to move forward with this project a
bit, starting with pre-transition activities.



To kick this off, I'm delighted to announce that a prototype archive
of NVDA source code and dependencies powered by Python 3 is now
available. Apart from removal of data generated by SCons, the archive
is ready to run on Python 3.7 with some preparations, and. are you
ready for it: IT RUNS!
Well,
I must add that there are some important features missing or not
working as intended, but I'm sure this will be rectified as the
project moves forward.



Note that the archive is a prototype - please do not test this unless
your intention is to provide contributions to Python 3 transition
workflow once NV Access is ready to accept pull requests.



Archive link:

https://www.josephsl.net/files/pylennium/nvdapy37.zip



Things working:



* Windows OneCore synthesizer
* Python Console
* Sending log output to log file
* Object navigation commands
* Commands to configure options (NVDA+number row 2, for instance)
* Loading app modules



Things to be aware of:



* Requires Windows 10 until Espeak NG is ready.
* NVDA menu won't open due to division operator differences between
Python 2 nad 3
* Add-ons won't load
* Certain synth settings ring commands won't work
* Some braille displays won't work



The idea is to let seasoned developers (preferably third-party
contributors and/or a group of mainstream Python developers) test
ideas and porting issues and report their findings to NV Access. In
turn, when it comes time to actually transition NVDA source code and
add-ons to Python 3, data can be used to guide future work.



Second, a wiki page is being written to help you all move smoothly to
Python
3 and to coordinate this workflow. The document is subject to change based
on progress of pre-transition activities. The page in its current form can
be found at:

https://github.com/nvaccess/nvda/wiki/nvdapy3



As always, the umbrella issue on Python 3 transition can be found on
GitHub
at:

https://github.com/nvaccess/nvda/issues/7105



Along with other issues having "python 3" label added to them.



Lastly, I'd like to announce that I'm stepping back from Python 3
transition
workflow at this time (and, for that matter, NVDA code contributions for a
while). Besides automatic braille display detection (written by Babbage
B.V.) and various Windows 10 features support (mostly my work), the
biggest
change (and the most controversial one) in NVDA 2018.3.x has been moving
to
wxPython 4 (mostly my work with assistance from many). The results matched
my predictions from earlier this year: some notable add-ons not being
compatible with wxPython 4, hence notices throughout this summer (winter
for
those living in southern hemisphere).



At the moment I have mixed feelings about how we (NvDA community) handled
this change. Yes, wxPython 4 is a necessary stepping stone for moving to
Python 3, and yes, I understand that I was rather forceful in handling
certain parts of this journey. There are good things we did, and lessons
we
have learned so we can make Python 3 transition a smoother experience.
Even
for me, it was an interesting ride for the last three years (wxPython
Phoenix research began in 2015), and I know that I could have done things
better.



Recently, I hinted to some that my time as an active contributor to NVDA
screen reader is slowly coming to a close. As a first step, I'd like to
ask
that the community take an initiative to move forward with Python 3
transition (including other pre-transition activities); I feel that the
best
thing I can do for this work now is to provide the prototype archive and a
vision for its conclusion, along with some pull requests (one of them is
pending review). There is a feature I'd like to present as a token of
appreciation to those who've helped me for the past six years: add-on
update
checks, which will be impacted by Python 3 transition as well. But this
does
not mean I'm leaving the community: I'll still be around to give advice
regarding Project Pylennium.



Thank you.

Cheers,

Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Friday, September 21, 2018 3:43 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] GoldWave and Resource Monitor 18.10 #AddonRelease

Hi I hope the surprise on goldwave is not that it won't work on 32 bit
installs, as I still use that as it seems less laggy.
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: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Thursday, September 20, 2018 11:34 PM
Subject: [nvda] GoldWave and Resource Monitor 18.10 #AddonRelease

Hi all,



In about half an hour from now, GoldWave and Resource Monitor add-on
version
18.10 will hit the air. GoldWave brings localization updates (and a
surprise
to be revealed later), and Resource Monitor will be more accurate when
dealing with large memory and storage capacity (also comes with a
surprise).



Note for folks using Windows 10 Insider Preview builds: some of you were
telling me that, in some cases, NVDA did not recognize Insider builds
correctly when you press NVDA+Shift+number row 6. This has been corrected
with Resource Monitor 18.10.



As always, you can visit the community add-ons website to download these
updates when they become available, or use Add-on Updater to check for
updates.



As for the surprise I'm talking about: more on that very soon.

Cheers,

Joseph

----- Original Message -----
From: "Ian Westerland" <iwesterl@bigpond.net.au>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 6:20 AM
Subject: [nvda] Webb Browsers

Hello. The latest version of NVDA is working really well and I'd say, better than ever for my uses. So, thanks to everyone involved for your efforts.

I do a lot of online shopping on sites ranging from Coals and Woolworths Supermarkets to clothing shops and occasionally Ebay. Do others have the same issue as me with webb sites working better with a variety of Browsers? This morning I started by using Chrome on the Just Jeans site but couldn't find the Payment button. I changed to FireFox, then to WaterFox and still couldn't find the Pay button. Good old IE turned out to be the only one I had that gave me access to that button.

When I am really up against the technology, good old Window-Eyes has been known to be the solution but this is rare these days.

Any comments?

Thank you.


Ian Westerland

----- Original Message -----
From: <bamills888@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 5:00 AM
Subject: [nvda] WORKING WITHIN EXCEL


Hi
We have been working within excel but every now and then NVDA will stop talking and we don't know why? We are usually in the charting section. Is there an easy fix we can put in or a shortcut we can use to get nvda working again?

Thanks

B.

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 1:46 AM
Subject: [nvda] FW: [nvda-addons] Project Pylennium: updates, proposing start of Python 3 pre-transition activities

Hi everyone,

Although the below post is a bit technical, please keep an eye on it. You
won't feel the impact of what I outline regarding Python 3 transition for a
while, but when it does, please listen to notices from NV Access and add-on
authors regarding Python 3. And no, wxPython 4 is not the same thing as
Python 3.

Thanks.



From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Joseph Lee
Sent: Thursday, September 20, 2018 5:43 PM
To: 'NVDA screen reader development' <nvda-devel@lists.sourceforge.net>
Subject: [nvda-addons] Project Pylennium: updates, proposing start of Python
3 pre-transition activities



Dear NVDA development and add-ons communities:



This is Joseph Lee, a student at California State University, Los Angeles
and a long-time NVDA add-on author and code contributor. I'd like to
announce some important updates regarding Project Pylennium.



For a while, some NVDA developers (mostly third-party contributors) have
been working on how to bring Project Pylennium - Python 3 transition - to
life. After much discussion, NV Access and other developers agreed to wait
until a stable NVDA version powered by wxPython 4.0.3 (Phoenix) is released
before working on this project. Now that NVDA 2018.3.x (powered by wxPython
4) has been released, it is time to move forward with this project a bit,
starting with pre-transition activities.



To kick this off, I'm delighted to announce that a prototype archive of NVDA
source code and dependencies powered by Python 3 is now available. Apart
from removal of data generated by SCons, the archive is ready to run on
Python 3.7 with some preparations, and. are you ready for it: IT RUNS! Well,
I must add that there are some important features missing or not working as
intended, but I'm sure this will be rectified as the project moves forward.



Note that the archive is a prototype - please do not test this unless your
intention is to provide contributions to Python 3 transition workflow once
NV Access is ready to accept pull requests.



Archive link:

https://www.josephsl.net/files/pylennium/nvdapy37.zip



Things working:



* Windows OneCore synthesizer
* Python Console
* Sending log output to log file
* Object navigation commands
* Commands to configure options (NVDA+number row 2, for instance)
* Loading app modules



Things to be aware of:



* Requires Windows 10 until Espeak NG is ready.
* NVDA menu won't open due to division operator differences between
Python 2 nad 3
* Add-ons won't load
* Certain synth settings ring commands won't work
* Some braille displays won't work



The idea is to let seasoned developers (preferably third-party contributors
and/or a group of mainstream Python developers) test ideas and porting
issues and report their findings to NV Access. In turn, when it comes time
to actually transition NVDA source code and add-ons to Python 3, data can be
used to guide future work.



Second, a wiki page is being written to help you all move smoothly to Python
3 and to coordinate this workflow. The document is subject to change based
on progress of pre-transition activities. The page in its current form can
be found at:

https://github.com/nvaccess/nvda/wiki/nvdapy3



As always, the umbrella issue on Python 3 transition can be found on GitHub
at:

https://github.com/nvaccess/nvda/issues/7105



Along with other issues having "python 3" label added to them.



Lastly, I'd like to announce that I'm stepping back from Python 3 transition
workflow at this time (and, for that matter, NVDA code contributions for a
while). Besides automatic braille display detection (written by Babbage
B.V.) and various Windows 10 features support (mostly my work), the biggest
change (and the most controversial one) in NVDA 2018.3.x has been moving to
wxPython 4 (mostly my work with assistance from many). The results matched
my predictions from earlier this year: some notable add-ons not being
compatible with wxPython 4, hence notices throughout this summer (winter for
those living in southern hemisphere).



At the moment I have mixed feelings about how we (NvDA community) handled
this change. Yes, wxPython 4 is a necessary stepping stone for moving to
Python 3, and yes, I understand that I was rather forceful in handling
certain parts of this journey. There are good things we did, and lessons we
have learned so we can make Python 3 transition a smoother experience. Even
for me, it was an interesting ride for the last three years (wxPython
Phoenix research began in 2015), and I know that I could have done things
better.



Recently, I hinted to some that my time as an active contributor to NVDA
screen reader is slowly coming to a close. As a first step, I'd like to ask
that the community take an initiative to move forward with Python 3
transition (including other pre-transition activities); I feel that the best
thing I can do for this work now is to provide the prototype archive and a
vision for its conclusion, along with some pull requests (one of them is
pending review). There is a feature I'd like to present as a token of
appreciation to those who've helped me for the past six years: add-on update
checks, which will be impacted by Python 3 transition as well. But this does
not mean I'm leaving the community: I'll still be around to give advice
regarding Project Pylennium.



Thank you.

Cheers,

Joseph

----- Original Message -----
From: "Gene" <gsasner@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 1:49 AM
Subject: Re: [nvda] mouse cursor and NVDA cursor problems.


Some programs don't track properly in terms of where the mouse should be when you move it. Others who may know more may have suggestions. I imagine the sighted person is asking you about focus because they are trying to learn what you are doing. Isn't there a way that a sighted user can see what a blind person is doing in terms of their position on screen? Not where the mouse is, but where they are working. If that is correct, could that feature be used instead of the unreliable mouse tracking that evidently exists in the program?

Gene
----- Original Message -----

From: aikeo koomanivong
Sent: Thursday, September 20, 2018 7:41 PM
To: nvda
Subject: [nvda] mouse cursor and NVDA cursor problems.


Dear all
I’m using NVDA for training Daisy book making with Obie software
While training, sighted person always asking me for where’s the mouse
cursor focus but NVDA speaking correctly.
I’m trying to Move mouse to current navigator object by pressing
NVDA+shift+m [laptop layout]
but not really working
Looking for your comments.
regards


--
AIKEO KOOMANIVONG
CFBT-ICEVI coordinator of LAO PDR.
vise president
accessible ICT and musical development for the blind

Vocational development for LAO-blind association [VDBA]
Office e-mail: vdba.lao@gmail.com
Facebook page:
www.facebook.com/laoblind.org
my personal e-mail: mlp_keo@yahoo.com
skype name: peba_007
mobile phone: +8562099993423
Facebook:
www.facebook.com/keo.laoblind
Linkedin:
https://www.linkedin.com/pub/aikeo-koomanivong/a7/156/b8b

----- Original Message -----
From: "aikeo koomanivong" <moykoomanivong@gmail.com>
To: "nvda" <nvda@groups.io>
Sent: Friday, September 21, 2018 1:41 AM
Subject: [nvda] mouse cursor and NVDA cursor problems.


Dear all
I’m using NVDA for training Daisy book making with Obie software
While training, sighted person always asking me for where’s the mouse
cursor focus but NVDA speaking correctly.
I’m trying to Move mouse to current navigator object by pressing
NVDA+shift+m [laptop layout]
but not really working
Looking for your comments.
regards


--
AIKEO KOOMANIVONG
CFBT-ICEVI coordinator of LAO PDR.
vise president
accessible ICT and musical development for the blind

Vocational development for LAO-blind association [VDBA]
Office e-mail: vdba.lao@gmail.com
Facebook page:
www.facebook.com/laoblind.org
my personal e-mail: mlp_keo@yahoo.com
skype name: peba_007
mobile phone: +8562099993423
Facebook:
www.facebook.com/keo.laoblind
Linkedin:
https://www.linkedin.com/pub/aikeo-koomanivong/a7/156/b8b

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Thursday, September 20, 2018 11:34 PM
Subject: [nvda] GoldWave and Resource Monitor 18.10 #AddonRelease

Hi all,



In about half an hour from now, GoldWave and Resource Monitor add-on version
18.10 will hit the air. GoldWave brings localization updates (and a surprise
to be revealed later), and Resource Monitor will be more accurate when
dealing with large memory and storage capacity (also comes with a surprise).



Note for folks using Windows 10 Insider Preview builds: some of you were
telling me that, in some cases, NVDA did not recognize Insider builds
correctly when you press NVDA+Shift+number row 6. This has been corrected
with Resource Monitor 18.10.



As always, you can visit the community add-ons website to download these
updates when they become available, or use Add-on Updater to check for
updates.



As for the surprise I'm talking about: more on that very soon.

Cheers,

Joseph

On 21 Sep 2018, at 2:50 pm, Quentin Christensen <quentin@...> wrote:

Is it something you can reproduce?  IE - open a particular file, navigate to a chart, move to the second element in the chart, NVDA stops talking.  Or does it happen regularly (eg every 5 minutes) but not doing a specific thing?

Does it happen with any Excel file or a particular one?  Also which version of Excel / Windows / NVDA are you using?

It could be any number of things, but if you have a specific file that always exhibits the behaviour, and a copy of your NVDA log, if you email them both to info@... with a description of how to reproduce the issue, I can have a look and see if I can find anything.

Regards

Quentin.

On Fri, Sep 21, 2018 at 2:02 PM <bamills888@...> wrote:

Hi
We have been working within excel but every now and then NVDA will stop talking and we don't know why? We are usually in the charting section. Is there an easy fix we can put in or a shortcut we can use to get nvda working again?

Thanks

B.

--

Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

www.nvaccess.org 

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 

On 21 Sep 2018, at 2:50 pm, Quentin Christensen <quentin@...> wrote:

Is it something you can reproduce?  IE - open a particular file, navigate to a chart, move to the second element in the chart, NVDA stops talking.  Or does it happen regularly (eg every 5 minutes) but not doing a specific thing?

Does it happen with any Excel file or a particular one?  Also which version of Excel / Windows / NVDA are you using?

It could be any number of things, but if you have a specific file that always exhibits the behaviour, and a copy of your NVDA log, if you email them both to info@... with a description of how to reproduce the issue, I can have a look and see if I can find anything.

Regards

Quentin.

On Fri, Sep 21, 2018 at 2:02 PM <bamills888@...> wrote:

Hi
We have been working within excel but every now and then NVDA will stop talking and we don't know why? We are usually in the charting section. Is there an easy fix we can put in or a shortcut we can use to get nvda working again?

Thanks

B.

--

Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

www.nvaccess.org 

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess