Date   

Re: StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #addonrelease

 

Hi,

Already fixed in 18.10 from the add-on side. A more general fix is on its way (it’ll show up tonight).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Inam Uddin via Groups.Io
Sent: Friday, September 21, 2018 5:33 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #AddonRelease

 

Respected Joseph, other than God nobody is perfect but the question is that when and how you will fix it?

With regards from Inamuddin with the Skype ID:

Charlsdarwin1

 

 

It is nice to be important but it is more important to be nice!

You can contact me via gmail:

Inamuddin09@...

Outlook:

Inam092@...

Yahoo:

Inamuddin2010@...

AOL:

Charlsdarwin1969@...

Talk with me on Skype:

Charlsdarwin1

Follow me on my twitter ID:

www.twitter.com/charlsdarwin1

Call me on my cell no.:

+92-334-3348409                                             

 

 

From: Joseph Lee
Sent: Saturday, September 22, 2018 4:51 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #AddonRelease

 

Hi,

This was my fault, and unfortunately, a manual download should be attempted (from add-ons website, sorry about that).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Inam Uddin via Groups.Io
Sent: Friday, September 21, 2018 4:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #AddonRelease

 

Dear Joseph, the matter of fact is that the latest windows 10 app essential is 18.10 and I have 18.09.1 when I go to check for update, it is giving me your development update which is 20 million or so why not 18.10?

With regards from Inamuddin with the Skype ID:

Charlsdarwin1

 

 

It is nice to be important but it is more important to be nice!

You can contact me via gmail:

Inamuddin09@...

Outlook:

Inam092@...

Yahoo:

Inamuddin2010@...

AOL:

Charlsdarwin1969@...

Talk with me on Skype:

Charlsdarwin1

Follow me on my twitter ID:

www.twitter.com/charlsdarwin1

Call me on my cell no.:

+92-334-3348409                                             

 

 

From: Joseph Lee
Sent: Friday, September 21, 2018 11:15 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda] StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #AddonRelease

 

Hi all,

 

Shortly after release of SPL add-on 18.10, a broadcaster reported an issue where Studio won’t play the first track after an encoder was connected to a streaming server. After some investigation, the problem was traced to wxPython 4 (NVDA 2018.3.x) where text output would fail under some circumstances (specifically, wxPython 4 is more strict about where timers can be invoked from).

 

Because this affects everyone (except for people using really old builds) who are using NVDA 2018.3.x, I’m going to release version 18.10.1 and 18.09.3-LTS for those on stable and longterm channels, respectively. For those using development snapshots, revision A of September 21st build will also be released.

 

Thanks.

Cheers,

Joseph

 

 


Re: problems starting nvda with windows 1809 as an insider

Gene
 

There is a check box or some sort of control on the page that says something like not this time.  No one is forced to donate.  If they were, they wouldn't be donations. 
 
Gene

----- Original Message -----
Sent: Friday, September 21, 2018 5:55 PM
Subject: Re: [nvda] problems starting nvda with windows 1809 as an insider

Good Afternoon:  I'm not concerned about Adobe Reader at this time.  I'm more concerned about getting NVDA back to running.  I'm running the tool to hopefully return the NVDA program on this machine.  If not, how can you download a new version of NVDA without giving a donation at this time?  I'm retired, so, don't have a lot of extra cash to give right now.

Dave



On 9/21/2018 3:10 PM, Gene wrote:
I'm not sure what the problem is nor if the two problems are related or completely separate.  You can undo a restore operation.  You may want to do that.  If you don't know how, tell us the version of Windows you are running and someone will probably tell you. 
 
Then, you may be able to do whatever you want regarding NVDA, if you still need to, but undoing the restore will probably allow it to work again. 
 
As far as Adobe is concerned, before you do anything else, let us know what happens when you try to run it.  Is there an error message?  Does nothing happen?  There are logs in Windows that may give information on what the problem is or may be.
 
Gene
----- Origfinal Message -----
Sent: Friday, September 21, 2018 3:54 PM
Subject: [nvda] problems starting nvda with windows 1809 as an insider

This morning Adobe Reader wasn't working, so, I decided to run a restore
on my computer.  It's running win1809 64 bit version. After the restore
was completed I just received a jingle when the machine starts up.  It
doesn't make any difference if alt+y for the uac is pressed or not.  I
was going to uninstall nvda, but I can't get past the area to give a
donation in the web site.  It doesn't make any difference whether admin
is used from the shortcut in my desktop.  I have also tried using the
option to run with Jaws.  I've also tried to refresh it or go back to
the previous version and also tried problem solving it but nothing seems
to let me in.  Thank in advance for help here.

Dave






Re: StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #addonrelease

Inam Uddin
 

Respected Joseph, other than God nobody is perfect but the question is that when and how you will fix it?

With regards from Inamuddin with the Skype ID:

Charlsdarwin1

 

 

It is nice to be important but it is more important to be nice!

You can contact me via gmail:

Inamuddin09@...

Outlook:

Inam092@...

Yahoo:

Inamuddin2010@...

AOL:

Charlsdarwin1969@...

Talk with me on Skype:

Charlsdarwin1

Follow me on my twitter ID:

www.twitter.com/charlsdarwin1

Call me on my cell no.:

+92-334-3348409                                             

 

 

From: Joseph Lee
Sent: Saturday, September 22, 2018 4:51 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #AddonRelease

 

Hi,

This was my fault, and unfortunately, a manual download should be attempted (from add-ons website, sorry about that).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Inam Uddin via Groups.Io
Sent: Friday, September 21, 2018 4:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #AddonRelease

 

Dear Joseph, the matter of fact is that the latest windows 10 app essential is 18.10 and I have 18.09.1 when I go to check for update, it is giving me your development update which is 20 million or so why not 18.10?

With regards from Inamuddin with the Skype ID:

Charlsdarwin1

 

 

It is nice to be important but it is more important to be nice!

You can contact me via gmail:

Inamuddin09@...

Outlook:

Inam092@...

Yahoo:

Inamuddin2010@...

AOL:

Charlsdarwin1969@...

Talk with me on Skype:

Charlsdarwin1

Follow me on my twitter ID:

www.twitter.com/charlsdarwin1

Call me on my cell no.:

+92-334-3348409                                             

 

 

From: Joseph Lee
Sent: Friday, September 21, 2018 11:15 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda] StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #AddonRelease

 

Hi all,

 

Shortly after release of SPL add-on 18.10, a broadcaster reported an issue where Studio won’t play the first track after an encoder was connected to a streaming server. After some investigation, the problem was traced to wxPython 4 (NVDA 2018.3.x) where text output would fail under some circumstances (specifically, wxPython 4 is more strict about where timers can be invoked from).

 

Because this affects everyone (except for people using really old builds) who are using NVDA 2018.3.x, I’m going to release version 18.10.1 and 18.09.3-LTS for those on stable and longterm channels, respectively. For those using development snapshots, revision A of September 21st build will also be released.

 

Thanks.

Cheers,

Joseph

 

 


Re: StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #addonrelease

 

Hi,

This was my fault, and unfortunately, a manual download should be attempted (from add-ons website, sorry about that).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Inam Uddin via Groups.Io
Sent: Friday, September 21, 2018 4:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #AddonRelease

 

Dear Joseph, the matter of fact is that the latest windows 10 app essential is 18.10 and I have 18.09.1 when I go to check for update, it is giving me your development update which is 20 million or so why not 18.10?

With regards from Inamuddin with the Skype ID:

Charlsdarwin1

 

 

It is nice to be important but it is more important to be nice!

You can contact me via gmail:

Inamuddin09@...

Outlook:

Inam092@...

Yahoo:

Inamuddin2010@...

AOL:

Charlsdarwin1969@...

Talk with me on Skype:

Charlsdarwin1

Follow me on my twitter ID:

www.twitter.com/charlsdarwin1

Call me on my cell no.:

+92-334-3348409                                             

 

 

From: Joseph Lee
Sent: Friday, September 21, 2018 11:15 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda] StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #AddonRelease

 

Hi all,

 

Shortly after release of SPL add-on 18.10, a broadcaster reported an issue where Studio won’t play the first track after an encoder was connected to a streaming server. After some investigation, the problem was traced to wxPython 4 (NVDA 2018.3.x) where text output would fail under some circumstances (specifically, wxPython 4 is more strict about where timers can be invoked from).

 

Because this affects everyone (except for people using really old builds) who are using NVDA 2018.3.x, I’m going to release version 18.10.1 and 18.09.3-LTS for those on stable and longterm channels, respectively. For those using development snapshots, revision A of September 21st build will also be released.

 

Thanks.

Cheers,

Joseph

 


Re: FW: [nvda-addons] Project Pylennium: updates, proposing start of Python 3 pre-transition activities

 

To be honest I agree, moving from 32bit win7 to 64 bit win7 has given me a bit more power out of this aging system.

On win10, after a full reformat, I have ben running the same configuration on this gen 4 and its been fine for what it is.

I do run 64 bit where ever I can 32 is fine to, the office on the workstation is 32 bit, and I have not bothered moving to 64 bit but I have been wandering.

On 9/21/2018 10:52 PM, Brian's Mail list account via Groups.Io wrote:
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








.


Re: StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #addonrelease

Inam Uddin
 

Dear Joseph, the matter of fact is that the latest windows 10 app essential is 18.10 and I have 18.09.1 when I go to check for update, it is giving me your development update which is 20 million or so why not 18.10?

With regards from Inamuddin with the Skype ID:

Charlsdarwin1

 

 

It is nice to be important but it is more important to be nice!

You can contact me via gmail:

Inamuddin09@...

Outlook:

Inam092@...

Yahoo:

Inamuddin2010@...

AOL:

Charlsdarwin1969@...

Talk with me on Skype:

Charlsdarwin1

Follow me on my twitter ID:

www.twitter.com/charlsdarwin1

Call me on my cell no.:

+92-334-3348409                                             

 

 

From: Joseph Lee
Sent: Friday, September 21, 2018 11:15 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda] StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #AddonRelease

 

Hi all,

 

Shortly after release of SPL add-on 18.10, a broadcaster reported an issue where Studio won’t play the first track after an encoder was connected to a streaming server. After some investigation, the problem was traced to wxPython 4 (NVDA 2018.3.x) where text output would fail under some circumstances (specifically, wxPython 4 is more strict about where timers can be invoked from).

 

Because this affects everyone (except for people using really old builds) who are using NVDA 2018.3.x, I’m going to release version 18.10.1 and 18.09.3-LTS for those on stable and longterm channels, respectively. For those using development snapshots, revision A of September 21st build will also be released.

 

Thanks.

Cheers,

Joseph

 


Re: problems starting nvda with windows 1809 as an insider

ely.r@...
 

Dave,

It is not necessary to donate. It is a request only. NVDA is free to all who need it. Donate when you can.  The bottom of the NVDA menu has a button titled Donate. Very convenient when there is cash to do it.

Luck

Rick

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dave Grossoehme
Sent: Friday, September 21, 2018 6:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] problems starting nvda with windows 1809 as an insider

 

Good Afternoon:  I'm not concerned about Adobe Reader at this time.  I'm more concerned about getting NVDA back to running.  I'm running the tool to hopefully return the NVDA program on this machine.  If not, how can you download a new version of NVDA without giving a donation at this time?  I'm retired, so, don't have a lot of extra cash to give right now.

Dave

 

 

On 9/21/2018 3:10 PM, Gene wrote:

I'm not sure what the problem is nor if the two problems are related or completely separate.  You can undo a restore operation.  You may want to do that.  If you don't know how, tell us the version of Windows you are running and someone will probably tell you. 

 

Then, you may be able to do whatever you want regarding NVDA, if you still need to, but undoing the restore will probably allow it to work again. 

 

As far as Adobe is concerned, before you do anything else, let us know what happens when you try to run it.  Is there an error message?  Does nothing happen?  There are logs in Windows that may give information on what the problem is or may be.

 

Gene

----- Origfinal Message -----

Sent: Friday, September 21, 2018 3:54 PM

Subject: [nvda] problems starting nvda with windows 1809 as an insider

 

This morning Adobe Reader wasn't working, so, I decided to run a restore
on my computer.  It's running win1809 64 bit version. After the restore
was completed I just received a jingle when the machine starts up.  It
doesn't make any difference if alt+y for the uac is pressed or not.  I
was going to uninstall nvda, but I can't get past the area to give a
donation in the web site.  It doesn't make any difference whether admin
is used from the shortcut in my desktop.  I have also tried using the
option to run with Jaws.  I've also tried to refresh it or go back to
the previous version and also tried problem solving it but nothing seems
to let me in.  Thank in advance for help here.

Dave



 


Re: problems starting nvda with windows 1809 as an insider

Dave Grossoehme
 

Good Afternoon again:  I forgot to answer your question.  The version of windows is the fall addition which is 1809 build 17763.1.

Dave



On 9/21/2018 3:10 PM, Gene wrote:
I'm not sure what the problem is nor if the two problems are related or completely separate.  You can undo a restore operation.  You may want to do that.  If you don't know how, tell us the version of Windows you are running and someone will probably tell you. 
 
Then, you may be able to do whatever you want regarding NVDA, if you still need to, but undoing the restore will probably allow it to work again. 
 
As far as Adobe is concerned, before you do anything else, let us know what happens when you try to run it.  Is there an error message?  Does nothing happen?  There are logs in Windows that may give information on what the problem is or may be.
 
Gene
----- Origfinal Message -----
Sent: Friday, September 21, 2018 3:54 PM
Subject: [nvda] problems starting nvda with windows 1809 as an insider

This morning Adobe Reader wasn't working, so, I decided to run a restore
on my computer.  It's running win1809 64 bit version. After the restore
was completed I just received a jingle when the machine starts up.  It
doesn't make any difference if alt+y for the uac is pressed or not.  I
was going to uninstall nvda, but I can't get past the area to give a
donation in the web site.  It doesn't make any difference whether admin
is used from the shortcut in my desktop.  I have also tried using the
option to run with Jaws.  I've also tried to refresh it or go back to
the previous version and also tried problem solving it but nothing seems
to let me in.  Thank in advance for help here.

Dave






Re: problems starting nvda with windows 1809 as an insider

Dave Grossoehme
 

Good Afternoon:  I'm not concerned about Adobe Reader at this time.  I'm more concerned about getting NVDA back to running.  I'm running the tool to hopefully return the NVDA program on this machine.  If not, how can you download a new version of NVDA without giving a donation at this time?  I'm retired, so, don't have a lot of extra cash to give right now.

Dave



On 9/21/2018 3:10 PM, Gene wrote:
I'm not sure what the problem is nor if the two problems are related or completely separate.  You can undo a restore operation.  You may want to do that.  If you don't know how, tell us the version of Windows you are running and someone will probably tell you. 
 
Then, you may be able to do whatever you want regarding NVDA, if you still need to, but undoing the restore will probably allow it to work again. 
 
As far as Adobe is concerned, before you do anything else, let us know what happens when you try to run it.  Is there an error message?  Does nothing happen?  There are logs in Windows that may give information on what the problem is or may be.
 
Gene
----- Origfinal Message -----
Sent: Friday, September 21, 2018 3:54 PM
Subject: [nvda] problems starting nvda with windows 1809 as an insider

This morning Adobe Reader wasn't working, so, I decided to run a restore
on my computer.  It's running win1809 64 bit version. After the restore
was completed I just received a jingle when the machine starts up.  It
doesn't make any difference if alt+y for the uac is pressed or not.  I
was going to uninstall nvda, but I can't get past the area to give a
donation in the web site.  It doesn't make any difference whether admin
is used from the shortcut in my desktop.  I have also tried using the
option to run with Jaws.  I've also tried to refresh it or go back to
the previous version and also tried problem solving it but nothing seems
to let me in.  Thank in advance for help here.

Dave






Re: Web Browsers

Gene
 

There is another aspect to the problem I hadn't considered in my first message.  More sites now are using embedded programs.  I'm not sure how that fits into the discussion.  The use of dialogs, while not an embedded program,  is an example of a new interface that has been added to some web pages over the last few years.  When you open a dialog in a site, my experience, others may wish to comment, is that at times, I need to turn browse mode off to work with it.  I haven't seen many but they seem inconsistent from my recollection about whether this is necessary and I have seen some where you can have the controls read  and not the explanatory text in the dialog and some as I recall, I can cause everything to be read.  Sometimes, I can close a dialog with escape, sometimes only with the close button.
 
As far as embedded programs are concerned, I don't know how JAWS compares with NVDA as to their accessibility.
 
Having said all that, what I said initially is important.  Proper Internet training would teach what I described in my first message.
 
Gene

----- Original Message -----
From: Gene
Sent: Friday, September 21, 2018 2:35 PM
Subject: Re: [nvda] Web Browsers

Which is why, instead of expecting sighted site designers to change the layout of their sites, blind people should know what such "helpful" comments tell them.  The shape obviously doesn't matter.  But if something is on the left side of a site, such as the navigation links are, screen-readers place them at the top of the screen.  Then comes the main content, which is below the navigation links and which is in the center of the screen for sighted users, the center from left to right, it may be anywhere from top to bottom for a sighted user, then on the right, there is often a number of links which blind people see at the bottom of the screen.  So when a sighted person tells you that something is on the right middle of the screen, that means that, for a blind person, it will be near the bottom of the screen. 
 
A lot of blind people get poor instruction on how to use the Internet. 
 
Gene
----- Original Message -----
Sent: Friday, September 21, 2018 9:52 AM
Subject: Re: [nvda] Web Browsers

The one thing that Jawes can afford to do is to make significant financial
clout to making a script work for a piece of software where the writers for
whatever reason are not prepared to make it obey conventions. Sadly this
same lack of expertise is now afflicting web sites again where accessibility
seems to men yes things should work but the clutter and complication factor
is far too high when you think about us blind folk not being able to get an
overview and general layout of a site. Helpful comments like the broken
green circle at the top left of the page are not welcome!
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Dave" <dlh007@...>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 1:52 PM
Subject: Re: [nvda] Web Browsers


> Hello Ian,
>
> Yes, I too noticed a Snappier behavior from this latest version of NVDA.
>
> I was using FireFox.
>
> As for the various Browsers being able to read all buttons, or Links, or
> different aspects on a Web Site-  Yes, I too have noticed this.
>
> I have been looking for work lately, and when on www.monster.com, a
> Employment Web Site, Sometimes I can read the Needed Links, and then
> other times, those links are not seen.
>
> Or once I've used them once, even if I return to the Main page of the
> web site, for what ever reason, I cannot find or read these links.  Have
> to shut down my Browser, and then re-visit the same site, and then those
> links will show up, but only sometimes.  Go Figure!
>
> And as far as differences between Screen Readers, Yes there too, I have
> noticed that one will read something better than the others.  I am a
> long time Window eyes user, who moved over to Jaws, and have had NVEA as
> the Screen Reader I call up to bail me out of Trouble when the others
> stop speaking.
>
> Over the last five years or so, I have actually found NVDA to be getting
> stronger and stronger.    In fact, when I needed to switch over to JAWS,
> at that time, I almost just switched to NVDA.  I have one program that
> NVDA will not read the screens, and Jaws does, so have been using Jaws.
>
> But, like I said, NVDA has come a long way, and is actually a very good
> Screen Reader.
>
>
>
> Dave
>
>
>
>
>




Re: problems starting nvda with windows 1809 as an insider

Gene
 

I'm not sure what the problem is nor if the two problems are related or completely separate.  You can undo a restore operation.  You may want to do that.  If you don't know how, tell us the version of Windows you are running and someone will probably tell you. 
 
Then, you may be able to do whatever you want regarding NVDA, if you still need to, but undoing the restore will probably allow it to work again. 
 
As far as Adobe is concerned, before you do anything else, let us know what happens when you try to run it.  Is there an error message?  Does nothing happen?  There are logs in Windows that may give information on what the problem is or may be.
 
Gene
----- Origfinal Message -----

Sent: Friday, September 21, 2018 3:54 PM
Subject: [nvda] problems starting nvda with windows 1809 as an insider

This morning Adobe Reader wasn't working, so, I decided to run a restore
on my computer.  It's running win1809 64 bit version. After the restore
was completed I just received a jingle when the machine starts up.  It
doesn't make any difference if alt+y for the uac is pressed or not.  I
was going to uninstall nvda, but I can't get past the area to give a
donation in the web site.  It doesn't make any difference whether admin
is used from the shortcut in my desktop.  I have also tried using the
option to run with Jaws.  I've also tried to refresh it or go back to
the previous version and also tried problem solving it but nothing seems
to let me in.  Thank in advance for help here.

Dave





Re: FW: [nvda-addons] Project Pylennium: updates, proposing start of Python 3 pre-transition activities

Ryan Mann
 

Wouldn’t that mean that machines running a 32-bit version of Windows would no longer be able to run NVDA. That would not be good since some of the computers at the organization I work for are running 32-bit versions of Windows. Therefore, I would no longer be able to use those machines to demonstrate NVDA.

On Sep 21, 2018, at 6:52 AM, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:

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







problems starting nvda with windows 1809 as an insider

Dave Grossoehme
 

This morning Adobe Reader wasn't working, so, I decided to run a restore on my computer.  It's running win1809 64 bit version. After the restore was completed I just received a jingle when the machine starts up.  It doesn't make any difference if alt+y for the uac is pressed or not.  I was going to uninstall nvda, but I can't get past the area to give a donation in the web site.  It doesn't make any difference whether admin is used from the shortcut in my desktop.  I have also tried using the option to run with Jaws.  I've also tried to refresh it or go back to the previous version and also tried problem solving it but nothing seems to let me in.  Thank in advance for help here.

Dave


Re: Web Browsers

Dave <dlh007@...>
 

Hello Brian,

I would like to believe that more programmers today, at least know of the
need for writing Software with Screen Readers in mind, but I have my
doubts.

There is such a Flood of new Software, and then there are the countless
Updates for everything currently available.

With the urgent push to get new and updated software out the door,
giving the attention needed to add Screen Reader support just seems more
of a Dream, than something likely to be done.


Even though it seems like I have greater accessibility today, I can't
help but sense that we've actually less total access than in years past.

What good is a Web Site, when you can read 90 percent of it, but can't
read the Check Out function?

Or find the Button that lets the Shopper move to the next 25 listings
etc.


I know there is the ADA that is a set of laws that are to require many
things be done to ease the access to many things, from Buildings to
Software, but so many things slip through without any kind of
consideration for those in need of the alterations. Unless the laws are enforced, then what good is the law?

I was just mentioning to a friend the other day, that I am sure telling
a lie is against the law. And yet our Politicians and Media
personalities lie to us all the time.


So is the Set of Laws known as the ADA, doing us that much good?


Dave


Re: edge and web shortcuts

Gary Metzler
 

Hi Brian,

My default browser is edge.

-----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 4:16 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] edge and web shortcuts

What is the default browser set as?

It sounds a bit like a windows issue. I've seen something similar in
windows 7 if a browser is launched with different syntax for the page you
wanted to go to so to speak.

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: "Gary Metzler" <gmtravel@comcast.net>
To: "nvda" <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 9:06 PM
Subject: [nvda] edge and web shortcuts


Hi All,



I am using the latest win10 and nvda. Whenever I start my facebook
shortcut
and it loads I get the message invalid entry. But, when I do this within
edge it doesn't happen. It only happens with edge and desktop shortcuts.
Has anyone else noticed this? Can this be fixed? Thanks for any help.



Regards, Gary KN4Ox

Send to: gmtravel@comcast.net







Re: edge and web shortcuts

Brian's Mail list account <bglists@...>
 

What is the default browser set as?

It sounds a bit like a windows issue. I've seen something similar in windows 7 if a browser is launched with different syntax for the page you wanted to go to so to speak.

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: "Gary Metzler" <gmtravel@comcast.net>
To: "nvda" <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 9:06 PM
Subject: [nvda] edge and web shortcuts


Hi All,



I am using the latest win10 and nvda. Whenever I start my facebook shortcut
and it loads I get the message invalid entry. But, when I do this within
edge it doesn't happen. It only happens with edge and desktop shortcuts.
Has anyone else noticed this? Can this be fixed? Thanks for any help.



Regards, Gary KN4Ox

Send to: gmtravel@comcast.net






edge and web shortcuts

Gary Metzler
 

Hi All,

 

I am using the latest win10 and nvda.  Whenever I start my facebook shortcut and it loads I get the message invalid entry.  But, when I do this within edge it doesn’t happen.  It only happens with edge and desktop shortcuts. Has anyone else noticed this?  Can this be fixed?  Thanks for any help.  

 

Regards, Gary KN4Ox

Send to: gmtravel@...

 


Re: Web Browsers

Gene
 

Which is why, instead of expecting sighted site designers to change the layout of their sites, blind people should know what such "helpful" comments tell them.  The shape obviously doesn't matter.  But if something is on the left side of a site, such as the navigation links are, screen-readers place them at the top of the screen.  Then comes the main content, which is below the navigation links and which is in the center of the screen for sighted users, the center from left to right, it may be anywhere from top to bottom for a sighted user, then on the right, there is often a number of links which blind people see at the bottom of the screen.  So when a sighted person tells you that something is on the right middle of the screen, that means that, for a blind person, it will be near the bottom of the screen. 
 
A lot of blind people get poor instruction on how to use the Internet. 
 
Gene

----- Original Message -----
Sent: Friday, September 21, 2018 9:52 AM
Subject: Re: [nvda] Web Browsers

The one thing that Jawes can afford to do is to make significant financial
clout to making a script work for a piece of software where the writers for
whatever reason are not prepared to make it obey conventions. Sadly this
same lack of expertise is now afflicting web sites again where accessibility
seems to men yes things should work but the clutter and complication factor
is far too high when you think about us blind folk not being able to get an
overview and general layout of a site. Helpful comments like the broken
green circle at the top left of the page are not welcome!
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Dave" <dlh007@...>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 1:52 PM
Subject: Re: [nvda] Web Browsers


> Hello Ian,
>
> Yes, I too noticed a Snappier behavior from this latest version of NVDA.
>
> I was using FireFox.
>
> As for the various Browsers being able to read all buttons, or Links, or
> different aspects on a Web Site-  Yes, I too have noticed this.
>
> I have been looking for work lately, and when on www.monster.com, a
> Employment Web Site, Sometimes I can read the Needed Links, and then
> other times, those links are not seen.
>
> Or once I've used them once, even if I return to the Main page of the
> web site, for what ever reason, I cannot find or read these links.  Have
> to shut down my Browser, and then re-visit the same site, and then those
> links will show up, but only sometimes.  Go Figure!
>
> And as far as differences between Screen Readers, Yes there too, I have
> noticed that one will read something better than the others.  I am a
> long time Window eyes user, who moved over to Jaws, and have had NVEA as
> the Screen Reader I call up to bail me out of Trouble when the others
> stop speaking.
>
> Over the last five years or so, I have actually found NVDA to be getting
> stronger and stronger.    In fact, when I needed to switch over to JAWS,
> at that time, I almost just switched to NVDA.  I have one program that
> NVDA will not read the screens, and Jaws does, so have been using Jaws.
>
> But, like I said, NVDA has come a long way, and is actually a very good
> Screen Reader.
>
>
>
> Dave
>
>
>
>
>




StationPlaylist Studio add-on 18.10.1/18.09.3-LTS #addonrelease

 

Hi all,

 

Shortly after release of SPL add-on 18.10, a broadcaster reported an issue where Studio won’t play the first track after an encoder was connected to a streaming server. After some investigation, the problem was traced to wxPython 4 (NVDA 2018.3.x) where text output would fail under some circumstances (specifically, wxPython 4 is more strict about where timers can be invoked from).

 

Because this affects everyone (except for people using really old builds) who are using NVDA 2018.3.x, I’m going to release version 18.10.1 and 18.09.3-LTS for those on stable and longterm channels, respectively. For those using development snapshots, revision A of September 21st build will also be released.

 

Thanks.

Cheers,

Joseph


Re: Still having problems with iTunes

Lino Morales
 

WIN 10 and I have 8 GB of ram. Running an i7 processor I think.

 

Sent from Mail for Windows 10

 


From: nvda@nvda.groups.io <nvda@nvda.groups.io> on behalf of Josh Kennedy <joshknnd1982@...>
Sent: Friday, September 21, 2018 9:51:56 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Still having problems with iTunes
 
What version of widows are you running, and what kind of processor and how much ram do you have?