Re: Navigating Text since NVDA 2017.3


Antony Stone
 

The question was not how to restore NVDA 2017.3 to its default settings; the
question was how to make NVDA 2017.3 work (in this specific respect) like NVDA
2017.2 and earlier.

Damien Sykes reported that he had hear from Tyler Spivey that "You can change
it, but you have to know how and where it’s stored. It’s not in the
configuration dialogs."

There may be more information in the GIT documentation; I am not sure.


Antony.

On Thursday 07 December 2017 at 13:36:30, Robert Mendoza wrote:

To reset to configuration factory default, press nvda plus control plus
R, thrice.

On 12/7/2017 8:05 PM, zahra wrote:
yes, but i want to return the behaviour of nvda 17.3 to the previous
versions. what should i do?

On 12/7/17, Brian's Mail list account via Groups.Io wrote:
If you are still on .3 it is already there. I seem to recall your
computer is quite old and running xp?

If so then this discussion is not applicable.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "zahra" <nasrinkhaksar3@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 7:47 AM
Subject: Re: [nvda] Navigating Text since NVDA 2017.3


hi.
can you please explane for me how should i change the behaviour to the
previous state?
God bless you all.

On 12/7/17, Quentin Christensen wrote:
Well, to those who need the answer, that you got the information out
there is as important a part of the process as Tyler in tracking it
down. A team effort :)

On Thu, Dec 7, 2017 at 12:57 PM, Damien Sykes wrote:
Hi,
Actually, Tyler did all the tracking down, I simply put it out here
for people to understand what was going on. I still don’t quite
understand the magnitude of the issue myself. I noticed the issue,
Tyler told me what it was and how to change it, I changed it and
verified that it worked, I “published”, if you will, the results.
Cheers.
Damien.

*From:* Quentin Christensen <quentin@...>
*Sent:* Thursday, December 07, 2017 1:27 AM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] Navigating Text since NVDA 2017.3

Damien,

Well tracked down :)

Quentin.

On Thu, Dec 7, 2017 at 11:30 AM, Damien Sykes
<damien@...

wrote:
Hi guys,
For anyone like me who has noticed the text lag and wonders why. The
following came from Tyler Spivey, who helped me resolve this strange
conundrum.
It actually appears that NVDA has always had some reason or other to
have
to wait a predetermined amount of time for the cursor to move in
order to
read whatever new information is under the cursor, or to inform of
highlighted text, or if no change has occurred, to state the fact
that we
are at the beginning or end of the field. Until 2017.3, this was 30
milliseconds, a time so short that you would hardly notice it.

An entry in the change log for 2017.3 reads:
• In editable text, when moving the caret (e.g. with the cursor keys
or backspace), NVDA's spoken feedback is now more accurate in many
cases, particularly in Chrome and terminal applications.

In fact, one of the ways this seems to have been resolved was to
increase
the cursor wait time from 30 to 100 milliseconds, which may not seem
much
but is in fact a 230% increase. This means that people who are well
tuned
in to how NVDA read data previously, and perhaps more importantly
rely on
speed, will notice this change.
This is all apparently covered on GitHub, which, as far as I’m
concerned
isn’t really a user-friendly platform (that’s to say it’s meant for
developers, and expert ones at that, which means you’re going to see
a lot
of technical jargon). Some may argue that this issue is a very fine
line
between a development technicality and usability, and since I seem to
have
been the only one who cared or even noticed this, I’m inclined to
agree.
But at least it’s out there now.
So, to summarise:
1. This is actually intended behaviour.
2. You can change it, but you have to know how and where it’s stored.
It’s not in the configuration dialogs. Some may not even find it
worth the
effort – I only did because it ground straight through my sensitive
teeth
and pounded through my skull.
3. If you change it, be aware that you may not get the improved
accuracy
stated in the change log entry quoted above.
Cheers.
Damien.
--
This email was created using 100% recycled electrons.

Please reply to the list;
please *don't* CC me.

Join nvda@nvda.groups.io to automatically receive all group messages.