Re: Those with other screenreaders as well problem


Brian's Mail list account <bglists@...>
 

What for Jaws? Its not avoidable from freedom scientific it pesters you, but it was only after the update which did other things to jaws too, apparently that I noticed the part about Skype. I do not use it either, but I suspect the problem with not putting windows back as it found it is a bug introduced. Note that I did not try the registry fix tool in nvda.

To my mind it had probably hooked something that nvda wanted and did not let go of it correctly.
Minor irritation but thought I'd mention it. I have noticed before that when nvda does start to play up going into protected desktop and out again can often fix things.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Cohn, Jonathan" <jcohn@air.org>
To: <nvda@nvda.groups.io>; <nvda@groups.io>
Sent: Friday, August 31, 2018 12:39 AM
Subject: Re: [nvda] Those with other screenreaders as well problem


I have been avoiding this update, because I don’t use Skype.

Get Outlook for iOS<https://aka.ms/o0ukef>

________________________________
From: 30101230420n behalf of
Sent: Thursday, August 30, 2018 4:38 PM
To: nvda@groups.io
Subject: [nvda] Those with other screenreaders as well problem

Now a number of people here use other screenreaders on the same machine,
and normally if one shuts one down and starts another and then goes the
other way, all works fine, however this evening as the old joke goes , a
funny thing happened on the way back to nvda from Jaws.
I always try to keep things up to date of course, and tonight I ran Jaws,
for which I have a licence obtained very cheaply in a sale. This so far has
meant a couple of major updates, but this evening not having run it for
some days, I did yet another update. All seemed to go well and I tested it
and saw no real difference. I then closed it and ran nvda.
What happened next was strange and I have now duplicated it three times.
Nvda could not read the menu you get when you go to shut down the pc with
alt/f4, it could not read the menus of Firefox and many other programs, nor
did it take single key entry to the desktop icons and say for example
Waterfox when I hit w.
The solution to this turned out to be control alt delete and on the
protected desktop picking cancel, whereupon everything was sweetness and
light.
I have to stress that before the Jaws update, nothing like this was the
case. Now I'm not saying that its a deliberate ploy to sabotage nvda, but it
does make me think that Jaws is not leaving windows as it found it, so
please beware. If this happens to you its not nvda playing up, just windows
left in a strange state by Jaws.
Note I am using Windows 7. I notice that Jaws has a major update for Skypes
cock ups, erm improvements sorry..
End of public service announcement.

Goodnight!

Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

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