Date   

Re: LAMBDA 1.3.0 #addonrelease

 

On Sun, Feb 16, 2020 at 01:01 PM, Joseph Lee wrote:
we must remember that not all authors are well versed in English idioms
Which is, at its heart, utterly beside the point.  I don't expect anyone to write documentation in a language they don't speak, just the one they do.  From all appearances there exists a cadre of folks who already volunteer time to do translations, and if I'm mistaken about that then such really should be cultivated.

I am entirely monolingual, and I can appreciate what it is to be monolingual no matter what your native language happens to be.  But if you write what's needed in that language, it can certainly be translated into however many others are needed where those who speak both languages can be found.

Even "just OK, but not absolutely perfect" translation from one language into another is preferable to a complete dearth of information.  If the only documentation for a given add-on were to be presented in other than English (in my case) I'd happily use Google Translate or Worldlingo translator to extract the major gist.  It wouldn't be the first time I've had to go that route, and it certainly won't be the last.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: LAMBDA 1.3.0 #addonrelease

 

Hi,

As part of basic review for add-ons, we the add-ons community look for documentation and ways to improve an add-on’s readme. For the most part, documentation for many add-ons provide essential information, although we must remember that not all authors are well versed in English idioms (I am known for writing good documentation, although I have to constantly remind myself that, as a non-native English speaker, I need to cater to folks like me and also find ways to improve my own add-ons’ docs).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Sunday, February 16, 2020 9:58 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] LAMBDA 1.3.0 #AddonRelease

 

On Sun, Feb 16, 2020 at 12:36 PM, Joseph Lee wrote:

The thing is, not many add-on authors are members of users list.

In this case I was referring to those that are and who might make an announcement here, but you bring up a very important point.

I have been disappointed, sorely disappointed, at how little documentation of any sort is available for a great many of the add-ons on both the official and under development pages.  I truly cannot fathom why anyone would dedicate the time and effort, which is substantial, to creating a tool for use with NVDA and then never give a public statement regarding what that tool actually does and how to use it, particularly on the page from which it is downloaded.

There are constantly people arriving who are new to NVDA.  I'm certainly not new to NVDA anymore, but I still have no idea of what a number of the add-ons do.  Whether I use them or not, that information should be front and center on the page where the add-on is obtained.  To my mind, it shouldn't even go up on such a page without documentation.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: LAMBDA 1.3.0 #addonrelease

 

On Sun, Feb 16, 2020 at 12:36 PM, Joseph Lee wrote:
The thing is, not many add-on authors are members of users list.
In this case I was referring to those that are and who might make an announcement here, but you bring up a very important point.

I have been disappointed, sorely disappointed, at how little documentation of any sort is available for a great many of the add-ons on both the official and under development pages.  I truly cannot fathom why anyone would dedicate the time and effort, which is substantial, to creating a tool for use with NVDA and then never give a public statement regarding what that tool actually does and how to use it, particularly on the page from which it is downloaded.

There are constantly people arriving who are new to NVDA.  I'm certainly not new to NVDA anymore, but I still have no idea of what a number of the add-ons do.  Whether I use them or not, that information should be front and center on the page where the add-on is obtained.  To my mind, it shouldn't even go up on such a page without documentation.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: LAMBDA 1.3.0 #addonrelease

 

Hi,

The thing is, not many add-on authors are members of users list. I can request such info from add-on authors when releasing stable versions (as an admin-level recommendation, as I’m the admin of NVDA add-ons list).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Sunday, February 16, 2020 9:30 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] LAMBDA 1.3.0 #AddonRelease

 

I would encourage those making these sorts of announcements to dedicate a paragraph or two to the actual purpose of the Add-On being discussed.

There is a constant churn of members here, and even those who have been around a long time may not be aware of Add-Ons that do not appear on the NVDA Official Add-Ons Page or even have any real awareness of the purpose of a number of them that do.  The Lambda Add-On Page under the official page is one that is particularly well-documented, but there are lots of add-ons that have virtually nothing noting what they're all about, how to use them, etc.

It never hurts to give a synopsis regarding the purpose of a given Add-On.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: LAMBDA 1.3.0 #addonrelease

 

I would encourage those making these sorts of announcements to dedicate a paragraph or two to the actual purpose of the Add-On being discussed.

There is a constant churn of members here, and even those who have been around a long time may not be aware of Add-Ons that do not appear on the NVDA Official Add-Ons Page or even have any real awareness of the purpose of a number of them that do.  The Lambda Add-On Page under the official page is one that is particularly well-documented, but there are lots of add-ons that have virtually nothing noting what they're all about, how to use them, etc.

It never hurts to give a synopsis regarding the purpose of a given Add-On.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


LAMBDA 1.3.0 #addonrelease

Iván Novegil
 

Hello all.


LAMBDA add-on 1.3.0 has just been released. It is now powered by Python 3, keeping backwards compatibility. The release of NVDA 2019.3 makes it urgent to reduce the testing period and to release this version as stable, although community guidelines. This doesn't means that it hasn't been tested, as they were, at least, two testers (Alberto and me). Of course, despite being a stable version, issues can be reported as usual.

Changes:

  • Support for newer version of NVDA (Support for Python 3)
  • Solved an issue while pressing duplicate line command NVDA+d in a blank line caused clipboard content to be pasted. Now when you press NVDA+d and you are in a blank line, a new blank line appears as expected.


Download it from: 

https://github.com/lambda-nvda/lambdaNvda/releases/download/1.3.0/lambda-1.3.0.nvda-addon


This version is possible thanks to the work of Alberto Zanella, main mantainer, and all the community translators. With regard to this, we welcome in this version some new languages and updated documentation for some of those which were already added.


Reviewers, please update addonFiles (our permissions were revoked by the migration), and our nvdaaddons repo, or let me know the transitory process to do that by myself. All the code is at https://github.com/lambda-nvda/lambdaNvda


Regards.

--

Iván Novegil Cancelas
Editor
ivan.novegil@...



Comunidad hispanohablante de NVDA | Proyecto NVDA.es
- www.NVDA.es
- @nvda_es

Usuario do NVDA en galego

***Esta mensaxe e/ou os seus adxuntos están dirixidos ao seu destinatario e poden conter información privilexiada ou confidencial. A utilización, copia ou divulgación dos mesmos por parte de alguén diferente do destinatario mencionado non están permitidas sen autorización. Se recibiu esta mensaxe por erro pregámoslle o comunique por esta mesma vía e a destrúa.***


Extended Winamp

Robert Doc Wright godfearer
 

For some reason on my desktop this addon is sporadic many times I will open WinAmp and press any of the keys that is suppose to give me file length information and it announces 0. Today I pressed ctrl+insert+f3 and after that the commands worked.

 

******

If we can't look at ourselves, and ask, why?  then where does the learning start?

 


my configuration is almost complete with 2019.3

 

Hi all.

Well except for the interactive fiction interpreters addon from n stockton which I have given up on ever getting updated, nvda is in of itself working.

I have made a portable version of nvda 2019.2.1 which has, just the addons I need, no win10 apps, no extras just the configurations I want and such.

I suggest for those that need older addons they just use nvda with the addons that don't update or are not updated or will never update from now on.

All I will use this version for is to play text games, its not ever going to update itself at all.


Re: vocalizer for nvda

Afik Souffir <afik.souffir@...>
 

 

Hi Tal,

 

You have dealer in Israel, Shmuel Naaman from philosoft company.

 

You can write to him  

In this email address

 

Hopes this helps,

 

Afik.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of tal lederman
Sent: Saturday, February 15, 2020 7:22 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] vocalizer for nvda

 

hello,
regarding vocalizer for nvda i bought it directly from nunace websites. is there any advantages for buying it from other dealers?


Re: screen not refreshing on certain sites

Scott Berry
 

I also have this problem.



On 2/15/2020 6:09 AM, Darren Harris via Groups.Io wrote:

Hi all,

 

I’m having an issue that I don’t quite know how to solve.

 

On some sites, audible being the chief, whenever I try making changes to a given page it doesn’t seem to refresh properproperly unless I alt tab out of it then alt tab back in.

 

This was happening before the update but I can’t seem to find how you stop it.

 

Can someone please help?

 

Many thanks.

--
Scott Berry
Medical Office Assistant
Associates in Allied health
Patient Advocate


Re: Continuing my saga with Vocalizer voices with latest NVDA

Gerardo Corripio
 

Do I have the right page? Because when I go to https://vocalizer-nvda.com/downloads I still see that the driver is version 3.0.14.

 

                                                                                              Enviado desde Correo para Windows 10

 

De: Rui Fontes
Enviado: sábado, 15 de febrero de 2020 06:49 p. m.
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] Continuing my saga with Vocalizer voices with latest NVDA

 

Hello!

 

All voices add-ons were corrected and already uploaded to the site...

So, this problem with lake of quotation marks should be over now...

 

Best regards,

 

Costumer support

Tiflotecnia, Lda.

 

 

Às 19:24 de 15/02/2020, Gerardo Corripio escreveu:

I sent an Email previously about my continuing saga with the Tiflotecnia Vocalizer voices; sorry for the bother on this subject... Here’s my log,hoping I can finally know what’s going on with the Vocalizer voices not wanting to cooperate on my system?

INFO - __main__ (13:18:39.261) - MainThread (6168):

Starting NVDA version 2019.3.1

INFO - core.main (13:18:39.545) - MainThread (6168):

Config dir: C:\Users\gerac\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (13:18:39.546) - MainThread (6168):

Loading config: C:\Users\gerac\AppData\Roaming\nvda\nvda.ini

INFO - core.main (13:18:39.748) - MainThread (6168):

Using Windows version 10.0.18363 workstation

INFO - core.main (13:18:39.749) - MainThread (6168):

Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]

INFO - core.main (13:18:39.749) - MainThread (6168):

Using comtypes version 1.1.7

INFO - core.main (13:18:39.749) - MainThread (6168):

Using configobj version 5.1.0 with validate version 1.0.1

WARNING - addonHandler._report_manifest_errors (13:18:39.839) - MainThread (6168):

Error loading manifest:

{'name': True, 'summary': VdtTypeError('the value "[\'Nuance Vocalizer Expressive - english Compact Voices (Australia\', \'British\', \'Irish\', \'Scotish\', \'South African and United States)\']" is of the wrong type.'), 'description': True, 'author': True, 'version': True, 'minimumNVDAVersion': True, 'lastTestedNVDAVersion': True, 'url': True, 'docFileName': True}

ERROR - addonHandler._getAvailableAddonsFromPath (13:18:39.839) - MainThread (6168):

Error loading Addon from path: C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-english Compact

Traceback (most recent call last):

  File "addonHandler\__init__.pyc", line 195, in _getAvailableAddonsFromPath

  File "addonHandler\__init__.pyc", line 297, in __init__

addonHandler.AddonError: Manifest file has errors.

WARNING - addonHandler._report_manifest_errors (13:18:39.846) - MainThread (6168):

Error loading manifest:

{'name': True, 'summary': VdtTypeError('the value "[\'Nuance Vocalizer Expressive - Portuguese and Spanish Compact Voices (Argentina\', \'Basque\', \'Brazil\', \'Cataluna\', \'Colombia\', \'Galician\', \'Mexico\', \'Portugal and Spain)\']" is of the wrong type.'), 'description': True, 'author': True, 'version': True, 'minimumNVDAVersion': True, 'lastTestedNVDAVersion': True, 'url': True, 'docFileName': True}

ERROR - addonHandler._getAvailableAddonsFromPath (13:18:39.846) - MainThread (6168):

Error loading Addon from path: C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-portugueseAndSpanish Compact Voices

Traceback (most recent call last):

  File "addonHandler\__init__.pyc", line 195, in _getAvailableAddonsFromPath

  File "addonHandler\__init__.pyc", line 297, in __init__

addonHandler.AddonError: Manifest file has errors.

INFO - synthDriverHandler.setSynth (13:18:40.671) - MainThread (6168):

Loaded synthDriver ibmeci

INFO - core.main (13:18:40.671) - MainThread (6168):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (13:18:40.673) - MainThread (6168):

Braille input initialized

INFO - braille.initialize (13:18:40.676) - MainThread (6168):

Using liblouis version 3.10.0

INFO - braille.initialize (13:18:40.682) - MainThread (6168):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (13:18:40.690) - MainThread (6168):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (13:18:41.049) - MainThread (6168):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:18:41.074) - _UIAHandler.UIAHandler.MTAThread (8868):

UIAutomation: IUIAutomation6

INFO - core.main (13:18:44.196) - MainThread (6168):

NVDA initialized

WARNING - external:synthDrivers.vocalizer_expressive.storage._loadLicenseData (13:19:10.401) - MainThread (6168):

Couldn't automatically unpickle 'C:\\Users\\gerac\\AppData\\Roaming\\vocalizer-for-nvda\\activation.dat', trying manual method

 

                                                                                              Enviado desde Correo para Windows 10

 

 


Re: Continuing my saga with Vocalizer voices with latest NVDA

Rui Fontes
 

Hello!


All voices add-ons were corrected and already uploaded to the site...

So, this problem with lake of quotation marks should be over now...


Best regards,

 

Costumer support

Tiflotecnia, Lda.



Às 19:24 de 15/02/2020, Gerardo Corripio escreveu:

I sent an Email previously about my continuing saga with the Tiflotecnia Vocalizer voices; sorry for the bother on this subject... Here’s my log,hoping I can finally know what’s going on with the Vocalizer voices not wanting to cooperate on my system?

INFO - __main__ (13:18:39.261) - MainThread (6168):

Starting NVDA version 2019.3.1

INFO - core.main (13:18:39.545) - MainThread (6168):

Config dir: C:\Users\gerac\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (13:18:39.546) - MainThread (6168):

Loading config: C:\Users\gerac\AppData\Roaming\nvda\nvda.ini

INFO - core.main (13:18:39.748) - MainThread (6168):

Using Windows version 10.0.18363 workstation

INFO - core.main (13:18:39.749) - MainThread (6168):

Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]

INFO - core.main (13:18:39.749) - MainThread (6168):

Using comtypes version 1.1.7

INFO - core.main (13:18:39.749) - MainThread (6168):

Using configobj version 5.1.0 with validate version 1.0.1

WARNING - addonHandler._report_manifest_errors (13:18:39.839) - MainThread (6168):

Error loading manifest:

{'name': True, 'summary': VdtTypeError('the value "[\'Nuance Vocalizer Expressive - english Compact Voices (Australia\', \'British\', \'Irish\', \'Scotish\', \'South African and United States)\']" is of the wrong type.'), 'description': True, 'author': True, 'version': True, 'minimumNVDAVersion': True, 'lastTestedNVDAVersion': True, 'url': True, 'docFileName': True}

ERROR - addonHandler._getAvailableAddonsFromPath (13:18:39.839) - MainThread (6168):

Error loading Addon from path: C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-english Compact

Traceback (most recent call last):

  File "addonHandler\__init__.pyc", line 195, in _getAvailableAddonsFromPath

  File "addonHandler\__init__.pyc", line 297, in __init__

addonHandler.AddonError: Manifest file has errors.

WARNING - addonHandler._report_manifest_errors (13:18:39.846) - MainThread (6168):

Error loading manifest:

{'name': True, 'summary': VdtTypeError('the value "[\'Nuance Vocalizer Expressive - Portuguese and Spanish Compact Voices (Argentina\', \'Basque\', \'Brazil\', \'Cataluna\', \'Colombia\', \'Galician\', \'Mexico\', \'Portugal and Spain)\']" is of the wrong type.'), 'description': True, 'author': True, 'version': True, 'minimumNVDAVersion': True, 'lastTestedNVDAVersion': True, 'url': True, 'docFileName': True}

ERROR - addonHandler._getAvailableAddonsFromPath (13:18:39.846) - MainThread (6168):

Error loading Addon from path: C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-portugueseAndSpanish Compact Voices

Traceback (most recent call last):

  File "addonHandler\__init__.pyc", line 195, in _getAvailableAddonsFromPath

  File "addonHandler\__init__.pyc", line 297, in __init__

addonHandler.AddonError: Manifest file has errors.

INFO - synthDriverHandler.setSynth (13:18:40.671) - MainThread (6168):

Loaded synthDriver ibmeci

INFO - core.main (13:18:40.671) - MainThread (6168):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (13:18:40.673) - MainThread (6168):

Braille input initialized

INFO - braille.initialize (13:18:40.676) - MainThread (6168):

Using liblouis version 3.10.0

INFO - braille.initialize (13:18:40.682) - MainThread (6168):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (13:18:40.690) - MainThread (6168):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (13:18:41.049) - MainThread (6168):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:18:41.074) - _UIAHandler.UIAHandler.MTAThread (8868):

UIAutomation: IUIAutomation6

INFO - core.main (13:18:44.196) - MainThread (6168):

NVDA initialized

WARNING - external:synthDrivers.vocalizer_expressive.storage._loadLicenseData (13:19:10.401) - MainThread (6168):

Couldn't automatically unpickle 'C:\\Users\\gerac\\AppData\\Roaming\\vocalizer-for-nvda\\activation.dat', trying manual method

 

                                                                                              Enviado desde Correo para Windows 10

 


Re: vocalizer for nvda

Rui Fontes
 

As far as I know, Nuance do not sell Vocalizer for NVDA...


Tiflotecnia, my company, and CodeFactory have Vocalizer for NVDA, distributed by various companies around the world...


Best regards,

 

Costumer support

Tiflotecnia, Lda.


Às 05:21 de 15/02/2020, tal lederman escreveu:

hello,
regarding vocalizer for nvda i bought it directly from nunace websites. is there any advantages for buying it from other dealers?


Re: Number and Abbrieviation Processing

John Isige
 

Out of curiosity, why doesn't the "Trust voice's language when
processing characters and symbols" setting at least handle the expansion
of abbreviations issue? I always wondered about that.


Anyway, if there's a way around this, it would be nice if somebody could
put up a dictionary file or such. It happens with the Microsoft voices,
SAPI 5 and OneCore, and SAPI 5 Eloquence I'm pretty sure. It's
especially annoying in web pages and file names, e.g. when you have
something like "heading level 3 Mary's Devotion", and it gets read as
something like "march threerd why's devotion". BTW it did it with that
example I made up, the second quote is how it read the first quote, SAPI
5 Eloquence from Code Factory.

On 2/15/2020 2:43 PM, Gary wrote:
Hi Quentin,

Thank you for your reply.

I tried both suggestions.  For the simpler replacement of the period
with the word "dot," this worked for the number processing, but made
reading text difficult.  For the regex solution, this didn't work as
expected, and I should have realized it before I tried.  The problem
with using regex is that there is no way to capture the value the
regex expression is matching to pass it from the input to the output.

For example, to adjust how NVDA handles numbers seperated by periods,
Here's what I entered:

String to match: [0-9].[0-9]
Replacement: [0-9] dot [0-9]

Doing this, NVDA properly made a replacement based on the string I
wish to have matched.  However, the replacement was literally what I
put into the replacement string.  So, for example:

2019.3.1

was read as:

201 [0-9] dot [0-9] [0-9] dot [0-9]

A script would need to be written to properly do this, I'm afraid.

Honestly, a toggle to turn off date processing would be best.
Otherwise, I suppose I'll need to look around at other software
synthesizers or see if this has ever been asked of the Microsoft
community.

Gary


Re: nvda 2019.3.1 with seika braille display

Mallard
 

Hello Joseph,


Thanks very much. It's really difficult to work with a braille display that doesn't scroll horizontally...

I'm patiently waiting...

Ciao,

Ollie

On 15/02/2020 18:51, Joseph Lee wrote:

Hi,

A developer of this display contacted NVDA developers about this a few hours ago, and they are working on resolving this issue.

Cheers,

Joseph

*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *tal lederman
*Sent:* Friday, February 14, 2020 9:04 PM
*To:* nvda@nvda.groups.io
*Subject:* [nvda] nvda 2019.3.1 with seika braille display


hello,
i have a very old model of seika braille display, i can't remember exactly the type. when i installed the latest version of nvda it stopped working. i went to the user guide and tried to download the updated version of seika driver from the link attached there, but it asked for a username and password and it didn't let me download the driver.
my computer runs with windows 7 64 bit.
thanks for your help


Re: NVDA and Google Chrome

George McCoy
 

Don,


It happens to me with two chromium based browsers, Google Chrome and Brave.  I am still running NVDA 2019.2.1 so I must conclude that the behavior is a result of a recent update to the Chromium renderer.


George

On 2/15/2020 9:23 AM, Don H wrote:
It seems that an issue I am having with links not working on web pages can be resolved by refreshing the page with insert F5.  It seems that the link is acrtivating just not being refreshed with the new info.  So my question is is this a NVDA or Google Chrome issue?



Re: Number and Abbrieviation Processing

Gary
 

Hi Quentin,

Thank you for your reply.

I tried both suggestions.  For the simpler replacement of the period with the word "dot," this worked for the number processing, but made reading text difficult.  For the regex solution, this didn't work as expected, and I should have realized it before I tried.  The problem with using regex is that there is no way to capture the value the regex expression is matching to pass it from the input to the output. 

For example, to adjust how NVDA handles numbers seperated by periods, Here's what I entered:

String to match: [0-9].[0-9]
Replacement: [0-9] dot [0-9]

Doing this, NVDA properly made a replacement based on the string I wish to have matched.  However, the replacement was literally what I put into the replacement string.  So, for example:

2019.3.1

was read as:

201 [0-9] dot [0-9] [0-9] dot [0-9]

A script would need to be written to properly do this, I'm afraid.

Honestly, a toggle to turn off date processing would be best.  Otherwise, I suppose I'll need to look around at other software synthesizers or see if this has ever been asked of the Microsoft community.

Gary
 


Re: Screen Curtain

Tyler Spivey
 

Go back into input gestures and go back down to screen curtain where you set it in the first place, and remove it.

Since you can't use your down arrow, try:

1. Hit the reset button in that dialog to reset all your custom gestures, or

2. Use NVDA+f2 before hitting the down arrow to pass it through.

Once you're on the gesture you want to remove the key from, expand it and go down to the key inside it. Hit remove.


Now, to add the correct one, go back to the gesture and hit add.

It'll ask you what gesture you want. Press it.

Then from the menu that comes up, pick what keyboard layout you want. All layouts is a good choice. Note that if you enter the wrong key, hitting escape in the menu will still add the key, so hit Remove and try again in that case.


On 2/15/2020 11:19 AM, Greg Rhodes wrote:

Default to toggle screen curtain on appears to be the Down Arrow. How do I set an alternate keyboard shortcut for toggling screen curtain on and off? Not finding directions to do this in the User Manual or NVDA Basics book. Thanks.

 

Greg

 


Re: Continuing my saga with Vocalizer voices with latest NVDA

Gerardo Corripio
 

Yes please contact me off-list to set up a time; I’ve the remote Addon but am not sure how to set it up properly. Thanks again! Here’s my log just in case it helps some.

INFO - __main__ (13:18:39.261) - MainThread (6168):

Starting NVDA version 2019.3.1

INFO - core.main (13:18:39.545) - MainThread (6168):

Config dir: C:\Users\gerac\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (13:18:39.546) - MainThread (6168):

Loading config: C:\Users\gerac\AppData\Roaming\nvda\nvda.ini

INFO - core.main (13:18:39.748) - MainThread (6168):

Using Windows version 10.0.18363 workstation

INFO - core.main (13:18:39.749) - MainThread (6168):

Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]

INFO - core.main (13:18:39.749) - MainThread (6168):

Using comtypes version 1.1.7

INFO - core.main (13:18:39.749) - MainThread (6168):

Using configobj version 5.1.0 with validate version 1.0.1

WARNING - addonHandler._report_manifest_errors (13:18:39.839) - MainThread (6168):

Error loading manifest:

{'name': True, 'summary': VdtTypeError('the value "[\'Nuance Vocalizer Expressive - english Compact Voices (Australia\', \'British\', \'Irish\', \'Scotish\', \'South African and United States)\']" is of the wrong type.'), 'description': True, 'author': True, 'version': True, 'minimumNVDAVersion': True, 'lastTestedNVDAVersion': True, 'url': True, 'docFileName': True}

ERROR - addonHandler._getAvailableAddonsFromPath (13:18:39.839) - MainThread (6168):

Error loading Addon from path: C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-english Compact

Traceback (most recent call last):

  File "addonHandler\__init__.pyc", line 195, in _getAvailableAddonsFromPath

  File "addonHandler\__init__.pyc", line 297, in __init__

addonHandler.AddonError: Manifest file has errors.

WARNING - addonHandler._report_manifest_errors (13:18:39.846) - MainThread (6168):

Error loading manifest:

{'name': True, 'summary': VdtTypeError('the value "[\'Nuance Vocalizer Expressive - Portuguese and Spanish Compact Voices (Argentina\', \'Basque\', \'Brazil\', \'Cataluna\', \'Colombia\', \'Galician\', \'Mexico\', \'Portugal and Spain)\']" is of the wrong type.'), 'description': True, 'author': True, 'version': True, 'minimumNVDAVersion': True, 'lastTestedNVDAVersion': True, 'url': True, 'docFileName': True}

ERROR - addonHandler._getAvailableAddonsFromPath (13:18:39.846) - MainThread (6168):

Error loading Addon from path: C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-portugueseAndSpanish Compact Voices

Traceback (most recent call last):

  File "addonHandler\__init__.pyc", line 195, in _getAvailableAddonsFromPath

  File "addonHandler\__init__.pyc", line 297, in __init__

addonHandler.AddonError: Manifest file has errors.

INFO - synthDriverHandler.setSynth (13:18:40.671) - MainThread (6168):

Loaded synthDriver ibmeci

INFO - core.main (13:18:40.671) - MainThread (6168):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (13:18:40.673) - MainThread (6168):

Braille input initialized

INFO - braille.initialize (13:18:40.676) - MainThread (6168):

Using liblouis version 3.10.0

INFO - braille.initialize (13:18:40.682) - MainThread (6168):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (13:18:40.690) - MainThread (6168):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (13:18:41.049) - MainThread (6168):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:18:41.074) - _UIAHandler.UIAHandler.MTAThread (8868):

UIAutomation: IUIAutomation6

INFO - core.main (13:18:44.196) - MainThread (6168):

NVDA initialized

WARNING - external:synthDrivers.vocalizer_expressive.storage._loadLicenseData (13:19:10.401) - MainThread (6168):

Couldn't automatically unpickle 'C:\\Users\\gerac\\AppData\\Roaming\\vocalizer-for-nvda\\activation.dat', trying manual method

 

                                                                                              Enviado desde Correo para Windows 10

 

De: Rui Fontes
Enviado: sábado, 15 de febrero de 2020 01:34 p. m.
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] Continuing my saga with Vocalizer voices with latest NVDA

 

We renew our offer to run a remote session...

 

Best regards,

 

Rui Fontes

Tiflotecnia, Lda.

 

Às 19:14 de 15/02/2020, Gerardo Corripio escreveu:

I tried still once again, with the driver Rui shared with us yesterday, to install, but no luck! Not even with Control+NVDA+s nor within the NVDA Menu does the Vocalizer shortcut appear as it should! I checked my Microsoft Security, but no notification or nothing came up, thus I was beginning to hink maybe the antivirus was the culprit,but no. What else could I try? I know it installed because when NVDA starts up, it says that at least one voice is needed to work Vocalizer; this even after installing the packs for English and Spanish from the site! Shnould I uninstall and reinstall? Because with NVDA EARLIER THAN 19.3.1 IT WORKED BEAUTIFULLY! WITH the Vocalizer shortcut and everything! Even weirder, I don’t even get the error of the license activation like you guys. What do you guys think is happening?

 

                                                                                              Enviado desde Correo para Windows 10

 

 


vocalizer voices and latest nvda

Don H
 

Sorry if I am confused. Is there a issue effecting all users with using the Vocalizer addon with VDDA 2019.3.1?