Re: Update: Defender no longer mistakenly flagging NVDA
|
Gene
If you need to register, the add-on should let NVDA
switch to its default voice to read the message. Evidently, it doesn't,
still using Eloquence to read the announcement and offering no way to switch to
a different voice. Perhaps there is a way that should be discussed.
I think that using another screen-reader and modifying the NVDA.ini file would
solve the problem. In general, if a synthesizer the user sets as default
can't be used for some reason, NvDA defaults to its default. If this is
what is going on, that the user is trapped in a register message and can't
switch to another synthesizer, that is very poor design.
To be safe, when upgrading to this version of NVDA
if using any synthesizer that may not be compatible, it would be a good idea to
switch to another synthesizer that will have no compatibility problems and make
sure that setting is saved by using control NVDA key c after the change is
made. Then, turn off save settings on exit so you won't upgrade, try the
incompatible voice, close NVDA, and have that new setting saved. All this
should be done before upgrading.
Gene ----- Original Message ----- From: Rui Fontes
Sent: Monday, February 10, 2020 11:51 AM
Subject: Re: [nvda] Update: Defender no longer mistakenly flagging
NVDA Normally that message is from Eloquence from CodeFactory... Rui Fontes Às 17:16 de 10/02/2020, Robert Doc Wright godfearer
escreveu:
|
|
|