|
Other tool for solving the Verification Image
I know this has been posted before but could not retrieve the email about the extension or addons for Firefox that is similar with webvism. I appreciate if you could share it again here some alternative option that I could use with on the Firefox ESR to solve the capture or verification image.
--
Robert Mendoza
|
|
|
Re: Registry fixing tool in nvda
How are you trying to update? Do you have a
newer version already on your computer?
While Window-eyes will be useful for a good while,
since there is no more Window-eyes, is it worth updating? Is there
anything you want in the final version? In other words, is the problem
worth solving since at some point, you'll have to switch screen-readers and if
there isn't anything you want in the last version, there will be no more
versions?
Gene
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Monday, March 12, 2018 4:32 PM
Subject: Re: [nvda] Registry fixing tool in nvda
Question from a long time
Window Eyes user. At present Windows can’t update to the latest version as it
thinks there is an incompatible program installed on my computer. That program
is Window Eyes. I have correctly uninstalled WE and have done multiple searches
to try and find remnants. My best guess is that it is lurking still in my
registry. I am not foolish enough to try editing my registry, and Leary of using
any of the “registry cleaners.” Any chance that this addon would find such a
lingering registry entry. When I read “other programs” I assume other access
software. I am not having the issues described in this thread, but. . .
.
Any advice out
there?
Rick
Dr. Rick Ely
TVI, Vision Consultant
451 Rocky Hill Road
Florence, MA
01062
&413() 727-3038
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On
Behalf Of Gene New Zealand
Sent: Monday, March 12, 2018 3:53
PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Registry
fixing tool in nvda
Hi
Just had a quick look is this a snapshot to fix the unknown and pane problems
that some people have had in the past? if it is and it works it would be far
easier than the other way which i have been posting from time to
time.
Gene nz
On 3/13/2018 12:10 AM, Brian's Mail list account via
Groups.Io wrote:
I know a number of people here
have had serious issues with browsers not reading word not working right with
nvda and other associated problems.
For some time now this has been known
to be due to registry issues due to uninstallers of other software not
correctly registering important files. The latest next snapshot has a tool to
fix this, rather predictably in its tool menu, so if you are having such
issues, it may well be a good idea to try this version of nvda and use the
tool.
it should do no harm, but do remember that next snaps are bleeding
edge code and will need to be used with caution. Always back up your previous
version and set a restore point before doing any work on registry files. Note
the account that its used on has to have admin access or it won't work.
Here is what the entry says.
commit
8793a65c7aa65949a9043aafc932627ff158c90a
Author: Michael Curran <mick@...>
Date: Thu 08
Mar 2018 09:41:04 +1000
Installer: re-register some common COM interfaces
which commonly get broken by bad uninstallers.
Raw diff
commit
d3a9795e75cdbe9241d11eecb9a98fbe774a17f7
Author: Michael Curran <mick@...>
Date: Mon 12
Mar 2018 12:06:37 +1000
COMRegistrationFixes tool: add a backslash to the
systemDrive. Also deremove some unused functions.
Raw diff
commit
3a5abd72a307fbe02779111dfee3bc5f5371345d
Author: Michael Curran <mick@...>
Date: Mon 12
Mar 2018 12:07:19 +1000
Add the COM Registrations Fixing tool to NVDA's
Tools menu.
Raw diff
commit e1d79784de5f0b77343992e61b1fb811a9dc826e
Author: Michael Curran <mick@...>
Date: Mon 12
Mar 2018 15:43:05 +1000
Add a warning dialog to the COM Registration
Fixing tool when run manually from the Tools menu.
Raw diff
commit
7c2e945533f7386b4b3142281e23009997f5d801
Author: Michael Curran <mick@...>
Date: Mon 12
Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit
877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mick@...>
Date: Mon 12
Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit
e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mick@...>
Date: Mon 12
Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff
------------------------------------------------------------------------------
Brian
bglists@...
Sent
via blueyonder.
Please address personal E-mail to:-
briang1@..., putting
'Brian Gaff'
in the display name field.
--
Check out my
website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net
Regardless of where you are in New Zealand if you are near one of the APNK sites
you can use a copy of the NVDA screen reader on one of their computers. To find
out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries
(Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you,
please visit the following link https://certification.nvaccess.org/.
The certification page contains the official list of NVDA certified individuals
from around the world, who have sat and successfully passed the NVDA expert
exam.
|
|
|
nvda dictation bridge and wsr corrections dialog
Hi If I am dictating with wsr, NVDA is not automatically speaking the corrections dialog if I go to correct some word that windows speech recognition misheard. Is this a dictation bridge bug? Sent from Mail for Windows 10
|
|
|
Re: Error while updating to NVDA 2018.1 via the NVDA update utility.
I actually prefur the linux rout, linux is more fairer than windows, in theory unless you exit the home directory you should be ok, by default windows likes to make programs etc system things.
And well you can make it your own but to be honest.
toggle quoted messageShow quoted text
On 13/03/2018 11:06 a.m., Kevin Cussick via Groups.Io wrote: agreed I just don't understand why people put there computers at risk.
On 12/03/2018 13:50, Devin Prater wrote:
This is a great message. Also, compare UAC to what Linux users have to do, typing in their whole root password when installing or updating programs sometimes. Compared to that, one keystroke is nothing.
"nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> on behalf of Gene" wrote:
It's a minimum amount of inconvenience to respond when the UAC prompt appears. All you have to do is use the alt y command. Why are people so casual about disabling a security feature that is minimally inconvenient? You issue one command. Compare that very minor inconvenience to what you may have to doo if you are infected because UAC is off. I realize that malware can circumvent UAC, and, from what I've been told, it isn't difficult. But still, what if you could have prevented nfection by having it on at a minimum of inconvenience?
Gene
----- Original Message -----
*From:*Dennis L<mailto:dennisl1982@gmail.com>
*Sent:*Sunday, March 11, 2018 10:52 PM
*To:*nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
*Subject:*Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.
this is why I turn off user account control.
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com<mailto:joseph.lee22590@gmail.com>>
To: <nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>>
Sent: Sunday, March 11, 2018 9:45 PM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update
utility.
Hi,
Yes, but this time, say "yes" when UAC (User Account Control) screen
appears.
Cheers,
Joseph
-----Original Message-----
From: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io><nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>> On Behalf Of Arianna
Sepulveda
Sent: Sunday, March 11, 2018 6:44 PM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: [nvda] Error while updating to NVDA 2018.1 via the NVDA update
utility.
Hello, All,
I just tried installing the NVDA 2018.1 update via the NVDA update utility,
and got the following error. I'm not sure what is relevant, so I just
coppied the entire output of the log viewer.
INFO - __main__ (18:37:12.331):
Starting NVDA
INFO - core.main (18:37:12.667):
Config dir: C:\Users\englishrider91\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:37:12.667):
Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:37:12.684):
NVDA version 2018.1
INFO - core.main (18:37:12.684):
Using Windows version 10.0.15063 workstation INFO - core.main
(18:37:12.684):
Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,
20:19:30) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:37:12.684):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (18:37:13.601):
Loaded synthDriver eloquence
INFO - core.main (18:37:13.601):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (18:37:13.601):
Braille input initialized
INFO - braille.initialize (18:37:13.601):
Using liblouis version 3.3.0
INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):
UIAutomation: IUIAutomation3
INFO - core.main (18:37:14.687):
NVDA initialized
ERROR - gui.installerGui.doInstall (18:37:46.061):
Failed to execute installer
Traceback (most recent call last):
File "gui\installerGui.pyo", line 32, in doInstall
File "config\__init__.pyo", line 192, in execElevated
File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by the user.
ERROR - gui.installerGui.doInstall (18:37:46.061):
Installation failed: [Error 1223] The operation was canceled by the user.
Should I try updating again?
Thanks,
Ari
|
|
|
Re: Registry fixing tool in nvda
what is this nvda reregistration tool?
That may actually be usefull for me to have.
toggle quoted messageShow quoted text
On 13/03/2018 10:36 a.m., Adriani Botez wrote: This registry tool in NVDA only registers the required dlls for the accessibility API to comunicate properly with NVDA. You will not be able to edit your registry with it.
You can use CCleaner for that purpose.
Best
Adriani
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von ely.r@comcast.net
Gesendet: Montag, 12. März 2018 22:33
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Registry fixing tool in nvda
Question from a long time Window Eyes user. At present Windows can’t update to the latest version as it thinks there is an incompatible program installed on my computer. That program is Window Eyes. I have correctly uninstalled WE and have done multiple searches to try and find remnants. My best guess is that it is lurking still in my registry. I am not foolish enough to try editing my registry, and Leary of using any of the “registry cleaners.” Any chance that this addon would find such a lingering registry entry. When I read “other programs” I assume other access software. I am not having the issues described in this thread, but. . . .
Any advice out there?
Rick
Dr. Rick Ely
TVI, Vision Consultant
451 Rocky Hill Road
Florence, MA 01062
&413() 727-3038
From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> > On Behalf Of Gene New Zealand
Sent: Monday, March 12, 2018 3:53 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Registry fixing tool in nvda
Hi
Just had a quick look is this a snapshot to fix the unknown and pane problems that some people have had in the past? if it is and it works it would be far easier than the other way which i have been posting from time to time.
Gene nz
On 3/13/2018 12:10 AM, Brian's Mail list account via Groups.Io wrote:
I know a number of people here have had serious issues with browsers not reading word not working right with nvda and other associated problems.
For some time now this has been known to be due to registry issues due to uninstallers of other software not correctly registering important files. The latest next snapshot has a tool to fix this, rather predictably in its tool menu, so if you are having such issues, it may well be a good idea to try this version of nvda and use the tool.
it should do no harm, but do remember that next snaps are bleeding edge code and will need to be used with caution. Always back up your previous version and set a restore point before doing any work on registry files. Note the account that its used on has to have admin access or it won't work.
Here is what the entry says.
commit 8793a65c7aa65949a9043aafc932627ff158c90a
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Thu 08 Mar 2018 09:41:04 +1000
Installer: re-register some common COM interfaces which commonly get broken by bad uninstallers.
Raw diff
commit d3a9795e75cdbe9241d11eecb9a98fbe774a17f7
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 12:06:37 +1000
COMRegistrationFixes tool: add a backslash to the systemDrive. Also deremove some unused functions.
Raw diff
commit 3a5abd72a307fbe02779111dfee3bc5f5371345d
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 12:07:19 +1000
Add the COM Registrations Fixing tool to NVDA's Tools menu.
Raw diff
commit e1d79784de5f0b77343992e61b1fb811a9dc826e
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 15:43:05 +1000
Add a warning dialog to the COM Registration Fixing tool when run manually from the Tools menu.
Raw diff
commit 7c2e945533f7386b4b3142281e23009997f5d801
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff
------------------------------------------------------------------------------
Brian
bglists@blueyonder.co.uk <mailto:bglists@blueyonder.co.uk>
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk <mailto:briang1@blueyonder.co.uk> , putting 'Brian Gaff'
in the display name field.
|
|
|
Re: Registry fixing tool in nvda
Well it depends on how long you have had the system active for how many installs of windows you have done on it.
For me on a workstation used for business and a few photo tasks as well as backup, its been active on a single install and upgrade from 7 since 2015.
The system has had layers removed layers added, etc.
So I am due to after getting it all backed up, and all the necessary things from it, just do a complete reformat on the request of its user who will be away for a week freeing the system at the end of the month for me to reformat, reconfigure and hopefully test to see if anything else is broken.
Right now there are layers of software and such for just about everything and the module set thus used is a lot smaller.
Previously there were 20-30 programs in addition to all everything else
Now there are round 8-10 programs, and the system has been running for 3-4 years and is due for a full reformat.
As well as this there are unused hardware packages, incompatible drivers and the like.
Depending how long things have remained, and with the issues registry cleaners can become its contrivertial, and now we have access to the windows installers, I wouldn't think twice about a reformat.
Ofcause I do have backups both on drives internal and external, cloud, software, etc.
You may not.
toggle quoted messageShow quoted text
On 13/03/2018 10:36 a.m., Adriani Botez wrote: This registry tool in NVDA only registers the required dlls for the accessibility API to comunicate properly with NVDA. You will not be able to edit your registry with it.
You can use CCleaner for that purpose.
Best
Adriani
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von ely.r@comcast.net
Gesendet: Montag, 12. März 2018 22:33
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Registry fixing tool in nvda
Question from a long time Window Eyes user. At present Windows can’t update to the latest version as it thinks there is an incompatible program installed on my computer. That program is Window Eyes. I have correctly uninstalled WE and have done multiple searches to try and find remnants. My best guess is that it is lurking still in my registry. I am not foolish enough to try editing my registry, and Leary of using any of the “registry cleaners.” Any chance that this addon would find such a lingering registry entry. When I read “other programs” I assume other access software. I am not having the issues described in this thread, but. . . .
Any advice out there?
Rick
Dr. Rick Ely
TVI, Vision Consultant
451 Rocky Hill Road
Florence, MA 01062
&413() 727-3038
From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> > On Behalf Of Gene New Zealand
Sent: Monday, March 12, 2018 3:53 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Registry fixing tool in nvda
Hi
Just had a quick look is this a snapshot to fix the unknown and pane problems that some people have had in the past? if it is and it works it would be far easier than the other way which i have been posting from time to time.
Gene nz
On 3/13/2018 12:10 AM, Brian's Mail list account via Groups.Io wrote:
I know a number of people here have had serious issues with browsers not reading word not working right with nvda and other associated problems.
For some time now this has been known to be due to registry issues due to uninstallers of other software not correctly registering important files. The latest next snapshot has a tool to fix this, rather predictably in its tool menu, so if you are having such issues, it may well be a good idea to try this version of nvda and use the tool.
it should do no harm, but do remember that next snaps are bleeding edge code and will need to be used with caution. Always back up your previous version and set a restore point before doing any work on registry files. Note the account that its used on has to have admin access or it won't work.
Here is what the entry says.
commit 8793a65c7aa65949a9043aafc932627ff158c90a
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Thu 08 Mar 2018 09:41:04 +1000
Installer: re-register some common COM interfaces which commonly get broken by bad uninstallers.
Raw diff
commit d3a9795e75cdbe9241d11eecb9a98fbe774a17f7
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 12:06:37 +1000
COMRegistrationFixes tool: add a backslash to the systemDrive. Also deremove some unused functions.
Raw diff
commit 3a5abd72a307fbe02779111dfee3bc5f5371345d
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 12:07:19 +1000
Add the COM Registrations Fixing tool to NVDA's Tools menu.
Raw diff
commit e1d79784de5f0b77343992e61b1fb811a9dc826e
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 15:43:05 +1000
Add a warning dialog to the COM Registration Fixing tool when run manually from the Tools menu.
Raw diff
commit 7c2e945533f7386b4b3142281e23009997f5d801
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mailto:mick@nvaccess.org> <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff
------------------------------------------------------------------------------
Brian
bglists@blueyonder.co.uk <mailto:bglists@blueyonder.co.uk>
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk <mailto:briang1@blueyonder.co.uk> , putting 'Brian Gaff'
in the display name field.
|
|
|
Add Custom Braille Commands
I want to be able to press hot keys like alt+tab and control+tab to cycle windows from my braille keyboard.
Does the facility for adding new commands exist within NVDA?
|
|
|
Re: Registry fixing tool in nvda
Gene New Zealand <hurrikennyandopo@...>
Hi
Will yesterdays snapshot be able to fix what is in the ticket below.
I asked Brian but because he is say 12 hours behind us I might not know for a while.
NVDA stops reading webpages in all browser - saying "unknown" or "pane" (#2807)
The above is the ticket number.
If this is the case i know of a person who has contacted me with the what is described in the ticket. I am sure also she is using windows 10 but could get more info from her if needed.
I am hoping the next snapshot where the tool is under the tools menu might fix the problem or am i wrong?
She needs a way to register those files that are broken where it says unknown or pane.
Gene nz
toggle quoted messageShow quoted text
On 3/13/2018 10:36 AM, Adriani Botez wrote:
This registry tool in NVDA only registers the required dlls for the accessibility API to comunicate properly with NVDA. You will not be able to edit your registry with
it.
You can use CCleaner for that purpose.
Best
Adriani
Question from a long time Window Eyes user. At present Windows can’t update to the latest version as it thinks there is an incompatible program installed on my computer. That program is Window
Eyes. I have correctly uninstalled WE and have done multiple searches to try and find remnants. My best guess is that it is lurking still in my registry. I am not foolish enough to try editing my registry, and Leary of using any of the “registry cleaners.”
Any chance that this addon would find such a lingering registry entry. When I read “other programs” I assume other access software. I am not having the issues described in this thread, but. . . .
Any advice out there?
Rick
Dr. Rick Ely
TVI, Vision Consultant
451 Rocky Hill Road
Florence, MA 01062
&413() 727-3038
Hi
Just had a quick look is this a snapshot to fix the unknown and pane problems that some people have had in the past? if it is and it works it would be far easier than the other way which i have been posting from time to time.
Gene nz
On 3/13/2018 12:10 AM, Brian's Mail list account via Groups.Io wrote:
I know a number of people here have had serious issues with browsers not reading word not working right with nvda and other associated problems.
For some time now this has been known to be due to registry issues due to uninstallers of other software not correctly registering important files. The latest next snapshot has a tool to fix this, rather predictably in its tool menu, so if you are having such
issues, it may well be a good idea to try this version of nvda and use the tool.
it should do no harm, but do remember that next snaps are bleeding edge code and will need to be used with caution. Always back up your previous version and set a restore point before doing any work on registry files. Note the account that its used on has to
have admin access or it won't work.
Here is what the entry says.
commit 8793a65c7aa65949a9043aafc932627ff158c90a
Author: Michael Curran
<mick@...>
Date: Thu 08 Mar 2018 09:41:04 +1000
Installer: re-register some common COM interfaces which commonly get broken by bad uninstallers.
Raw diff
commit d3a9795e75cdbe9241d11eecb9a98fbe774a17f7
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 12:06:37 +1000
COMRegistrationFixes tool: add a backslash to the systemDrive. Also deremove some unused functions.
Raw diff
commit 3a5abd72a307fbe02779111dfee3bc5f5371345d
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 12:07:19 +1000
Add the COM Registrations Fixing tool to NVDA's Tools menu.
Raw diff
commit e1d79784de5f0b77343992e61b1fb811a9dc826e
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 15:43:05 +1000
Add a warning dialog to the COM Registration Fixing tool when run manually from the Tools menu.
Raw diff
commit 7c2e945533f7386b4b3142281e23009997f5d801
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff
------------------------------------------------------------------------------
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
--
Check out my website for NVDA tutorials and other blindness related material at
http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers.
To find out which locations (or location) is near to you please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link
https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA
expert exam.
--
Check out my website for NVDA tutorials and other blindness related material at
http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers.
To find out which locations (or location) is near to you please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link
https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA
expert exam.
|
|
|
Re: Windows10 Mail and NVDA: several bugs reported
Have you opened the browser, then tried going to
Google? What happens?
Gene
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Monday, March 12, 2018 1:18 PM
Subject: Re: [nvda] Windows10 Mail and NVDA: several bugs
reported
Thank you very much for the reply.
Please, if you can, comment on future updates related to this bug.
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
***Note que a anterior mensaxe e/ou os seus adxuntos pode conter
información privada ou confidencial. O emprego da información desta mensaxe e/ou
dos seus adxuntos está reservado ao ámbito privado do destinatario agás
autorización do remitente. Se recibiu esta mensaxe por erro comuníqueo por esta
mesma vía e destrúa a mensaxe.***
O 12/03/2018 á(s) 15:32, Joseph Lee
escribiu:
Hi,
Looks like NVDA is told to use UIA directly. This is the case when
traditional means of fetching information from Word and its components won't
work (I need to better document this and others soon).
Cheers,
Joseph
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Monday, March 12, 2018 4:14 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows10 Mail and NVDA: several bugs reported
I'll ask the next question which build of windows 10 is it he is using? I'm
sure Joseph will ask otherwise!
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Iván Novegil via Groups.Io" <ivan.novegil@...>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 9:59 AM
Subject: [nvda] Windows10 Mail and NVDA: several bugs reported
Hello all.
A Spanish user asked us about the following two bugs he has with
Windows10's mail app.
-When opening a mail to read it, NVDA reports "page 1".
-When writing a message with word echo enabled and pressing space after
typing a word with accented letters or "ñ" on it NVDA doesn't report it.
Can someone try to reproduce these bugs to open an issue if needed? The
two ones happened after updating to 2018.1 and using either Eloquence or
eSpeakNG and with WinTenApps and without it.
Thanks in advance.
Regards.
|
|
|
Re: Error while updating to NVDA 2018.1 via the NVDA update utility.
agreed I just don't understand why people put there computers at risk.
toggle quoted messageShow quoted text
On 12/03/2018 13:50, Devin Prater wrote: This is a great message. Also, compare UAC to what Linux users have to do, typing in their whole root password when installing or updating programs sometimes. Compared to that, one keystroke is nothing.
"nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> on behalf of Gene" wrote:
It's a minimum amount of inconvenience to respond when the UAC prompt appears. All you have to do is use the alt y command. Why are people so casual about disabling a security feature that is minimally inconvenient? You issue one command. Compare that very minor inconvenience to what you may have to doo if you are infected because UAC is off. I realize that malware can circumvent UAC, and, from what I've been told, it isn't difficult. But still, what if you could have prevented nfection by having it on at a minimum of inconvenience?
Gene
----- Original Message -----
*From:*Dennis L<mailto:dennisl1982@gmail.com>
*Sent:*Sunday, March 11, 2018 10:52 PM
*To:*nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
*Subject:*Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.
this is why I turn off user account control.
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com<mailto:joseph.lee22590@gmail.com>>
To: <nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>>
Sent: Sunday, March 11, 2018 9:45 PM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update
utility.
Hi,
Yes, but this time, say "yes" when UAC (User Account Control) screen
appears.
Cheers,
Joseph
-----Original Message-----
From: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io><nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>> On Behalf Of Arianna
Sepulveda
Sent: Sunday, March 11, 2018 6:44 PM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: [nvda] Error while updating to NVDA 2018.1 via the NVDA update
utility.
Hello, All,
I just tried installing the NVDA 2018.1 update via the NVDA update utility,
and got the following error. I'm not sure what is relevant, so I just
coppied the entire output of the log viewer.
INFO - __main__ (18:37:12.331):
Starting NVDA
INFO - core.main (18:37:12.667):
Config dir: C:\Users\englishrider91\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:37:12.667):
Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:37:12.684):
NVDA version 2018.1
INFO - core.main (18:37:12.684):
Using Windows version 10.0.15063 workstation INFO - core.main
(18:37:12.684):
Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,
20:19:30) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:37:12.684):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (18:37:13.601):
Loaded synthDriver eloquence
INFO - core.main (18:37:13.601):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (18:37:13.601):
Braille input initialized
INFO - braille.initialize (18:37:13.601):
Using liblouis version 3.3.0
INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):
UIAutomation: IUIAutomation3
INFO - core.main (18:37:14.687):
NVDA initialized
ERROR - gui.installerGui.doInstall (18:37:46.061):
Failed to execute installer
Traceback (most recent call last):
File "gui\installerGui.pyo", line 32, in doInstall
File "config\__init__.pyo", line 192, in execElevated
File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by the user.
ERROR - gui.installerGui.doInstall (18:37:46.061):
Installation failed: [Error 1223] The operation was canceled by the user.
Should I try updating again?
Thanks,
Ari
|
|
|
Re: Registry fixing tool in nvda
Hi, Rick,
Maybe the microsoft disability disability center might be able to
help you.
Rosemarie
toggle quoted messageShow quoted text
Question
from a long time Window Eyes user. At present Windows can’t
update to the latest version as it thinks there is an
incompatible program installed on my computer. That program
is Window Eyes. I have correctly uninstalled WE and have
done multiple searches to try and find remnants. My best
guess is that it is lurking still in my registry. I am not
foolish enough to try editing my registry, and Leary of
using any of the “registry cleaners.” Any chance that this
addon would find such a lingering registry entry. When I
read “other programs” I assume other access software. I am
not having the issues described in this thread, but. . . .
Any advice
out there?
Rick
Dr. Rick
Ely
TVI,
Vision Consultant
451 Rocky
Hill Road
Florence,
MA 01062
&413()
727-3038
Hi
Just had a quick look is this a snapshot to fix the unknown
and pane problems that some people have had in the past? if it
is and it works it would be far easier than the other way
which i have been posting from time to time.
Gene nz
On 3/13/2018 12:10 AM, Brian's Mail list
account via Groups.Io wrote:
I know a
number of people here have had serious issues with browsers
not reading word not working right with nvda and other
associated problems.
For some time now this has been known to be due to registry
issues due to uninstallers of other software not correctly
registering important files. The latest next snapshot has a
tool to fix this, rather predictably in its tool menu, so if
you are having such issues, it may well be a good idea to
try this version of nvda and use the tool.
it should do no harm, but do remember that next snaps are
bleeding edge code and will need to be used with caution.
Always back up your previous version and set a restore point
before doing any work on registry files. Note the account
that its used on has to have admin access or it won't work.
Here is what the entry says.
commit 8793a65c7aa65949a9043aafc932627ff158c90a
Author: Michael Curran <mick@...>
Date: Thu 08 Mar 2018 09:41:04 +1000
Installer: re-register some common COM interfaces which
commonly get broken by bad uninstallers.
Raw diff
commit d3a9795e75cdbe9241d11eecb9a98fbe774a17f7
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 12:06:37 +1000
COMRegistrationFixes tool: add a backslash to the
systemDrive. Also deremove some unused functions.
Raw diff
commit 3a5abd72a307fbe02779111dfee3bc5f5371345d
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 12:07:19 +1000
Add the COM Registrations Fixing tool to NVDA's Tools menu.
Raw diff
commit e1d79784de5f0b77343992e61b1fb811a9dc826e
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 15:43:05 +1000
Add a warning dialog to the COM Registration Fixing tool
when run manually from the Tools menu.
Raw diff
commit 7c2e945533f7386b4b3142281e23009997f5d801
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff
------------------------------------------------------------------------------
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@...,
putting 'Brian Gaff'
in the display name field.
--
Check
out my website for NVDA tutorials and other blindness
related material at http://www.accessibilitycentral.net
Regardless of where you are in New Zealand if you are
near one of the APNK sites you can use a copy of the
NVDA screen reader on one of their computers. To find
out which locations (or location) is near to you please
visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries
(Aotearoa People's Network Kaharoa). To find an NVDA
certified expert near you, please visit the following
link https://certification.nvaccess.org/.
The certification page contains the official list of
NVDA certified individuals from around the world, who
have sat and successfully passed the NVDA expert exam.
|
|
|
Re: Registry fixing tool in nvda
This registry tool in NVDA only registers the required dlls for the accessibility API to comunicate properly with NVDA. You will not be able to edit your registry with it. You can use CCleaner for that purpose. Best Adriani Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von ely.r@...
Gesendet: Montag, 12. März 2018 22:33
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Registry fixing tool in nvda Question from a long time Window Eyes user. At present Windows can’t update to the latest version as it thinks there is an incompatible program installed on my computer. That program is Window Eyes. I have correctly uninstalled WE and have done multiple searches to try and find remnants. My best guess is that it is lurking still in my registry. I am not foolish enough to try editing my registry, and Leary of using any of the “registry cleaners.” Any chance that this addon would find such a lingering registry entry. When I read “other programs” I assume other access software. I am not having the issues described in this thread, but. . . . Any advice out there? Rick Dr. Rick Ely TVI, Vision Consultant 451 Rocky Hill Road Florence, MA 01062 &413() 727-3038
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene New Zealand
Sent: Monday, March 12, 2018 3:53 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Registry fixing tool in nvda Hi Just had a quick look is this a snapshot to fix the unknown and pane problems that some people have had in the past? if it is and it works it would be far easier than the other way which i have been posting from time to time. Gene nz On 3/13/2018 12:10 AM, Brian's Mail list account via Groups.Io wrote: I know a number of people here have had serious issues with browsers not reading word not working right with nvda and other associated problems.
For some time now this has been known to be due to registry issues due to uninstallers of other software not correctly registering important files. The latest next snapshot has a tool to fix this, rather predictably in its tool menu, so if you are having such issues, it may well be a good idea to try this version of nvda and use the tool.
it should do no harm, but do remember that next snaps are bleeding edge code and will need to be used with caution. Always back up your previous version and set a restore point before doing any work on registry files. Note the account that its used on has to have admin access or it won't work.
Here is what the entry says.
commit 8793a65c7aa65949a9043aafc932627ff158c90a
Author: Michael Curran <mick@...>
Date: Thu 08 Mar 2018 09:41:04 +1000
Installer: re-register some common COM interfaces which commonly get broken by bad uninstallers.
Raw diff
commit d3a9795e75cdbe9241d11eecb9a98fbe774a17f7
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 12:06:37 +1000
COMRegistrationFixes tool: add a backslash to the systemDrive. Also deremove some unused functions.
Raw diff
commit 3a5abd72a307fbe02779111dfee3bc5f5371345d
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 12:07:19 +1000
Add the COM Registrations Fixing tool to NVDA's Tools menu.
Raw diff
commit e1d79784de5f0b77343992e61b1fb811a9dc826e
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 15:43:05 +1000
Add a warning dialog to the COM Registration Fixing tool when run manually from the Tools menu.
Raw diff
commit 7c2e945533f7386b4b3142281e23009997f5d801
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff
------------------------------------------------------------------------------
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
--
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.
|
|
|
Re: Registry fixing tool in nvda
Question from a long time Window Eyes user. At present Windows can’t update to the latest version as it thinks there is an incompatible program installed on my computer. That program is Window Eyes. I have correctly uninstalled WE and have done multiple searches to try and find remnants. My best guess is that it is lurking still in my registry. I am not foolish enough to try editing my registry, and Leary of using any of the “registry cleaners.” Any chance that this addon would find such a lingering registry entry. When I read “other programs” I assume other access software. I am not having the issues described in this thread, but. . . . Any advice out there? Rick Dr. Rick Ely TVI, Vision Consultant 451 Rocky Hill Road Florence, MA 01062 &413() 727-3038
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene New Zealand
Sent: Monday, March 12, 2018 3:53 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Registry fixing tool in nvda Hi Just had a quick look is this a snapshot to fix the unknown and pane problems that some people have had in the past? if it is and it works it would be far easier than the other way which i have been posting from time to time. Gene nz On 3/13/2018 12:10 AM, Brian's Mail list account via Groups.Io wrote: I know a number of people here have had serious issues with browsers not reading word not working right with nvda and other associated problems.
For some time now this has been known to be due to registry issues due to uninstallers of other software not correctly registering important files. The latest next snapshot has a tool to fix this, rather predictably in its tool menu, so if you are having such issues, it may well be a good idea to try this version of nvda and use the tool.
it should do no harm, but do remember that next snaps are bleeding edge code and will need to be used with caution. Always back up your previous version and set a restore point before doing any work on registry files. Note the account that its used on has to have admin access or it won't work.
Here is what the entry says.
commit 8793a65c7aa65949a9043aafc932627ff158c90a
Author: Michael Curran <mick@...>
Date: Thu 08 Mar 2018 09:41:04 +1000
Installer: re-register some common COM interfaces which commonly get broken by bad uninstallers.
Raw diff
commit d3a9795e75cdbe9241d11eecb9a98fbe774a17f7
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 12:06:37 +1000
COMRegistrationFixes tool: add a backslash to the systemDrive. Also deremove some unused functions.
Raw diff
commit 3a5abd72a307fbe02779111dfee3bc5f5371345d
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 12:07:19 +1000
Add the COM Registrations Fixing tool to NVDA's Tools menu.
Raw diff
commit e1d79784de5f0b77343992e61b1fb811a9dc826e
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 15:43:05 +1000
Add a warning dialog to the COM Registration Fixing tool when run manually from the Tools menu.
Raw diff
commit 7c2e945533f7386b4b3142281e23009997f5d801
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff
------------------------------------------------------------------------------
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
--
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.
|
|
|
Re: Registry fixing tool in nvda
Gene New Zealand <hurrikennyandopo@...>
Hi
Just had a quick look is this a snapshot to fix the unknown and pane problems that some people have had in the past? if it is and it works it would be far easier than the other way which i have been posting from time to time.
Gene nz
toggle quoted messageShow quoted text
On 3/13/2018 12:10 AM, Brian's Mail list account via Groups.Io wrote:
I know a number of people here have had serious issues with browsers not reading word not working right with nvda and other associated problems.
For some time now this has been known to be due to registry issues due to uninstallers of other software not correctly registering important files. The latest next snapshot has a tool to fix this, rather predictably in its tool menu, so if you are having such
issues, it may well be a good idea to try this version of nvda and use the tool.
it should do no harm, but do remember that next snaps are bleeding edge code and will need to be used with caution. Always back up your previous version and set a restore point before doing any work on registry files. Note the account that its used on has to
have admin access or it won't work.
Here is what the entry says.
commit 8793a65c7aa65949a9043aafc932627ff158c90a
Author: Michael Curran
<mick@...>
Date: Thu 08 Mar 2018 09:41:04 +1000
Installer: re-register some common COM interfaces which commonly get broken by bad uninstallers.
Raw diff
commit d3a9795e75cdbe9241d11eecb9a98fbe774a17f7
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 12:06:37 +1000
COMRegistrationFixes tool: add a backslash to the systemDrive. Also deremove some unused functions.
Raw diff
commit 3a5abd72a307fbe02779111dfee3bc5f5371345d
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 12:07:19 +1000
Add the COM Registrations Fixing tool to NVDA's Tools menu.
Raw diff
commit e1d79784de5f0b77343992e61b1fb811a9dc826e
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 15:43:05 +1000
Add a warning dialog to the COM Registration Fixing tool when run manually from the Tools menu.
Raw diff
commit 7c2e945533f7386b4b3142281e23009997f5d801
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran
<mick@...>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff
------------------------------------------------------------------------------
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
--
Check out my website for NVDA tutorials and other blindness related material at
http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers.
To find out which locations (or location) is near to you please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link
https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA
expert exam.
|
|
|
Re: NVDA chasing Outlook 365
First off, I don’t know why crashing in the above subject got changed to “chasing” but in any case, I was able to get a debug log but it tells little more to me.
Essentially when control-two is typed which should switch the main Outlook view from what it is to the Calendar view, both NVDA and Outlook become unresponsive. It looks like NVDA pretty much just dies at
the control-2 if I am reading the below portion of the log correctly.
…
IO - speech.speak (15:14:29.400):
Speaking [LangChangeCommand ('en_GB'), u'unread From Iv\xe1n Novegil via Groups.Io, Subject Re: [nvda] Windows10 Mail and NVDA: several bugs reported, Received Mon 3/12/2018
2:21 PM, Size 86 KB,']
IO - inputCore.InputManager.executeGesture (15:14:35.358):
Input: kb(desktop):control+2
DEBUGWARNING - watchdog._watcher (15:14:37.355):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 212, in <module>
File "core.pyo", line 473, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 443, in Notify
File "IAccessibleHandler.pyo", line 894, in pumpAll
File "IAccessibleHandler.pyo", line 617, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 327, in isUIAWindow
File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper
WARNING - watchdog._watcher (15:14:52.367):
Core frozen in stack:
File "nvda.pyw", line 212, in <module>
…
From: <nvda@nvda.groups.io> on behalf of "Cohn, Jonathan" <jcohn@...>
Reply-To: "nvda@nvda.groups.io" <nvda@nvda.groups.io>
Date: Friday, March 9, 2018 at 5:25 PM
To: "nvda@nvda.groups.io" <nvda@nvda.groups.io>
Subject: [nvda] NVDA chasing Outlook 365
Hello,
I have recreated this situation but not done any debugging.
NVDA 2018.1
Outlook 365
Windows 7 enterprise
- Open Outlook.
- Open a message and read it with numpad-+
Switch back to Inbox listing with alt-tab
Switch to calendar tab with control-2
At this point Outlook stops responding. I won’t be able to look at this further today, but besides simplifying down to not opening a message, what other actions
do I need to do before submitting a ticket?
How do I turn on debug log as I know that will be useful. Are additional details about versions required?
Thanks,
Jonathan Cohn
American Institutes for Research – Assessments
Web Accessibility specialist
|
|
|
Re: Windows10 Mail and NVDA: several bugs reported
Thank you very much for the reply.
Please, if you can, comment on future updates related to this
bug.
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
***Note que a anterior mensaxe e/ou os seus adxuntos pode
conter información privada ou confidencial. O emprego da
información desta mensaxe e/ou dos seus adxuntos está
reservado ao ámbito privado do destinatario agás autorización
do remitente. Se recibiu esta mensaxe por erro comuníqueo por
esta mesma vía e destrúa a mensaxe.***
O 12/03/2018 á(s) 15:32, Joseph Lee
escribiu:
toggle quoted messageShow quoted text
Hi,
Looks like NVDA is told to use UIA directly. This is the case when
traditional means of fetching information from Word and its components won't
work (I need to better document this and others soon).
Cheers,
Joseph
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Monday, March 12, 2018 4:14 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows10 Mail and NVDA: several bugs reported
I'll ask the next question which build of windows 10 is it he is using? I'm
sure Joseph will ask otherwise!
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Iván Novegil via Groups.Io" <ivan.novegil@...>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 9:59 AM
Subject: [nvda] Windows10 Mail and NVDA: several bugs reported
Hello all.
A Spanish user asked us about the following two bugs he has with
Windows10's mail app.
-When opening a mail to read it, NVDA reports "page 1".
-When writing a message with word echo enabled and pressing space after
typing a word with accented letters or "ñ" on it NVDA doesn't report it.
Can someone try to reproduce these bugs to open an issue if needed? The
two ones happened after updating to 2018.1 and using either Eloquence or
eSpeakNG and with WinTenApps and without it.
Thanks in advance.
Regards.
|
|
|
Re: Windows10 Mail and NVDA: several bugs reported
He's using 16299.125.
A little correction: it doesn't happen with ñ as I've said, only
with accents.
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
***Note que a anterior mensaxe e/ou os seus adxuntos pode
conter información privada ou confidencial. O emprego da
información desta mensaxe e/ou dos seus adxuntos está
reservado ao ámbito privado do destinatario agás autorización
do remitente. Se recibiu esta mensaxe por erro comuníqueo por
esta mesma vía e destrúa a mensaxe.***
O 12/03/2018 á(s) 12:14, Brian's Mail
list account via Groups.Io escribiu:
toggle quoted messageShow quoted text
I'll
ask the next question which build of windows 10 is it he is using?
I'm sure Joseph will ask otherwise!
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Iván Novegil via Groups.Io"
<ivan.novegil@...>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 9:59 AM
Subject: [nvda] Windows10 Mail and NVDA: several bugs reported
Hello all.
A Spanish user asked us about the following two bugs he has with
Windows10's mail app.
-When opening a mail to read it, NVDA reports "page 1".
-When writing a message with word echo enabled and pressing space
after
typing a word with accented letters or "ñ" on it NVDA doesn't
report it.
Can someone try to reproduce these bugs to open an issue if
needed? The
two ones happened after updating to 2018.1 and using either
Eloquence or
eSpeakNG and with WinTenApps and without it.
Thanks in advance.
Regards.
|
|
|
Re: Registry fixing tool in nvda
Brian's Mail list account <bglists@...>
I should just add that as this patch runs at start up, it should be enough to fix it by merely running the snapshot. Otherwise you can run it from the menu if you have maybe uninstalled something while it was running, nvda that is.
I think I'll quit before I confuse myself!
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.
toggle quoted messageShow quoted text
----- Original Message ----- From: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io> To: <nvda@nvda.groups.io> Sent: Monday, March 12, 2018 11:10 AM Subject: [nvda] Registry fixing tool in nvda I know a number of people here have had serious issues with browsers not reading word not working right with nvda and other associated problems.
For some time now this has been known to be due to registry issues due to uninstallers of other software not correctly registering important files. The latest next snapshot has a tool to fix this, rather predictably in its tool menu, so if you are having such issues, it may well be a good idea to try this version of nvda and use the tool.
it should do no harm, but do remember that next snaps are bleeding edge code and will need to be used with caution. Always back up your previous version and set a restore point before doing any work on registry files. Note the account that its used on has to have admin access or it won't work.
Here is what the entry says.
commit 8793a65c7aa65949a9043aafc932627ff158c90a
Author: Michael Curran <mick@nvaccess.org>
Date: Thu 08 Mar 2018 09:41:04 +1000
Installer: re-register some common COM interfaces which commonly get broken by bad uninstallers.
Raw diff
commit d3a9795e75cdbe9241d11eecb9a98fbe774a17f7
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 12:06:37 +1000
COMRegistrationFixes tool: add a backslash to the systemDrive. Also deremove some unused functions.
Raw diff
commit 3a5abd72a307fbe02779111dfee3bc5f5371345d
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 12:07:19 +1000
Add the COM Registrations Fixing tool to NVDA's Tools menu.
Raw diff
commit e1d79784de5f0b77343992e61b1fb811a9dc826e
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 15:43:05 +1000
Add a warning dialog to the COM Registration Fixing tool when run manually from the Tools menu.
Raw diff
commit 7c2e945533f7386b4b3142281e23009997f5d801
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff
------------------------------------------------------------------------------
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.
|
|
|
Re: Please Clarify NVDA 2018?
Brian's Mail list account <bglists@...>
I still regualarly see Windows 7 with registrations available on bona fide sites and vendors so I'd guess there is still some call for them out there.
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.
toggle quoted messageShow quoted text
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 3:00 PM
Subject: Re: [nvda] Please Clarify NVDA 2018?
Hi,
NVDA 2017.4 and later requires Windows 7 SP1 or higher. As for getting Windows 10 in an affordable way, the “most affordable” way is no more unless that program comes back.
Cheers,
Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Monday, March 12, 2018 7:59 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Please Clarify NVDA 2018?
The latest versions don't support XP. They work with Windows 7 and higher. I don't know about Vista. If you are using XP, you have to use the last version that supports XP if you want the latest version you can use. That is, I believe, version 17.4.
Gene
----- Original Message -----
From: David Russell <mailto:david.sonofhashem@gmail.com>
Sent: Monday, March 12, 2018 9:47 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: [nvda] Please Clarify NVDA 2018?
Hello Group members,
Two questions which "should" be simple enough to answer.
- Does NVDA 2018 only work with computers and devices compatible with
Windows Ten?
- If NVDA works only with newer windows versions, is there an online
resource that will distribute Windows Ten or other said product, and
help install at a reduced cost to blind users?
--
David Russell
david.sonofhashem@gmail.com <mailto:david.sonofhashem@gmail.com>
"chilah phanim" Make G-d smile!
|
|
|
Re: Please Clarify NVDA 2018?
Brian's Mail list account <bglists@...>
2017.3 is your last xp/vista version. its all down to routines available in the kernal of windows really.
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.
toggle quoted messageShow quoted text
----- Original Message -----
From: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 2:59 PM
Subject: Re: [nvda] Please Clarify NVDA 2018?
The latest versions don't support XP. They work with Windows 7 and higher. I don't know about Vista. If you are using XP, you have to use the last version that supports XP if you want the latest version you can use. That is, I believe, version 17.4.
Gene
----- Original Message -----
From: David Russell
Sent: Monday, March 12, 2018 9:47 AM
To: nvda@nvda.groups.io
Subject: [nvda] Please Clarify NVDA 2018?
Hello Group members,
Two questions which "should" be simple enough to answer.
- Does NVDA 2018 only work with computers and devices compatible with
Windows Ten?
- If NVDA works only with newer windows versions, is there an online
resource that will distribute Windows Ten or other said product, and
help install at a reduced cost to blind users?
--
David Russell
david.sonofhashem@gmail.com
"chilah phanim" Make G-d smile!
|
|
|
