Date   

Re: FW: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds?

René Linke <rene.linke@...>
 

Hi,

Here, I have the same problem here in NVDA 2018.3.2 and NVDA Alpha too. NVDA freezes after almost to fast navigating, reading or sometimes while typing the braile display is also blank, I need to switch the window and go back, then it's fine again.
It is totally strange.

René


Re: rate of speech

 

To be honest as a user on nvda, first from xp then 7 now 10.

Once I have my settings saved, then they are saved, I haven't thought about turning anything off and its a good idea for those that are not doodling round.

On 10/4/2018 8:21 AM, Gene wrote:
This appears to be one more example of why the default setting that NVDA should save changes on exit is a really bad default setting and should be changed. It would be a good idea for users to change the setting and it shouldn't be the default NVDA setting.

One of the reasons Window-eyes users felt freer to experiment than did JAWS users, at least thos who knew about this difference, is that Window-eyes didn't save settings permanently unless you manually saved them. That should be the same with NVDA. It's too easy to accidentally or inadvertently save settings you don't intend to save if save on exit is the default. there is such a thing as too much automation.

I'm quite sure, though I don't recall if I tested this, that speech settings you change in this way wouldn't be saved if you had save on exit disabled. Then you could close the program and revert to the settings you were using before.

Also, with default settings set as they are now, as long as you don't close the program, you can revert to the permanently saved settings by using the command control NVDA key r. So in the current case, if the program has not been closed, using this command will revert to the speech settings before you changed them.

If you make changes you do want to save permanently, you can save them with control NVDA key c. I would urge anyone who wants to use or try different settings without risking saving settings you don't want to save because theese are experimental or temporary use settings, to turn save settings on exit off and to only save settings when desired manually.

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

From: ely.r@...
Sent: Wednesday, October 03, 2018 2:10 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] rate of speech


Afternoon,
Hold down the NVDA key + Control then use right and left arrows to select the speech option you wish to change, and then the up and down arrows to change the speed, tone or voice act. Remember to keep those two keys held down as you make your changes. These do not revert to earlier settings when NVDA is restarted. Nice feature for making changes on the fly.
Rick

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Spivey
Sent: Wednesday, October 3, 2018 2:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] rate of speech

Press control+NVDA+v, then alt+r. That brings you to the rate slider, where you can use left/right to adjust it.

On 10/3/2018 10:05 AM, Howard Traxler wrote:
On my notebook (IBM thinkpad t40) I can use the
NVDA+shift+control nd up or ddown to change speech rate. On my new
HP6300 desktop, that key command makes it go faster but not slower. I
made the mistake of thinking after it got fast it would go in a circle
and start slow again. Not happen. Got it too fast to understand.
Now I can't get it slower again. Tried using jaws but it makes me
start the computer and, of course, jaws is off and nvda is running very fast.
Well then, there is narrator, but I can't remember how to start narrator.

Any suggestions?
Thanks.
Howard








Re: FW: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds?

Jaffar Sidek <jaffar.sidek10@...>
 

Confirmed by Winver.  Cheers!


On 4/10/2018 12:18 AM, Joseph Lee wrote:

Hi,

For those reporting continued problems: are you sure you are all running Windows 10 Version 1809 (October 2018 Update/build 17763)? If you all say “no”, then I’m afraid I cannot use your reports for this study. Thanks.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jaffar Sidek
Sent: Wednesday, October 3, 2018 9:14 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] FW: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds?

 

Hi.  Actually the problem is more severe when using intensive resource apps like Sound forge and Magix Samplitude.  NVDA totally freezes in the windows explorer view and takes some time to respond even after these apps have gone out of scope.  Cheers!

 

On 3/10/2018 2:00 PM, Afik Suffir wrote:

 

b.h

I can confirm the problem as well.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: Wednesday, October 3, 2018 8:58 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] FW: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds?

 

Hi Group,

 

I can confirm the problem. In fact, the only way I even see the window for Windows Explorer/This PC is when I move to the desktop and tab to the task bar and highlight the item that says 'windows explorer one running window.'  When I press enter on this to focus on the folder, everything disappears.  The title bar says: 'Explorer' but nothing shows up.  When Gold Wave is complete with its task, then everything goes back to normal.

 

 

On 10/3/2018 12:55 AM, Joseph Lee wrote:

Hi,

Note the steps below, and all requirements must be met in order to participate in this follow-up study.

Cheers,

Joseph

 

From: win10@win10.groups.io <win10@win10.groups.io> On Behalf Of Joseph Lee
Sent: Tuesday, October 2, 2018 9:55 PM
To: win10@win10.groups.io
Subject: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds?

 

Hi all,

 

For NvDA users running Version 1809: can you try the following for me and Quentin please:

 

  1. With NVDA 2018.3.x and Windows 10 Version 1809 installed, open File Explorer to any folder, preferably to a location where you have a large number of folders and files.
  2. Run an intensive task such as applying effects to a large audio file in programs such as GoldWave.
  3. Switch to File Explorer and see if NVDA reads folder and file names as you arrow through them.

 

This is a follow-up study to see if what NV Access and I have implemented in NVDA 2018.3 is working. If NVDA freezes, do let us know immediately so we can investigate as early as next week (Quentin and I are in the middle of a short vacation at the moment).

Cheers,

Joseph




-- 
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"

 



Re: Softwares to compose music for the blind

Damien Garwood <damien@...>
 

Hi Marco,
Audio is generally a recording, in terms of a computer represented in digital form, and reproducing roughly the same output regardless of equipment.
MIDI is a specification (Musical instrument digital interface) that describes how to communicate with digital musical instruments. The related files are simply instruction files containing several MIDI messages that are played through an instrument. This means that the output from said files depends very heavily on the equipment used to play it. Windows comes with its own MIDI synthesiser called Microsoft GS Wavetable which is based off of the Roland Virtual Sound Canvas, but with fewer instruments and effects. Usually, you will want to render a MIDI file into an appropriate audio format for people to be able to hear it how you imagine it to be heard. MIDI files are generally used for the composition process. They are the basis for converting the music to audio, or indeed a print score.
Hope this answers a few questions.
Cheers,
Damien.

On 03/10/2018 09:40 PM, Marco Oros wrote:
OK.
I'll return back to this discussion.
QWS is very good, I have a little Midi keyboard, because I would like to compose music outside My home.
But, another question is for You and It is related to this thing, what is difference between Audio and Midi and where to use first and second and what are Your best recommendations?
Because I would like to write article about It.
Dňa 13. 9. 2018 o 23:43 Jackie napísal(a):
It does have a virtual keyboard, though it's pretty hard to use that
w/any degree of precision.

On 9/13/18, Marco Oros <marco.oros93@...> wrote:
I haven't any MIDI device connected to My PC.

Can I use QWS also?





Re: Softwares to compose music for the blind

Marco Oros
 

OK.

I'll return back to this discussion.

QWS is very good, I have a little Midi keyboard, because I would like to compose music outside My home.

But, another question is for You and It is related to this thing, what is difference between Audio and Midi and where to use first and second and what are Your best recommendations?

Because I would like to write article about It.

Dňa 13. 9. 2018 o 23:43 Jackie napísal(a):

It does have a virtual keyboard, though it's pretty hard to use that
w/any degree of precision.

On 9/13/18, Marco Oros <marco.oros93@...> wrote:
I haven't any MIDI device connected to My PC.

Can I use QWS also?





Re: rate of speech

Mohamed
 

Yep, that's what I've been doing for about a year now, especially since I like to play with synthesizers that can be unstable, not saving configuration on exit means I don't have to worry about a bad synth making NVDA unusable.

On 10/3/2018 3:21 PM, Gene wrote:
This appears to be one more example of why the default setting that NVDA should save changes on exit is a really bad default setting and should be changed.  It would be a good idea for users to change the setting and it shouldn't be the default NVDA setting.
 
One of the reasons Window-eyes users felt freer to experiment than did JAWS users, at least thos who knew about this difference, is that Window-eyes didn't save settings permanently unless you manually saved them.  That should be the same with NVDA.  It's too easy to accidentally or inadvertently save settings you don't intend to save if save on exit is the default.  there is such a thing as too much automation. 
 
I'm quite sure, though I don't recall if I tested this, that speech settings you change in this way wouldn't be saved if you had save on exit disabled.  Then you could close the program and revert to the settings you were using before. 
 
Also, with default settings set as they are now, as long as you don't close the program, you can revert to the permanently saved settings by using the command control NVDA key r.  So in the current case, if the program has not been closed, using this command will revert to the speech settings before you changed them. 
 
If you make changes you do want to save permanently, you can save them with control NVDA key c.  I would urge anyone who wants to use or try different settings without risking saving settings you don't want to save because theese are experimental or temporary use settings, to turn save settings on exit off and to only save settings when desired manually.
 
Gene
----- Original Message -----
From: ely.r@...
Sent: Wednesday, October 03, 2018 2:10 PM
Subject: Re: [nvda] rate of speech

Afternoon,
Hold down the NVDA key + Control  then use right and left arrows to select the speech option you wish to change, and then the up and down arrows to change the speed, tone or voice act. Remember to keep those two keys held down as you make your changes. These do not revert to earlier settings when NVDA is restarted. Nice feature for making changes on the fly.
Rick

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Spivey
Sent: Wednesday, October 3, 2018 2:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] rate of speech

Press control+NVDA+v, then alt+r. That brings you to the rate slider, where you can use left/right to adjust it.

On 10/3/2018 10:05 AM, Howard Traxler wrote:
> On my notebook (IBM thinkpad t40) I can use the
> NVDA+shift+control nd up or ddown to change speech rate.  On my new
> HP6300 desktop, that key command makes it go faster but not slower.  I
> made the mistake of thinking after it got fast it would go in a circle
> and start slow again.  Not happen.  Got it too fast to understand.
> Now I can't get it slower again.  Tried using jaws but it makes me
> start the computer and, of course, jaws is off and nvda is running very fast.
> Well then, there is narrator, but I can't remember how to start narrator.
>
> Any suggestions?
> Thanks.
> Howard
>








Re: NVDA and Win 10 1809

Robert Doc Wright godfearer
 

i am not running into tis problem.

----- Original Message -----
From: "Don H" <lmddh50@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, October 2, 2018 6:36 PM
Subject: [nvda] NVDA and Win 10 1809


NVDA seems to be running great with Win 10 1809. There is one strange thing that NVDA is voicing when entering the settings app. NVDA says
C equals Microsoft Windows O equals Microsoft Corporation L equals readman S equals washington and one more that I can't understand.s
Sighted help says there is nothing like this on the screen.
Not a game changer just a little annoying




Re: FW: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds?

Robert Doc Wright godfearer
 

it works just fine. I'm having it max match my X-men folder of movies. I opened another drive and I can move within it with no problems. I was the one who was having the problem with having to wait until a process had completed before I could do anything. thank you very much!!!

----- Original Message -----
From: Joseph Lee
Sent: Tuesday, October 2, 2018 10:55 PM
Subject: [nvda] FW: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds?

Hi,

Note the steps below, and all requirements must be met in order to participate in this follow-up study.

Cheers,

Joseph

 

From: win10@win10.groups.io <win10@win10.groups.io> On Behalf Of Joseph Lee
Sent: Tuesday, October 2, 2018 9:55 PM
To: win10@win10.groups.io
Subject: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds?

 

Hi all,

 

For NvDA users running Version 1809: can you try the following for me and Quentin please:

 

  1. With NVDA 2018.3.x and Windows 10 Version 1809 installed, open File Explorer to any folder, preferably to a location where you have a large number of folders and files.
  2. Run an intensive task such as applying effects to a large audio file in programs such as GoldWave.
  3. Switch to File Explorer and see if NVDA reads folder and file names as you arrow through them.

 

This is a follow-up study to see if what NV Access and I have implemented in NVDA 2018.3 is working. If NVDA freezes, do let us know immediately so we can investigate as early as next week (Quentin and I are in the middle of a short vacation at the moment).

Cheers,

Joseph


Re: rate of speech

Gene
 

This appears to be one more example of why the default setting that NVDA should save changes on exit is a really bad default setting and should be changed.  It would be a good idea for users to change the setting and it shouldn't be the default NVDA setting.
 
One of the reasons Window-eyes users felt freer to experiment than did JAWS users, at least thos who knew about this difference, is that Window-eyes didn't save settings permanently unless you manually saved them.  That should be the same with NVDA.  It's too easy to accidentally or inadvertently save settings you don't intend to save if save on exit is the default.  there is such a thing as too much automation. 
 
I'm quite sure, though I don't recall if I tested this, that speech settings you change in this way wouldn't be saved if you had save on exit disabled.  Then you could close the program and revert to the settings you were using before. 
 
Also, with default settings set as they are now, as long as you don't close the program, you can revert to the permanently saved settings by using the command control NVDA key r.  So in the current case, if the program has not been closed, using this command will revert to the speech settings before you changed them. 
 
If you make changes you do want to save permanently, you can save them with control NVDA key c.  I would urge anyone who wants to use or try different settings without risking saving settings you don't want to save because theese are experimental or temporary use settings, to turn save settings on exit off and to only save settings when desired manually.
 
Gene

----- Original Message -----
From: ely.r@...
Sent: Wednesday, October 03, 2018 2:10 PM
Subject: Re: [nvda] rate of speech

Afternoon,
Hold down the NVDA key + Control  then use right and left arrows to select the speech option you wish to change, and then the up and down arrows to change the speed, tone or voice act. Remember to keep those two keys held down as you make your changes. These do not revert to earlier settings when NVDA is restarted. Nice feature for making changes on the fly.
Rick

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Spivey
Sent: Wednesday, October 3, 2018 2:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] rate of speech

Press control+NVDA+v, then alt+r. That brings you to the rate slider, where you can use left/right to adjust it.

On 10/3/2018 10:05 AM, Howard Traxler wrote:
> On my notebook (IBM thinkpad t40) I can use the
> NVDA+shift+control nd up or ddown to change speech rate.  On my new
> HP6300 desktop, that key command makes it go faster but not slower.  I
> made the mistake of thinking after it got fast it would go in a circle
> and start slow again.  Not happen.  Got it too fast to understand.
> Now I can't get it slower again.  Tried using jaws but it makes me
> start the computer and, of course, jaws is off and nvda is running very fast.
> Well then, there is narrator, but I can't remember how to start narrator.
>
> Any suggestions?
> Thanks.
> Howard
>








Re: Captchas Revisited

Mallard <mallard@...>
 

My heartfelt condolences... (smile).

Il 03/10/2018 19:45, Ron Canazzi ha scritto:
Someone just reported on another list that Runalla is defunct.



On 10/3/2018 12:56 PM, Sarah k Alawami wrote:
Rumolla if you can get it to workis grate.It is I think $1 for 100 credits and you have 3 months to use them but the service is grate.

On 2 Oct 2018, at 16:50, E.T. via Groups.Io wrote:

   I am not wanting to create a new flood on this one. (smiles) I could not keep up with the last thread on this topic so I may have missed any discussion about the object captchas (pictures) in particular.

   Is there a way to solve this type of captchas? Usually I can get around captchas by contacting someone by email. But in one case, I must solve the captcha in order to contact support.

From E.T.'s Keyboard...
   Ancient.Aliens@...
Many believe that we have been visited
in the past. What if it were true?




Re: SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

Gene
 

thanks for your answers.
 
Whenever it happens, I hope the next full version is backwards compatible to avoid such problems.
 
Gene

----- Original Message -----
From: Joseph Lee
Sent: Wednesday, October 03, 2018 2:06 PM
Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

Hi,

For the foreseeable future, yes.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, October 3, 2018 12:05 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

After the current transition, is it likely that compatible add-ons will continue to be compatible for future versions of Python 3?

 

Gene

----- Original Message -----

From: Joseph Lee

Sent: Wednesday, October 03, 2018 1:37 PM

Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

Hi,

Current release process for Python 3.x notes that each 3.x release receives support for five years. We’ll move along Python 3.x releases.

As for what Python 4.0.0 will be like, as of 2018, the crystal ball isn’t even showing that version yet.

As for what add-on authors will do, it is up to them to decide. What we the community can do is provide guidelines and recommendations, as well as coordinate our efforts.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, October 3, 2018 11:13 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

What will happen when Python 3 reaches end of life?  Is all this going to be gone through again when Python 4 becomes the supported version?  How many add-on developers are going to be willing to go through this every ten years?  Doesn't each version of Python have a life cycle of ten years? 

 

This needs further clarification.

 

Gene

----- Original Message -----

From: Joseph Lee

Sent: Wednesday, October 03, 2018 11:58 AM

Subject: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

Dear NVDA community,

 

A few days ago the add-ons community were told the following:

 

SystrayList add-on 3.0 will make the code compatible with Python 3 and make it work with old Windows releases.

 

Subsequent comments indicate that, although we still need to support old Windows releases if given a chance, we should eventually move onto newer releases. Thus, the following will happen in November 2018 and beyond:

 

  • November 2018: SystrayList add-on 3.0 will be released, migrating source code to Python 3. The code will still be compatible with Python 2, thus it can be used by people still using Windows XP and Vista.
  • Once Python 3 transition is declared by NV Access: one final SystrayList add-on will be released for old Windows releases.
  • Once Python 3 version of NVDA ships: whichever version of SystrayList add-on 3.x will be out by then, that version will absolutely require Python 3, thus completely dropping support for Windows XP and Vista.

 

You don’t really have to use this add-on to access Taskbar and notification area – you can press Windows+T to move to Taskbar and Windows+B to move focus to notification area. The add-on is there for convenience.

 

As for the question of Python 3 and old Windows releases: the version of Python 3 NV Access and some developers are looking at does not support Windows releases earlier than 7. There is a version of Python 3 (version 3.4) that does support old Windows releases, but by the time NVDA moves to Python 3, that Python version will reach end of life (released in 2014, Python 3.4’s scheduled end of life is 2019). Coupled with the fact that recent NVDA requires Windows 7, it was decided to end support for old Windows releases from SystrayList add-on once we move to Python 3.

 

This naturally raises the question: if Python 3 drops support for Windows XP and Vista, and if one add-on drops support for these, how about other add-ons? Yes, other add-ons that exclusively rely on Python 2 will not work in Python 3 version of NVDA. There are some add-ons the community has come to rely on that assumes Python 2 from the outset, and for some, it is difficult to port the source code to Python 3 without extensive testing and modifications. This is especially true for speech synthesizer and braille display driver add-ons, as the way Python interprets texts has changed fundamentally in Python 3. This also means once we do use Python 3 in NVDA Core itself, we must say goodbye to Windows XP and Vista.

 

So what should the add-ons community do, and in extension, what can the global NVDA community do? Although the details of the transition is still being worked out (with some developers researching possible showstoppers), I recommend the following to be done for now until NV Access announces transition to Python 3:

 

  1. Contact add-on authors and talk to them about their feelings about Python 3 transition.
  2. If we can’t contact authors of add-ons, do let the community know immediately so we can come up with a contingency plan (likely taking ownership of the add-on project by the community).
  3. If you are an add-on author, think about how Python 3 can affect your add-ons and plan accordingly. You don’t have to port your add-ons to Python 3 just yet.

 

For users of add-ons I created or am maintaining (SystrayList add-on included), I’ll make sure my add-ons are compatible with Python 3 the first day Python 3 edition of NVDA is released. Speaking of that progress, version 18.10 of Object Location Tones and ObjPad are Python 3 compatible, and in November, SystrayList 3.0.

 

Thanks.

Cheers,

Joseph


Re: rate of speech

ely.r@...
 

Afternoon,
Hold down the NVDA key + Control then use right and left arrows to select the speech option you wish to change, and then the up and down arrows to change the speed, tone or voice act. Remember to keep those two keys held down as you make your changes. These do not revert to earlier settings when NVDA is restarted. Nice feature for making changes on the fly.
Rick

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Spivey
Sent: Wednesday, October 3, 2018 2:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] rate of speech

Press control+NVDA+v, then alt+r. That brings you to the rate slider, where you can use left/right to adjust it.

On 10/3/2018 10:05 AM, Howard Traxler wrote:
On my notebook (IBM thinkpad t40) I can use the
NVDA+shift+control nd up or ddown to change speech rate. On my new
HP6300 desktop, that key command makes it go faster but not slower. I
made the mistake of thinking after it got fast it would go in a circle
and start slow again. Not happen. Got it too fast to understand.
Now I can't get it slower again. Tried using jaws but it makes me
start the computer and, of course, jaws is off and nvda is running very fast.
Well then, there is narrator, but I can't remember how to start narrator.

Any suggestions?
Thanks.
Howard


Re: SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

Hi,

For the foreseeable future, yes.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, October 3, 2018 12:05 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

After the current transition, is it likely that compatible add-ons will continue to be compatible for future versions of Python 3?

 

Gene

----- Original Message -----

From: Joseph Lee

Sent: Wednesday, October 03, 2018 1:37 PM

Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

Hi,

Current release process for Python 3.x notes that each 3.x release receives support for five years. We’ll move along Python 3.x releases.

As for what Python 4.0.0 will be like, as of 2018, the crystal ball isn’t even showing that version yet.

As for what add-on authors will do, it is up to them to decide. What we the community can do is provide guidelines and recommendations, as well as coordinate our efforts.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, October 3, 2018 11:13 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

What will happen when Python 3 reaches end of life?  Is all this going to be gone through again when Python 4 becomes the supported version?  How many add-on developers are going to be willing to go through this every ten years?  Doesn't each version of Python have a life cycle of ten years? 

 

This needs further clarification.

 

Gene

----- Original Message -----

From: Joseph Lee

Sent: Wednesday, October 03, 2018 11:58 AM

Subject: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

Dear NVDA community,

 

A few days ago the add-ons community were told the following:

 

SystrayList add-on 3.0 will make the code compatible with Python 3 and make it work with old Windows releases.

 

Subsequent comments indicate that, although we still need to support old Windows releases if given a chance, we should eventually move onto newer releases. Thus, the following will happen in November 2018 and beyond:

 

  • November 2018: SystrayList add-on 3.0 will be released, migrating source code to Python 3. The code will still be compatible with Python 2, thus it can be used by people still using Windows XP and Vista.
  • Once Python 3 transition is declared by NV Access: one final SystrayList add-on will be released for old Windows releases.
  • Once Python 3 version of NVDA ships: whichever version of SystrayList add-on 3.x will be out by then, that version will absolutely require Python 3, thus completely dropping support for Windows XP and Vista.

 

You don’t really have to use this add-on to access Taskbar and notification area – you can press Windows+T to move to Taskbar and Windows+B to move focus to notification area. The add-on is there for convenience.

 

As for the question of Python 3 and old Windows releases: the version of Python 3 NV Access and some developers are looking at does not support Windows releases earlier than 7. There is a version of Python 3 (version 3.4) that does support old Windows releases, but by the time NVDA moves to Python 3, that Python version will reach end of life (released in 2014, Python 3.4’s scheduled end of life is 2019). Coupled with the fact that recent NVDA requires Windows 7, it was decided to end support for old Windows releases from SystrayList add-on once we move to Python 3.

 

This naturally raises the question: if Python 3 drops support for Windows XP and Vista, and if one add-on drops support for these, how about other add-ons? Yes, other add-ons that exclusively rely on Python 2 will not work in Python 3 version of NVDA. There are some add-ons the community has come to rely on that assumes Python 2 from the outset, and for some, it is difficult to port the source code to Python 3 without extensive testing and modifications. This is especially true for speech synthesizer and braille display driver add-ons, as the way Python interprets texts has changed fundamentally in Python 3. This also means once we do use Python 3 in NVDA Core itself, we must say goodbye to Windows XP and Vista.

 

So what should the add-ons community do, and in extension, what can the global NVDA community do? Although the details of the transition is still being worked out (with some developers researching possible showstoppers), I recommend the following to be done for now until NV Access announces transition to Python 3:

 

  1. Contact add-on authors and talk to them about their feelings about Python 3 transition.
  2. If we can’t contact authors of add-ons, do let the community know immediately so we can come up with a contingency plan (likely taking ownership of the add-on project by the community).
  3. If you are an add-on author, think about how Python 3 can affect your add-ons and plan accordingly. You don’t have to port your add-ons to Python 3 just yet.

 

For users of add-ons I created or am maintaining (SystrayList add-on included), I’ll make sure my add-ons are compatible with Python 3 the first day Python 3 edition of NVDA is released. Speaking of that progress, version 18.10 of Object Location Tones and ObjPad are Python 3 compatible, and in November, SystrayList 3.0.

 

Thanks.

Cheers,

Joseph


Re: SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

Gene
 

After the current transition, is it likely that compatible add-ons will continue to be compatible for future versions of Python 3?
 
Gene

----- Original Message -----
From: Joseph Lee
Sent: Wednesday, October 03, 2018 1:37 PM
Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

Hi,

Current release process for Python 3.x notes that each 3.x release receives support for five years. We’ll move along Python 3.x releases.

As for what Python 4.0.0 will be like, as of 2018, the crystal ball isn’t even showing that version yet.

As for what add-on authors will do, it is up to them to decide. What we the community can do is provide guidelines and recommendations, as well as coordinate our efforts.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, October 3, 2018 11:13 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

What will happen when Python 3 reaches end of life?  Is all this going to be gone through again when Python 4 becomes the supported version?  How many add-on developers are going to be willing to go through this every ten years?  Doesn't each version of Python have a life cycle of ten years? 

 

This needs further clarification.

 

Gene

----- Original Message -----

From: Joseph Lee

Sent: Wednesday, October 03, 2018 11:58 AM

Subject: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

Dear NVDA community,

 

A few days ago the add-ons community were told the following:

 

SystrayList add-on 3.0 will make the code compatible with Python 3 and make it work with old Windows releases.

 

Subsequent comments indicate that, although we still need to support old Windows releases if given a chance, we should eventually move onto newer releases. Thus, the following will happen in November 2018 and beyond:

 

  • November 2018: SystrayList add-on 3.0 will be released, migrating source code to Python 3. The code will still be compatible with Python 2, thus it can be used by people still using Windows XP and Vista.
  • Once Python 3 transition is declared by NV Access: one final SystrayList add-on will be released for old Windows releases.
  • Once Python 3 version of NVDA ships: whichever version of SystrayList add-on 3.x will be out by then, that version will absolutely require Python 3, thus completely dropping support for Windows XP and Vista.

 

You don’t really have to use this add-on to access Taskbar and notification area – you can press Windows+T to move to Taskbar and Windows+B to move focus to notification area. The add-on is there for convenience.

 

As for the question of Python 3 and old Windows releases: the version of Python 3 NV Access and some developers are looking at does not support Windows releases earlier than 7. There is a version of Python 3 (version 3.4) that does support old Windows releases, but by the time NVDA moves to Python 3, that Python version will reach end of life (released in 2014, Python 3.4’s scheduled end of life is 2019). Coupled with the fact that recent NVDA requires Windows 7, it was decided to end support for old Windows releases from SystrayList add-on once we move to Python 3.

 

This naturally raises the question: if Python 3 drops support for Windows XP and Vista, and if one add-on drops support for these, how about other add-ons? Yes, other add-ons that exclusively rely on Python 2 will not work in Python 3 version of NVDA. There are some add-ons the community has come to rely on that assumes Python 2 from the outset, and for some, it is difficult to port the source code to Python 3 without extensive testing and modifications. This is especially true for speech synthesizer and braille display driver add-ons, as the way Python interprets texts has changed fundamentally in Python 3. This also means once we do use Python 3 in NVDA Core itself, we must say goodbye to Windows XP and Vista.

 

So what should the add-ons community do, and in extension, what can the global NVDA community do? Although the details of the transition is still being worked out (with some developers researching possible showstoppers), I recommend the following to be done for now until NV Access announces transition to Python 3:

 

  1. Contact add-on authors and talk to them about their feelings about Python 3 transition.
  2. If we can’t contact authors of add-ons, do let the community know immediately so we can come up with a contingency plan (likely taking ownership of the add-on project by the community).
  3. If you are an add-on author, think about how Python 3 can affect your add-ons and plan accordingly. You don’t have to port your add-ons to Python 3 just yet.

 

For users of add-ons I created or am maintaining (SystrayList add-on included), I’ll make sure my add-ons are compatible with Python 3 the first day Python 3 edition of NVDA is released. Speaking of that progress, version 18.10 of Object Location Tones and ObjPad are Python 3 compatible, and in November, SystrayList 3.0.

 

Thanks.

Cheers,

Joseph


Re: NVDA not reading slides in Presentation mode "slide show complete"

Joshua Crary <JCrary@...>
 

Ive tried using arrow keys, using control plus A to high light, nothing is read ut loud.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Mike Sedmak
Sent: Wednesday, October 3, 2018 2:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA not reading slides in Presentation mode "slide show complete"

Once the slideshow starts are you using the arrow keys to attempt to read the slides?

On 10/3/18, Joshua Crary <JCrary@...> wrote:
It is 7 slides and I start the slide show with F5, having had high
lighted the first slide.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Mike Sedmak
Sent: Wednesday, October 3, 2018 12:53 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA not reading slides in Presentation mode
"slide show complete"

A couple sanity check questions:

How many slides in the presentation?
Are you using f5 to start the presentation at the beginning?

In the past I have found that if I use f5 then escape then f5 a second
time, the slides are readable on the second time. YMMV

Mike

On 10/3/18, Joshua Crary <JCrary@...> wrote:
Anyone have any input on this? I have a presentation on Friday and
need to use power point.

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Joshua Crary
Sent: Tuesday, October 2, 2018 9:39 AM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA not reading slides in Presentation mode "slide
show complete"

Hello

I am running the latest NVDA and PPT 2016. The files are not in
protected mode. In edit view, I can read the slides. However, in
presentation mode (after pressing F5), and all NVDA reads out loud is
"slide show complete".
I hit space bar twice, and it exits the slide show.

Any thoughts on what the issue is? I have not had this issue before
with NVDA until the last 3 months or so. Before then, it has always
worked well with PPT.



Joshh Crary
Director of Student Accessibility Services Roxbury Community College
Roxbury, MA 02120
857.701.1410
jcrary@...<mailto:jcrary@...>


Caution: This email originated from outside of Roxbury Community
College. Do not click links or open attachments unless you recognize
the sender and know the content is safe.





Caution: This email originated from outside of Roxbury Community
College. Do not click links or open attachments unless you recognize
the sender and know the content is safe.





Caution: This email originated from outside of Roxbury Community College. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Re: rate of speech

Tyler Spivey
 

Press control+NVDA+v, then alt+r. That brings you to the rate slider,
where you can use left/right to adjust it.

On 10/3/2018 10:05 AM, Howard Traxler wrote:
On my notebook (IBM thinkpad t40) I can use the
NVDA+shift+control nd up or ddown to change speech rate.  On my new
HP6300 desktop, that key command makes it go faster but not slower.  I
made the mistake of thinking after it got fast it would go in a circle
and start slow again.  Not happen.  Got it too fast to understand.  Now
I can't get it slower again.  Tried using jaws but it makes me start the
computer and, of course, jaws is off and nvda is running very fast. 
Well then, there is narrator, but I can't remember how to start narrator.
 
Any suggestions?
Thanks.
Howard


Re: NVDA not reading slides in Presentation mode "slide show complete"

Mike Sedmak
 

Once the slideshow starts are you using the arrow keys to attempt to
read the slides?

On 10/3/18, Joshua Crary <JCrary@...> wrote:
It is 7 slides and I start the slide show with F5, having had high lighted
the first slide.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Mike
Sedmak
Sent: Wednesday, October 3, 2018 12:53 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA not reading slides in Presentation mode "slide show
complete"

A couple sanity check questions:

How many slides in the presentation?
Are you using f5 to start the presentation at the beginning?

In the past I have found that if I use f5 then escape then f5 a second time,
the slides are readable on the second time. YMMV

Mike

On 10/3/18, Joshua Crary <JCrary@...> wrote:
Anyone have any input on this? I have a presentation on Friday and
need to use power point.

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Joshua Crary
Sent: Tuesday, October 2, 2018 9:39 AM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA not reading slides in Presentation mode "slide
show complete"

Hello

I am running the latest NVDA and PPT 2016. The files are not in
protected mode. In edit view, I can read the slides. However, in
presentation mode (after pressing F5), and all NVDA reads out loud is
"slide show complete".
I hit space bar twice, and it exits the slide show.

Any thoughts on what the issue is? I have not had this issue before
with NVDA until the last 3 months or so. Before then, it has always
worked well with PPT.



Joshh Crary
Director of Student Accessibility Services Roxbury Community College
Roxbury, MA 02120
857.701.1410
jcrary@...<mailto:jcrary@...>


Caution: This email originated from outside of Roxbury Community
College. Do not click links or open attachments unless you recognize
the sender and know the content is safe.





Caution: This email originated from outside of Roxbury Community College. Do
not click links or open attachments unless you recognize the sender and know
the content is safe.




Re: SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

Hi,

Current release process for Python 3.x notes that each 3.x release receives support for five years. We’ll move along Python 3.x releases.

As for what Python 4.0.0 will be like, as of 2018, the crystal ball isn’t even showing that version yet.

As for what add-on authors will do, it is up to them to decide. What we the community can do is provide guidelines and recommendations, as well as coordinate our efforts.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, October 3, 2018 11:13 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

What will happen when Python 3 reaches end of life?  Is all this going to be gone through again when Python 4 becomes the supported version?  How many add-on developers are going to be willing to go through this every ten years?  Doesn't each version of Python have a life cycle of ten years? 

 

This needs further clarification.

 

Gene

----- Original Message -----

From: Joseph Lee

Sent: Wednesday, October 03, 2018 11:58 AM

Subject: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

 

Dear NVDA community,

 

A few days ago the add-ons community were told the following:

 

SystrayList add-on 3.0 will make the code compatible with Python 3 and make it work with old Windows releases.

 

Subsequent comments indicate that, although we still need to support old Windows releases if given a chance, we should eventually move onto newer releases. Thus, the following will happen in November 2018 and beyond:

 

  • November 2018: SystrayList add-on 3.0 will be released, migrating source code to Python 3. The code will still be compatible with Python 2, thus it can be used by people still using Windows XP and Vista.
  • Once Python 3 transition is declared by NV Access: one final SystrayList add-on will be released for old Windows releases.
  • Once Python 3 version of NVDA ships: whichever version of SystrayList add-on 3.x will be out by then, that version will absolutely require Python 3, thus completely dropping support for Windows XP and Vista.

 

You don’t really have to use this add-on to access Taskbar and notification area – you can press Windows+T to move to Taskbar and Windows+B to move focus to notification area. The add-on is there for convenience.

 

As for the question of Python 3 and old Windows releases: the version of Python 3 NV Access and some developers are looking at does not support Windows releases earlier than 7. There is a version of Python 3 (version 3.4) that does support old Windows releases, but by the time NVDA moves to Python 3, that Python version will reach end of life (released in 2014, Python 3.4’s scheduled end of life is 2019). Coupled with the fact that recent NVDA requires Windows 7, it was decided to end support for old Windows releases from SystrayList add-on once we move to Python 3.

 

This naturally raises the question: if Python 3 drops support for Windows XP and Vista, and if one add-on drops support for these, how about other add-ons? Yes, other add-ons that exclusively rely on Python 2 will not work in Python 3 version of NVDA. There are some add-ons the community has come to rely on that assumes Python 2 from the outset, and for some, it is difficult to port the source code to Python 3 without extensive testing and modifications. This is especially true for speech synthesizer and braille display driver add-ons, as the way Python interprets texts has changed fundamentally in Python 3. This also means once we do use Python 3 in NVDA Core itself, we must say goodbye to Windows XP and Vista.

 

So what should the add-ons community do, and in extension, what can the global NVDA community do? Although the details of the transition is still being worked out (with some developers researching possible showstoppers), I recommend the following to be done for now until NV Access announces transition to Python 3:

 

  1. Contact add-on authors and talk to them about their feelings about Python 3 transition.
  2. If we can’t contact authors of add-ons, do let the community know immediately so we can come up with a contingency plan (likely taking ownership of the add-on project by the community).
  3. If you are an add-on author, think about how Python 3 can affect your add-ons and plan accordingly. You don’t have to port your add-ons to Python 3 just yet.

 

For users of add-ons I created or am maintaining (SystrayList add-on included), I’ll make sure my add-ons are compatible with Python 3 the first day Python 3 edition of NVDA is released. Speaking of that progress, version 18.10 of Object Location Tones and ObjPad are Python 3 compatible, and in November, SystrayList 3.0.

 

Thanks.

Cheers,

Joseph


Re: NVDA not reading slides in Presentation mode "slide show complete"

Joshua Crary <JCrary@...>
 

It is 7 slides and I start the slide show with F5, having had high lighted the first slide.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Mike Sedmak
Sent: Wednesday, October 3, 2018 12:53 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA not reading slides in Presentation mode "slide show complete"

A couple sanity check questions:

How many slides in the presentation?
Are you using f5 to start the presentation at the beginning?

In the past I have found that if I use f5 then escape then f5 a second time, the slides are readable on the second time. YMMV

Mike

On 10/3/18, Joshua Crary <JCrary@...> wrote:
Anyone have any input on this? I have a presentation on Friday and
need to use power point.

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Joshua Crary
Sent: Tuesday, October 2, 2018 9:39 AM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA not reading slides in Presentation mode "slide
show complete"

Hello

I am running the latest NVDA and PPT 2016. The files are not in
protected mode. In edit view, I can read the slides. However, in
presentation mode (after pressing F5), and all NVDA reads out loud is "slide show complete".
I hit space bar twice, and it exits the slide show.

Any thoughts on what the issue is? I have not had this issue before
with NVDA until the last 3 months or so. Before then, it has always
worked well with PPT.



Joshh Crary
Director of Student Accessibility Services Roxbury Community College
Roxbury, MA 02120
857.701.1410
jcrary@...<mailto:jcrary@...>


Caution: This email originated from outside of Roxbury Community
College. Do not click links or open attachments unless you recognize
the sender and know the content is safe.





Caution: This email originated from outside of Roxbury Community College. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Re: SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

Gene
 

What will happen when Python 3 reaches end of life?  Is all this going to be gone through again when Python 4 becomes the supported version?  How many add-on developers are going to be willing to go through this every ten years?  Doesn't each version of Python have a life cycle of ten years? 
 
This needs further clarification.
 
Gene

----- Original Message -----
From: Joseph Lee
Sent: Wednesday, October 03, 2018 11:58 AM
Subject: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases

Dear NVDA community,

 

A few days ago the add-ons community were told the following:

 

SystrayList add-on 3.0 will make the code compatible with Python 3 and make it work with old Windows releases.

 

Subsequent comments indicate that, although we still need to support old Windows releases if given a chance, we should eventually move onto newer releases. Thus, the following will happen in November 2018 and beyond:

 

  • November 2018: SystrayList add-on 3.0 will be released, migrating source code to Python 3. The code will still be compatible with Python 2, thus it can be used by people still using Windows XP and Vista.
  • Once Python 3 transition is declared by NV Access: one final SystrayList add-on will be released for old Windows releases.
  • Once Python 3 version of NVDA ships: whichever version of SystrayList add-on 3.x will be out by then, that version will absolutely require Python 3, thus completely dropping support for Windows XP and Vista.

 

You don’t really have to use this add-on to access Taskbar and notification area – you can press Windows+T to move to Taskbar and Windows+B to move focus to notification area. The add-on is there for convenience.

 

As for the question of Python 3 and old Windows releases: the version of Python 3 NV Access and some developers are looking at does not support Windows releases earlier than 7. There is a version of Python 3 (version 3.4) that does support old Windows releases, but by the time NVDA moves to Python 3, that Python version will reach end of life (released in 2014, Python 3.4’s scheduled end of life is 2019). Coupled with the fact that recent NVDA requires Windows 7, it was decided to end support for old Windows releases from SystrayList add-on once we move to Python 3.

 

This naturally raises the question: if Python 3 drops support for Windows XP and Vista, and if one add-on drops support for these, how about other add-ons? Yes, other add-ons that exclusively rely on Python 2 will not work in Python 3 version of NVDA. There are some add-ons the community has come to rely on that assumes Python 2 from the outset, and for some, it is difficult to port the source code to Python 3 without extensive testing and modifications. This is especially true for speech synthesizer and braille display driver add-ons, as the way Python interprets texts has changed fundamentally in Python 3. This also means once we do use Python 3 in NVDA Core itself, we must say goodbye to Windows XP and Vista.

 

So what should the add-ons community do, and in extension, what can the global NVDA community do? Although the details of the transition is still being worked out (with some developers researching possible showstoppers), I recommend the following to be done for now until NV Access announces transition to Python 3:

 

  1. Contact add-on authors and talk to them about their feelings about Python 3 transition.
  2. If we can’t contact authors of add-ons, do let the community know immediately so we can come up with a contingency plan (likely taking ownership of the add-on project by the community).
  3. If you are an add-on author, think about how Python 3 can affect your add-ons and plan accordingly. You don’t have to port your add-ons to Python 3 just yet.

 

For users of add-ons I created or am maintaining (SystrayList add-on included), I’ll make sure my add-ons are compatible with Python 3 the first day Python 3 edition of NVDA is released. Speaking of that progress, version 18.10 of Object Location Tones and ObjPad are Python 3 compatible, and in November, SystrayList 3.0.

 

Thanks.

Cheers,

Joseph