Date   

Re: a little two tone noise

Chris Smart
 

If you mean the descending tritone piano, (C F-sharp) sound, I believe that plays when NVDA has encountered an error. I don't think you have to do anything.



On 2020-12-23 12:44 p.m., mike mcglashon wrote:

Hey guys:

Again another question I’ve been meaning to ask,

What is the new “two tone” noise I hear once in a while;

I can’t seem to make it repeat in predictable circumstances?

Is it something useful (I know that is a subjective term);

I guess I’m asking if the noise is supposedly alerting me to something?

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 


Re: addons becoming incompatible after beta2 installed

Chris Smart
 

Mike


just wondering


why you


separate


every couple


of


words


in your


posts


by


a


blank line?


Re: a little two tone noise

 

Hi,

If you are using beta or an alpha snapshot, the two piano tones will let you know something has occurred that may warrant your attention, mostly dealing with errors.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mike mcglashon
Sent: Wednesday, December 23, 2020 9:45 AM
To: nvda@nvda.groups.io
Subject: [nvda] a little two tone noise

 

Hey guys:

Again another question I’ve been meaning to ask,

What is the new “two tone” noise I hear once in a while;

I can’t seem to make it repeat in predictable circumstances?

Is it something useful (I know that is a subjective term);

I guess I’m asking if the noise is supposedly alerting me to something?

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 


a little two tone noise

mike mcglashon
 

Hey guys:

Again another question I’ve been meaning to ask,

What is the new “two tone” noise I hear once in a while;

I can’t seem to make it repeat in predictable circumstances?

Is it something useful (I know that is a subjective term);

I guess I’m asking if the noise is supposedly alerting me to something?

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 


addons becoming incompatible after beta2 installed

mike mcglashon
 

Hi guys:

Installed nvda beta2 this morning;

When I did,

Many of my addons became incompatible, and,

I had to check a box claiming I understand this before installation;

Hence,

My question is,

How and where do I get the newer versions of the addons allegedly incompatible?

And,

Am I simply screwed if the author of the addon hasn’t updated it to the newest version of nvda?

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 


Re: Looking for newest vocalizer driver

darkmad88@...
 

Hello!
1.  Problem exists in any app i tried: Firefox(different versions), Chromium and some other Chromium-based browsers, Akelpad, Notepad, any edit field in Windows explorer, Total Commander.
2.I have no special profile for "Say all". Even a creation of clean user config for NVDA without any other addons does not help. Also there is no difference if i use installed or portable copy of NVDA.
Thank you for so quick answer.


Re: Working with Python in NVDA

 

Hi,
You will need Python 3.7. Liblouis bindings cannot be found in Python 3.8 or
later unless os.add_dll_directory (function/context manager) is called from
NvDA side, and I resolved it in a branch I'm working on to port NVDA to
Python 3.8 and later (it actually works apart from needing to install Python
3.8 specific dependencies):
https://github.com/josephsl/nvda
The branch to check out is "walrus" (without quotes) in reference to the
walrus operator (:=), which makes certain conditional statements easier to
read and digest (walrus operator, or assignment expression, was introduced
in Python 3.8). In the coming days, I will be releasing a really bleeding
edge version of NVDA (based on latest alpha snapshot), or for that matter,
two builds:
* Python 3.7 with wxPython GUI toolkit update (version 4.1.1)
* Python 3.8 with wxPython GUI toolkit update (4.1.1)

IMPORTANT: these bleeding-edge snapshots will come from my own fork of NVDA
and thus is unsupported by NV Access i.e. these are prototypes. The first
build will not affect add-ons that much, whereas the second build will break
at least one add-on and will cause BRLTTY support features to not function.
Both builds will have GUI toolkit related bugs, the most important being
NVDA will appear to freeze when you open NVDA's about dialog and similar
dialogs.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John J. Boyer
Sent: Wednesday, December 23, 2020 8:32 AM
To: nvda@nvda.groups.io
Subject: [nvda] Working with Python in NVDA

Hello Everyone,

I recently installed Python 3.9 on my Windows 10 desktop machine.
The first thing I noticed was that the statement import louis produces an
error,because the liblouis python bindings cannot be found.

At launch opens a console-like IDE. NVDA handles editing of lines nicely,
but there is no way to read previous lines except by pressing numpad 7.
There is also no wayh to
view the entire window, starting at the top.
I've also used NVDA with the Bash subsystem and ssh, with the same problem.

Any comments will be welcome.

Thanks,
John

--
John J. Boyer
Email: john.boyer@abilitiessoft.org
website: http://www.abilitiessoft.org
Status: Company dissolved but website and email addresses live.
Location: Madison, Wisconsin, USA
Mission: developing assistive technology software and providing STEM
services
that are available at no cost


Working with Python in NVDA

John J. Boyer
 

Hello Everyone,

I recently installed Python 3.9 on my Windows 10 desktop machine.
The first thing I noticed was that the statement import louis produces an error,because the liblouis python bindings cannot be found.

At launch opens a console-like IDE. NVDA handles editing of lines nicely, but there is no way to read previous lines except by pressing numpad 7.
There is also no wayh to
view the entire window, starting at the top.
I've also used NVDA with the Bash subsystem and ssh, with the same problem.

Any comments will be welcome.

Thanks,
John

--
John J. Boyer
Email: john.boyer@abilitiessoft.org
website: http://www.abilitiessoft.org
Status: Company dissolved but website and email addresses live.
Location: Madison, Wisconsin, USA
Mission: developing assistive technology software and providing STEM services
that are available at no cost


Re: NVDA 2020.4 Beta 2 is now available

Rosemarie Chavarria
 

Hi, Quentin,

 

I just downloaded this new version of NVDA and so-far it’s working great.

 

Rosemarie

 

 

 

Sent from Mail for Windows 10

 

From: Quentin Christensen
Sent: Wednesday, December 23, 2020 7:31 AM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA 2020.4 Beta 2 is now available

 

Hi everyone,

 

NVDA 2020.4 Beta2 is now available for download & testing. Since Beta1 we added Afrikaans Grade 2 braille, fixed reporting incorrect information when copying fails, QWERTY input with Papenmeier braille displays & an error affecting some add-ons. More at: https://www.nvaccess.org/post/nvda-2020-4beta2/

 

--

Quentin Christensen
Training and Support Manager

 

 


NVDA 2020.4 Beta 2 is now available

Quentin Christensen
 

Hi everyone,

NVDA 2020.4 Beta2 is now available for download & testing. Since Beta1 we added Afrikaans Grade 2 braille, fixed reporting incorrect information when copying fails, QWERTY input with Papenmeier braille displays & an error affecting some add-ons. More at: https://www.nvaccess.org/post/nvda-2020-4beta2/

--
Quentin Christensen
Training and Support Manager


Re: Looking for newest vocalizer driver

Rui Fontes
 

Hello!


To start debugging, two questions:

1 - In what apps are you trying the automatic language switching with SayAll?


2 - Have you any NVDA profil to sayAll?

If so, check if automatic language switching is on.


Best regards,


Customer support

Tiflotecnia, Lda.


Às 13:52 de 23/12/2020, darkmad88@... escreveu:

Hello, Rui! This driver works almost fine in my case, but there is one issue: automatic language switching doesn't work in "Say all" mode. I tried different russian+english voice combinations andsettings for automatic lang switching. It works fine in all modes except "Say all". Is there a chance to fix this?
Best regards and thank you for your work!


Re: Looking for newest vocalizer driver

darkmad88@...
 

Hello, Rui! This driver works almost fine in my case, but there is one issue: automatic language switching doesn't work in "Say all" mode. I tried different russian+english voice combinations andsettings for automatic lang switching. It works fine in all modes except "Say all". Is there a chance to fix this?
Best regards and thank you for your work!


Re: NVDA 2020.4 Beta 1 now available

 

Hi,

This is one of the reasons for using betas as portable copies. Although you won’t be able to test everything, it should give you a feel as to what’s new and changed (and a few months from now, add-ons that must be updated).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dan Miner via groups.io
Sent: Tuesday, December 22, 2020 9:52 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2020.4 Beta 1 now available

 

I’m on the side of parallel install for the beta line.  I’ve done it both ways over my career as software a developer and yes there is a bit more complexity with the release management side of it… but it is safer for users and potentially easier to switch back and forth if provisioned for in the project.  Saying that, I see the complexity of that with the logon screen support and roaming settings stuff.

 

I've not participated in trying a beta as I thought this was the case and I just don't want to crater my box.  *grin*

 

    Dan

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen

Sent: Tuesday, December 22, 2020 2:45 PM

To: nvda@nvda.groups.io

Subject: Re: [nvda] NVDA 2020.4 Beta 1 now available

 

Jim,

 

Interesting point.  The way it works currently is that:

- We regularly release Alpha snapshots every few days or sometimes several times a day, regardless of where else we are in the release cycle

- Three or four weeks before a release, we release a beta version.  If any bugs are found, we release a second (or third etc) beta.  This time around, the beta will have a little longer so we didn't either rush things to push a release before Christmas, or leave it entirely until next year.

- A week or so before the release, we put out a "Release Candidate" (RC) build.  Again, if any issues are found, we go to RC2, RC3 etc.

- Once all the big bugs have been ironed out (or pulled), we put out the final version.

 

The Beta and RC versions are set by default to prompt to update as new beta or RC builds, or the final stable version comes out.  If we were to have the beta install in a separate place, then it would make that sequence more complex.  And it would also be one more thing to change at some point (when we move to the RC?  Or only when we move to the stable version?) - and of course, any change is an opportunity to break something.

 

That's my thoughts off the top of my head, but it's an idea I'm happy to take more thoughts on.

 

Quentin.

 

On Tue, Dec 22, 2020 at 10:20 AM Jim Pipczak <jim.pipczak@...> wrote:

Hi all,

 

I believe that the beta should be installed into its own directory and not overwrite the existing full version. Your thoughts would be appreciated.

 

Thanks,

Jim

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen

Sent: Thursday, 17 December 2020 9:14 AM

To: nvda@nvda.groups.io

Subject: [nvda] NVDA 2020.4 Beta 1 now available

 

Hi everyone,

 

Lazily copying my tweet - so you get everything in one sentence: NVDA 2020.4Beta1 is now available for testing, including  new Chinese Input methods, an update to Liblouis, the elements list now works in focus mode, context sensitive help pressing F1 in NVDA dialogs & heaps more!

 

Read more and download from: https://www.nvaccess.org/post/nvda-2020-4beta1/

 

As usual, please do report any issues on GitHub.

 

Kind regards

 

Quentin.

 

 

--

Quentin Christensen

Training and Support Manager

 

Web: www.nvaccess.org

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

User group: https://nvda.groups.io/g/nvda

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

Twitter: @NVAccess

 

Jim Pipczak

Access Technology Service Development Lead

Client Services

Vision Australia

14 & 17 Barrett Street Kensington VIC 3031

 

M: +614 3375 7598 T: +613 8378 1243 (I: 344243)

E: Jim.Pipczak@...

www.visionaustralia.org

 

Vision Australia is committed to supporting the blind and low vision community through COVID-19. Find out about our response and free support resources online at www.visionaustralia.org/COVID19.

 

  

 

 

Vision Australia acknowledges Aboriginal and Torres Strait Islander people as the traditional custodians of the land on which we operate. We have an inclusive culture and value diversity and all abilities.

 

 

 

 

 

--

Quentin Christensen

Training and Support Manager

 

Web: www.nvaccess.org

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

User group: https://nvda.groups.io/g/nvda

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

Twitter: @NVAccess

 


Re: NVDA 2020.4 Beta 1 now available

Dan Miner
 

I’m on the side of parallel install for the beta line.  I’ve done it both ways over my career as software a developer and yes there is a bit more complexity with the release management side of it… but it is safer for users and potentially easier to switch back and forth if provisioned for in the project.  Saying that, I see the complexity of that with the logon screen support and roaming settings stuff.

 

I've not participated in trying a beta as I thought this was the case and I just don't want to crater my box.  *grin*

 

    Dan

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen

Sent: Tuesday, December 22, 2020 2:45 PM

To: nvda@nvda.groups.io

Subject: Re: [nvda] NVDA 2020.4 Beta 1 now available

 

Jim,

 

Interesting point.  The way it works currently is that:

- We regularly release Alpha snapshots every few days or sometimes several times a day, regardless of where else we are in the release cycle

- Three or four weeks before a release, we release a beta version.  If any bugs are found, we release a second (or third etc) beta.  This time around, the beta will have a little longer so we didn't either rush things to push a release before Christmas, or leave it entirely until next year.

- A week or so before the release, we put out a "Release Candidate" (RC) build.  Again, if any issues are found, we go to RC2, RC3 etc.

- Once all the big bugs have been ironed out (or pulled), we put out the final version.

 

The Beta and RC versions are set by default to prompt to update as new beta or RC builds, or the final stable version comes out.  If we were to have the beta install in a separate place, then it would make that sequence more complex.  And it would also be one more thing to change at some point (when we move to the RC?  Or only when we move to the stable version?) - and of course, any change is an opportunity to break something.

 

That's my thoughts off the top of my head, but it's an idea I'm happy to take more thoughts on.

 

Quentin.

 

On Tue, Dec 22, 2020 at 10:20 AM Jim Pipczak <jim.pipczak@...> wrote:

Hi all,

I believe that the beta should be installed into its own directory and not overwrite the existing full version. Your thoughts would be appreciated.

Thanks,

Jim

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen

Sent: Thursday, 17 December 2020 9:14 AM

To: nvda@nvda.groups.io

Subject: [nvda] NVDA 2020.4 Beta 1 now available

Hi everyone,

Lazily copying my tweet - so you get everything in one sentence: NVDA 2020.4Beta1 is now available for testing, including  new Chinese Input methods, an update to Liblouis, the elements list now works in focus mode, context sensitive help pressing F1 in NVDA dialogs & heaps more!

Read more and download from: https://www.nvaccess.org/post/nvda-2020-4beta1/

As usual, please do report any issues on GitHub.

Kind regards

Quentin.

 

--

Quentin Christensen

Training and Support Manager

Web: www.nvaccess.org

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

User group: https://nvda.groups.io/g/nvda

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

Twitter: @NVAccess

 

Jim Pipczak

Access Technology Service Development Lead

Client Services

Vision Australia

14 & 17 Barrett Street Kensington VIC 3031

 

M: +614 3375 7598 T: +613 8378 1243 (I: 344243)

E: Jim.Pipczak@...

www.visionaustralia.org

 

Vision Australia is committed to supporting the blind and low vision community through COVID-19. Find out about our response and free support resources online at www.visionaustralia.org/COVID19.

  

 

 

Vision Australia acknowledges Aboriginal and Torres Strait Islander people as the traditional custodians of the land on which we operate. We have an inclusive culture and value diversity and all abilities.

 

 

 

 

 

--

Quentin Christensen

Training and Support Manager

 

Web: www.nvaccess.org

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

User group: https://nvda.groups.io/g/nvda

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

Twitter: @NVAccess

 


Re: NVDA 2020.4 Beta 1 now available

Quentin Christensen
 

Jim,

Interesting point.  The way it works currently is that:
- We regularly release Alpha snapshots every few days or sometimes several times a day, regardless of where else we are in the release cycle
- Three or four weeks before a release, we release a beta version.  If any bugs are found, we release a second (or third etc) beta.  This time around, the beta will have a little longer so we didn't either rush things to push a release before Christmas, or leave it entirely until next year.
- A week or so before the release, we put out a "Release Candidate" (RC) build.  Again, if any issues are found, we go to RC2, RC3 etc.
- Once all the big bugs have been ironed out (or pulled), we put out the final version.

The Beta and RC versions are set by default to prompt to update as new beta or RC builds, or the final stable version comes out.  If we were to have the beta install in a separate place, then it would make that sequence more complex.  And it would also be one more thing to change at some point (when we move to the RC?  Or only when we move to the stable version?) - and of course, any change is an opportunity to break something.

That's my thoughts off the top of my head, but it's an idea I'm happy to take more thoughts on.

Quentin.

On Tue, Dec 22, 2020 at 10:20 AM Jim Pipczak <jim.pipczak@...> wrote:

Hi all,

 

I believe that the beta should be installed into its own directory and not overwrite the existing full version. Your thoughts would be appreciated.

 

Thanks,

Jim

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Thursday, 17 December 2020 9:14 AM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA 2020.4 Beta 1 now available

 

Hi everyone,

 

Lazily copying my tweet - so you get everything in one sentence: NVDA 2020.4Beta1 is now available for testing, including  new Chinese Input methods, an update to Liblouis, the elements list now works in focus mode, context sensitive help pressing F1 in NVDA dialogs & heaps more!

 

 

As usual, please do report any issues on GitHub.

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 


Jim Pipczak
Access Technology Service Development Lead
Client Services
Vision Australia
14 & 17 Barrett Street Kensington VIC 3031

M: +614 3375 7598 T: +613 8378 1243 (I: 344243)
E: Jim.Pipczak@...
www.visionaustralia.org


Vision Australia is committed to supporting the blind and low vision community through COVID-19. Find out about our response and free support resources online at www.visionaustralia.org/COVID19.




--
Quentin Christensen
Training and Support Manager


Re: Nvda beta still not keeping the setting to run at startup.

Kevin Cussick
 

I should have said that it will run at startup, I think I did but can not remember. anyway it was running at startup and then installing it changed the setting. this has been a problem for some years now maybe 2 years and I hope at some point maybe this year this might be fixed.

On 22/12/2020 02:42, Vickie Andrada wrote:
Hmmmm, I've never had a problem getting NVDA to run at start up.
Vicki
On 12/21/2020 5:30 PM, Kevin Cussick via groups.io wrote:
Hi all, OK not really much of a problem but this has being going on now for years and it would be nice to see a fix for this nvda did not keep[ my setting to run at startup. but anyway got it fixed I installed the beta last week but my computer was not shut down. until last night and when I booted up to night nvda was not running fixed for now. just thought I would report.





Re: Dell issues - information request

William
 

are you sure it is cpu not ram?


Rowen Cary 於 22/12/2020 20:44 寫道:

I used to use latitude7410 and I was really troubled by the Realtek driver.
After using it for a period of time, the CPU occupancy rate will rise to 100, but I don't use this machine now, I can be sure that this is a problem with the Realtek driver, and the specific version has been forgotten.





Skim reading suggestions

William
 

Hi all,

Not sure if this is appropiate to post here, or else do let me know where should I put these content.


I am testing latest beta 20.4 of nvda.

I found that the function Skim reading is very useful and interesting.

With regard to this, can I suggest that nvda adding a function for user to configure which key will not stop say all.

For instance, the find next for notepad++ is f3 and shift f3, the find next in word is shift f4, I want to configure these keys to be included in that function.

Thanks,

William


Re: Dell issues - information request

Rowen Cary
 

I used to use latitude7410 and I was really troubled by the Realtek driver.
After using it for a period of time, the CPU occupancy rate will rise to 100, but I don't use this machine now, I can be sure that this is a problem with the Realtek driver, and the specific version has been forgotten.


Please your help with one program in Nvda

Jarek.Krcmar
 

Hello everyone
I am a believer and that is why I am from a web address
www.jw.org
downloaded and installed JWLibrary. But I found that Nvda doesn't read any text to me in this program.
Could you please advise me what to do with it?
Thank you in advance for your help.

--
Jarek

6621 - 6640 of 86492