Date   
Re: Excel: Three Small Fixes

James Scholes
 

On 16/08/2019 at 10:03 pm, Ralf Kefferpuetz wrote:
Your first ask is a long going thread on github, I prefer an option to give us the option what is spoken first, the cell coordinates or the cell content.
This isn't what the original poster is asking for. They want to change the order in which column/row headers are spoken, relative to the overall speaking of the cell itself.

Regards,

James Scholes

On 16/08/2019 at 10:03 pm, Ralf Kefferpuetz wrote:
Your first ask is a long going thread on github, I prefer an option to give us the option what is spoken first, the cell coordinates or the cell content. My personal optinion is that the cell coordinates should be spoken before the cell content….but this opinion differs 😊
*From:*nvda-devel@groups.io <nvda-devel@groups.io> *On Behalf Of *Jim Homme
*Sent:* Freitag, 16. August 2019 20:45
*To:* nvda-devel@groups.io
*Subject:* [nvda-devel] Excel: Three Small Fixes
Hi,
Would this be something too small for an add-on? I’m wishing for three things to happen in Excel and thinking of attempting to change them. I’m unsure if I can do this based on my Python knowledge, but I’m annoyed enough to try.
First: In Excel, if I move, I want NVDA to say column headers and row headers first, not last.
Second, if I choose something in an in-cell dropdown, the description property and the name property in the log always has the exact same information. Even though I consider this a Microsoft issue, I still wish it only spoke once. I want to make NVDA ignore the description, but do not want to turn that setting off. I created a profile that does this to get around the problem.
Third, in the VBA editor, F8 steps through code and moves the cursor to the next line. I would like NVDA to figure out that I am in the VBA editor and say the line after I press F8.
Thanks.
Jim
==========
Jim Homme
Digital Accessibility
Bender Consulting Services
412-787-8567
https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions

Re: Excel: Three Small Fixes

Bill Dengler
 

As for your second and third requests, they should be possible:
2. Figure out how to identify the control and create a CUSTOM NVDA class. Set the description property to the empty string.
3. Bind f8 to a custom script in VBA editor.

Bill

On 16 Aug 2019, at 14:45, Jim Homme <jhomme@...> wrote:

Hi,
Would this be something too small for an add-on? I’m wishing for three things to happen in Excel and thinking of attempting to change them. I’m unsure if I can do this based on my Python knowledge, but I’m annoyed enough to try.
 
First: In Excel, if I move, I want NVDA to say column headers and row headers first, not last.
Second, if I choose something in an in-cell dropdown, the description property and the name property in the log always has the exact same information. Even though I consider this a Microsoft issue, I still wish it only spoke once. I want to make NVDA ignore the description, but do not want to turn that setting off. I created a profile that does this to get around the problem.
Third, in the VBA editor, F8 steps through code and moves the cursor to the next line. I would like NVDA to figure out that I am in the VBA editor and say the line after I press F8.
 
 
Thanks.
 
 
Jim
 
 
 
==========
Jim Homme
Digital Accessibility 
Bender Consulting Services
412-787-8567
 

Re: Excel: Three Small Fixes

Luke Davis
 

On Sat, 17 Aug 2019, James Scholes wrote:

On 16/08/2019 at 10:03 pm, Ralf Kefferpuetz wrote:
Your first ask is a long going thread on github, I prefer an option to give us the option what is spoken first, the cell coordinates or the cell content.
This isn't what the original poster is asking for. They want to change the order in which column/row headers are spoken, relative to the overall speaking of the cell itself.
Interesting. I read that the OP said row and column headers too, but in my mind immediately translated that to cell coordinates and continued reading on that basis. In other words, I understood it the same as Ralf did.

Given your more precise reading, that raises a question.

In Excel? even with row and column header announcements turned on, the row/column headers aren't spoken at all. It isn't even clear how NVDA would know what the column and row headers are.
In fact I can't figure out a way to make it speak headers even if I try.

It does, however, speak cell coordinates.

This is why my original understanding of the message went to coordinates out of the box.

So, how exactly does one get NVDA to announce column and row headers in Excel in the first place, so I can then decide whether I like them spoken first or last?

Luke

Re: Excel: Three Small Fixes

Luke Davis
 

On Fri, 16 Aug 2019, Luke Davis wrote:

In Excel? even with row and column header announcements turned on, the row/column headers aren't spoken at all. It isn't even clear how NVDA would know what the column and row headers are.
I take that back, I see how it is done.

Re: Excel: Three Small Fixes

Luke Davis
 

On Fri, 16 Aug 2019, Jim Homme wrote:

Would this be something too small for an add-on? I’m wishing for three things to happen in Excel and thinking of attempting to change them. I’m unsure if I
can do this based on my Python knowledge, but I’m annoyed enough to try.
To answer your original question: personally, I don't know why those things shouldn't be done in an add-on.

Thing one, the order of header vs. cell contents, should hopefully make it into core at some point. But that may not happen quickly enough if you just set out to make it a PR against core.

After you've addressed your particular troublesome issues, you might also consider, for some future version of your add-on, addressing one of the other Excel annoyances out there: switching worksheets, and viewing the worksheet list, via F6. This can only be done currently via NVDA+F7, alt+f, arrow to sheets, tab to the list. However a single press of F6, is the intended (by Microsoft) keyboard shortcut for accessing that list.

See a discussion about it here: https://nvda.groups.io/g/nvda/topic/moving_between_worksheets_in/31955276?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,31955276

Luke

Formatting information script

Andy B.
 

Hi,

 

I am developing an add-on that requests the formatting information of the currently focused item. Right now, NVDA requests a textInfos object from the current review position. However, my add-on sets focus on objects that has a focusable flag set to False. HTML5 div and section elements are good examples. They cannot gain focus, but I force NVDA to set focus to those elements anyways. A strange problem is that objects that NVDA cannot naturally navigate to does not have a review position. This means my add-on must implement its own formatting retrieval system, defeating the entire purpose of reusable code. If NVDA is going to implement a setFocusObject method, then it should allow users to tell NVDA what object to get formatting information from… If one is not provided, use the current review position. Until something is done, my add-on is stuck because I do not see the point in rewriting what is already provided in NVDA core.

 

 

 

 

 

Sent from Mail for Windows 10

 

Is there a try build of the fix for crashing windows Explorer?

Brian's Mail list account
 

If so I'd like to test it on a machine I'm looking after which suffers from this when used with mouse in windows7 home premium.
Is it python 2 or 3?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Re: Is there a try build of the fix for crashing windows Explorer?

Bill Dengler
 

https://ci.appveyor.com/api/buildjobs/kc0a38ugwnoiyhhq/artifacts/output%2Fnvda_snapshot_try-explorerCrash-18422%2C9d9323fb.exe

Bill
On 18/08/2019, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
If so I'd like to test it on a machine I'm looking after which suffers from

this when used with mouse in windows7 home premium.
Is it python 2 or 3?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users




Add-on Updater 19.08.2 #addonrelease

 

Hi all,

 

Add-on Updater 19.08.2 is now available. This version resolves key error seen when trying to look for updates for certain add-ons, along with fixing localizations for Arabic and Ukrainian.

 

Note: Add-on Updater 19.09 is coming soon, and that version will require NVDA 2019.2 or later.

Cheers,

Joseph

Re: Is there a try build of the fix for crashing windows Explorer?

Brian's Mail list account
 

Thanks, May well shove this in and test it later in the week.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Bill Dengler" <codeofdusk@...>
To: <nvda-devel@groups.io>
Sent: Sunday, August 18, 2019 5:18 PM
Subject: Re: [nvda-devel] Is there a try build of the fix for crashing windows Explorer?


https://ci.appveyor.com/api/buildjobs/kc0a38ugwnoiyhhq/artifacts/output%2Fnvda_snapshot_try-explorerCrash-18422%2C9d9323fb.exe

Bill
On 18/08/2019, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
If so I'd like to test it on a machine I'm looking after which suffers from

this when used with mouse in windows7 home premium.
Is it python 2 or 3?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users




Re: Add-on Updater 19.08.2 #addonrelease

Brian's Mail list account
 

So will this version if installed in 2019.1.x stop it being installed?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Sunday, August 18, 2019 6:41 PM
Subject: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease


Hi all,



Add-on Updater 19.08.2 is now available. This version resolves key error
seen when trying to look for updates for certain add-ons, along with fixing
localizations for Arabic and Ukrainian.



Note: Add-on Updater 19.09 is coming soon, and that version will require
NVDA 2019.2 or later.

Cheers,

Joseph



Re: Add-on Updater 19.08.2 #addonrelease

 

Hi,
Eh?
19.08.2 is still compatible with 2019.1... and most likely the last one to
be compatible with it.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Sunday, August 18, 2019 11:44 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease

So will this version if installed in 2019.1.x stop it being installed?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Sunday, August 18, 2019 6:41 PM
Subject: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease


Hi all,



Add-on Updater 19.08.2 is now available. This version resolves key error
seen when trying to look for updates for certain add-ons, along with
fixing
localizations for Arabic and Ukrainian.



Note: Add-on Updater 19.09 is coming soon, and that version will require
NVDA 2019.2 or later.

Cheers,

Joseph




Re: Add-on Updater 19.08.2 #addonrelease

Brian's Mail list account
 

OK more explanation required. When you put out the next one which will require the current stable release, will something in this release stop it from being installed on 2019.1.1.
IE if you accidentally install the next version on the older version of nvda what will happen?

Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Sunday, August 18, 2019 7:45 PM
Subject: Re: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease


Hi,
Eh?
19.08.2 is still compatible with 2019.1... and most likely the last one to
be compatible with it.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Sunday, August 18, 2019 11:44 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease

So will this version if installed in 2019.1.x stop it being installed?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Sunday, August 18, 2019 6:41 PM
Subject: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease


Hi all,



Add-on Updater 19.08.2 is now available. This version resolves key error
seen when trying to look for updates for certain add-ons, along with
fixing
localizations for Arabic and Ukrainian.



Note: Add-on Updater 19.09 is coming soon, and that version will require
NVDA 2019.2 or later.

Cheers,

Joseph








Re: Is there a try build of the fix for crashing windows Explorer?

Brian's Mail list account
 

OK I see its based on Python 3 then, which is a little awkward, since this means importing new versions of add ons as well to the other machine and there are other possible issues.
For example it has no update of addons, if you enable add on updater you get an error. Also the log has weird stuff in it....

Are any of these anything to worry about?

WARNING - baseObject.Getter.__init__ (20:09:30.331):
Abstract class properties are not supported.

snip
DEBUG - core.main (20:09:30.558):
Initializing vision
Don't know this one....

DEBUG - core.main (20:09:30.558):
Initializing displayModel
DEBUG - core.main (20:09:30.559):
Initializing GUI
DEBUG - windowUtils._rawWindowProc (20:09:30.566):
CustomWindow rawWindowProc called for unknown window 852974
DEBUG - windowUtils._rawWindowProc (20:09:30.566):
CustomWindow rawWindowProc called for unknown window 852974
DEBUG - windowUtils._rawWindowProc (20:09:30.566):
CustomWindow rawWindowProc called for unknown window 852974
DEBUG - windowUtils._rawWindowProc (20:09:30.567):
CustomWindow rawWindowProc called for unknown window 852974
DEBUG - core.main (20:09:30.569):

snip


During startup. I do have the same add ons installed as I do with alpha snaps.
I note that no add on or nvda updates supported by try builds, so have disabled add on updater as it was generating errors

Brian


bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Bill Dengler" <codeofdusk@...>
To: <nvda-devel@groups.io>
Sent: Sunday, August 18, 2019 5:18 PM
Subject: Re: [nvda-devel] Is there a try build of the fix for crashing windows Explorer?


https://ci.appveyor.com/api/buildjobs/kc0a38ugwnoiyhhq/artifacts/output%2Fnvda_snapshot_try-explorerCrash-18422%2C9d9323fb.exe

Bill
On 18/08/2019, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
If so I'd like to test it on a machine I'm looking after which suffers from

this when used with mouse in windows7 home premium.
Is it python 2 or 3?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users




Re: Add-on Updater 19.08.2 #addonrelease

 

Hi,
Depends on NVDA version in use. If using versions earlier than 2019.1, it'll
install, although the add-on itself won't work properly. The absolute
minimum version the add-on requires is 2019.1 because the add-on will use
concepts provided by 2019.1 to check for compatibility range.
All of this changes later this year: as I noted a few times, once NVDA
2019.3 comes out, Add-on Updater will require 2019.3 because of extensive
use of Python 3 syntax. However, that switch won't occur as soon as 2019.3
comes out - I'll wait a few weeks before releasing a version of Add-on
Updater that will require 2019.3. Once that happens, there is no going back
- you won't be able to install the future Add-on updater release on an older
NVDA release, nor old add-on releases will work on NVDA 2019.3 and later.
Even if you do fool NVDA by "installing" it by copying add-on files, Add-on
Updater will fail to operate properly if what it expects and current NVDA
version do not match.
This isn't limited to Add-on Updater - any add-on that wishes to see light
of day once NVDA 2019.3 ships must be willing to not only declare its
support for 2019.3 in the manifest, source code must also be compliant. This
is the biggest reason why not all add-ons declaring Python 3 compatibility
will not be certified as such until source code is compliant (and for some,
they must be ready to deal with deeper differences between python 2 and 3,
which is perhaps one of the reasons for current difficulty with porting some
speech synthesizer add-ons).
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Sunday, August 18, 2019 12:27 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease

OK more explanation required. When you put out the next one which will
require the current stable release, will something in this release stop it
from being installed on 2019.1.1.
IE if you accidentally install the next version on the older version of
nvda what will happen?

Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Sunday, August 18, 2019 7:45 PM
Subject: Re: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease


Hi,
Eh?
19.08.2 is still compatible with 2019.1... and most likely the last one to
be compatible with it.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's
Mail
list account via Groups.Io
Sent: Sunday, August 18, 2019 11:44 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease

So will this version if installed in 2019.1.x stop it being installed?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Sunday, August 18, 2019 6:41 PM
Subject: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease


Hi all,



Add-on Updater 19.08.2 is now available. This version resolves key error
seen when trying to look for updates for certain add-ons, along with
fixing
localizations for Arabic and Ukrainian.



Note: Add-on Updater 19.09 is coming soon, and that version will require
NVDA 2019.2 or later.

Cheers,

Joseph









Re: Add-on Updater 19.08.2 #addonrelease

Brian's Mail list account
 

OK that makes sense. One assumes though that anyone still on an old version of nvda after that time if they avoid the latest version of updater, and indeed may wish not to have updater installed at all, can still download add ons that were for the older versions from somewhere, or maybe they will carry a flag on the web sit that shows which are for which version to avoid disappointment when downloading them.


Also, does this also mean that addons that still work now in Python three will continue to do so, or are there likely to be changes in nvda before then that might throw the odd spanner in already adapted code, such as Resource checker?


Yes some work would be needed to get pico to work as It seems its not just python 3, but the way sound is handled generally that mucks that one up.
I did also notice that in the try build to stop Explorer crashing with the mouse that Sapi 4 although it works does crash nvda at random times or if you attempt to switch it back to another synth. Not looked into that, as after all that is a try build and may contain other experimental code as I do not know what build of Alpha its based on.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Sunday, August 18, 2019 8:49 PM
Subject: Re: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease


Hi,
Depends on NVDA version in use. If using versions earlier than 2019.1, it'll
install, although the add-on itself won't work properly. The absolute
minimum version the add-on requires is 2019.1 because the add-on will use
concepts provided by 2019.1 to check for compatibility range.
All of this changes later this year: as I noted a few times, once NVDA
2019.3 comes out, Add-on Updater will require 2019.3 because of extensive
use of Python 3 syntax. However, that switch won't occur as soon as 2019.3
comes out - I'll wait a few weeks before releasing a version of Add-on
Updater that will require 2019.3. Once that happens, there is no going back
- you won't be able to install the future Add-on updater release on an older
NVDA release, nor old add-on releases will work on NVDA 2019.3 and later.
Even if you do fool NVDA by "installing" it by copying add-on files, Add-on
Updater will fail to operate properly if what it expects and current NVDA
version do not match.
This isn't limited to Add-on Updater - any add-on that wishes to see light
of day once NVDA 2019.3 ships must be willing to not only declare its
support for 2019.3 in the manifest, source code must also be compliant. This
is the biggest reason why not all add-ons declaring Python 3 compatibility
will not be certified as such until source code is compliant (and for some,
they must be ready to deal with deeper differences between python 2 and 3,
which is perhaps one of the reasons for current difficulty with porting some
speech synthesizer add-ons).
Cheers,
Joseph


-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Sunday, August 18, 2019 12:27 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease

OK more explanation required. When you put out the next one which will
require the current stable release, will something in this release stop it
from being installed on 2019.1.1.
IE if you accidentally install the next version on the older version of
nvda what will happen?

Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Sunday, August 18, 2019 7:45 PM
Subject: Re: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease


Hi,
Eh?
19.08.2 is still compatible with 2019.1... and most likely the last one to
be compatible with it.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's
Mail
list account via Groups.Io
Sent: Sunday, August 18, 2019 11:44 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease

So will this version if installed in 2019.1.x stop it being installed?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Sunday, August 18, 2019 6:41 PM
Subject: [nvda-devel] Add-on Updater 19.08.2 #AddonRelease


Hi all,



Add-on Updater 19.08.2 is now available. This version resolves key error
seen when trying to look for updates for certain add-ons, along with
fixing
localizations for Arabic and Ukrainian.



Note: Add-on Updater 19.09 is coming soon, and that version will require
NVDA 2019.2 or later.

Cheers,

Joseph













Ref :https://github.com/nvaccess/nvda/pull/10078

Brian's Mail list account
 

https://github.com/nvaccess/nvda/pull/10078

Hi has this made it to the alpha snaps yet?
I'm not up to speed with how this process works but on the current alpha we see a few issues still. 1. it says Yield is deprecated, but later on it seems like there is indeed a circular issue that calls itself until something gives up then windows notices and asks if you want to close it but of course its stopped speaking so you never here the message!
INFO - updateCheck.AutoUpdateChecker._started (09:04:42.038):
Performing automatic update check
IO - inputCore.InputManager.executeGesture (09:04:45.043):
Input: kb(desktop):NVDA+n
IO - speech.speak (09:04:45.107):
Speaking [LangChangeCommand ('en_GB'), 'NVDA menu']
IO - inputCore.InputManager.executeGesture (09:04:50.786):
Input: kb(desktop):downArrow
IO - speech.speak (09:04:50.814):
Speaking [LangChangeCommand ('en_GB'), 'Preferences subMenu p']
IO - inputCore.InputManager.executeGesture (09:04:52.410):
Input: kb(desktop):rightArrow
IO - speech.speak (09:04:52.438):
Speaking [LangChangeCommand ('en_GB'), 'Settings... s 1 of 6']
IO - inputCore.InputManager.executeGesture (09:04:53.594):
Input: kb(desktop):enter
DEBUG - gui.settingsDialogs.__new__ (09:04:53.599):
Creating new settings dialog (multiInstanceAllowed:False). State of _instances {}
DEBUG - windowUtils.getWindowScalingFactor (09:04:53.600):
GetDpiForWindow failed, using GetDeviceCaps instead
DEBUG - windowUtils.getWindowScalingFactor (09:04:53.606):
GetDpiForWindow failed, using GetDeviceCaps instead
IO - speech.speak (09:04:53.690):
Speaking [LangChangeCommand ('en_GB'), 'NVDA Settings: General (normal configuration) dialog']
IO - speech.speak (09:04:53.692):
Speaking [LangChangeCommand ('en_GB'), 'Categories: list']
IO - speech.speak (09:04:53.697):
Speaking [LangChangeCommand ('en_GB'), 'General 1 of 15']
IO - inputCore.InputManager.executeGesture (09:04:55.595):
Input: kb(desktop):downArrow
DEBUG - windowUtils.getWindowScalingFactor (09:04:55.597):
GetDpiForWindow failed, using GetDeviceCaps instead
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:04:55.600):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 0}
DEBUG - windowUtils.getWindowScalingFactor (09:04:55.603):
GetDpiForWindow failed, using GetDeviceCaps instead
IO - speech.speak (09:04:55.693):
Speaking [LangChangeCommand ('en_GB'), 'Speech 2 of 15']
IO - inputCore.InputManager.executeGesture (09:04:57.603):
Input: kb(desktop):tab
IO - speech.speak (09:04:57.674):
Speaking [LangChangeCommand ('en_GB'), 'Speech property page']
IO - speech.speak (09:04:57.681):
Speaking [LangChangeCommand ('en_GB'), 'Synthesizer grouping']
IO - speech.speak (09:04:57.688):
Speaking [LangChangeCommand ('en_GB'), 'Synthesizer edit read only multi line Alt+s']
IO - speech.speak (09:04:57.690):
Speaking [LangChangeCommand ('en_GB'), 'eSpeak NG\r']
DEBUGWARNING - Python warning (09:04:57.690):
C:\nvda extra\library.zip\api.py:287: DeprecationWarning: Yield() is deprecated
IO - inputCore.InputManager.executeGesture (09:04:59.475):
Input: kb(desktop):tab
IO - speech.speak (09:04:59.504):
Speaking [LangChangeCommand ('en_GB'), 'Change... button Alt+h']
IO - inputCore.InputManager.executeGesture (09:05:00.627):
Input: kb(desktop):space
IO - speech.speak (09:05:00.631):
Speaking [LangChangeCommand ('en_GB'), 'space', EndUtteranceCommand()]
IO - speech.speak (09:05:00.631):
Speaking [LangChangeCommand ('en_GB'), 'pressed']
DEBUG - gui.settingsDialogs.__new__ (09:05:00.795):
Creating new settings dialog (multiInstanceAllowed:True). State of _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1}
DEBUG - windowUtils.getWindowScalingFactor (09:05:00.796):
GetDpiForWindow failed, using GetDeviceCaps instead
DEBUGWARNING - synthDriverHandler.getSynthList (09:05:00.801):
Synthesizer 'oneCore' doesn't pass the check, excluding from list
IO - speech.speak (09:05:00.856):
Speaking [LangChangeCommand ('en_GB'), 'Select Synthesizer dialog']
IO - speech.speak (09:05:00.862):
Speaking [LangChangeCommand ('en_GB'), 'Synthesizer: combo box eSpeak NG collapsed Alt+s']
IO - inputCore.InputManager.executeGesture (09:05:04.619):
Input: kb(desktop):downArrow
IO - speech.speak (09:05:04.626):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech API version 4']
IO - inputCore.InputManager.executeGesture (09:05:05.947):
Input: kb(desktop):downArrow
IO - speech.speak (09:05:05.970):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech API version 5']
IO - inputCore.InputManager.executeGesture (09:05:07.947):
Input: kb(desktop):downArrow
IO - speech.speak (09:05:07.969):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech Platform']
IO - inputCore.InputManager.executeGesture (09:05:09.674):
Input: kb(desktop):downArrow
IO - speech.speak (09:05:09.692):
Speaking [LangChangeCommand ('en_GB'), 'No speech']
IO - inputCore.InputManager.executeGesture (09:05:10.762):
Input: kb(desktop):upArrow
IO - speech.speak (09:05:10.771):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech Platform']
IO - inputCore.InputManager.executeGesture (09:05:11.226):
Input: kb(desktop):upArrow
IO - speech.speak (09:05:11.242):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech API version 5']
IO - inputCore.InputManager.executeGesture (09:05:12.395):
Input: kb(desktop):upArrow
IO - speech.speak (09:05:12.412):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech API version 4']
IO - inputCore.InputManager.executeGesture (09:05:16.683):
Input: kb(desktop):enter
DEBUG - speechDictHandler.SpeechDict.load (09:05:16.781):
Loading speech dictionary '.\userConfig\speechDicts\voiceDicts.v1\sapi4\sapi4-English-American_ Reed (Adult Male) - ViaVoice Outloud 4.0.dic'...
DEBUG - speechDictHandler.SpeechDict.load (09:05:16.782):
file '.\userConfig\speechDicts\voiceDicts.v1\sapi4\sapi4-English-American_ Reed (Adult Male) - ViaVoice Outloud 4.0.dic' not found.
DEBUG - synthDriverHandler.SynthDriver.loadSettings (09:05:16.782):
Loaded settings for SynthDriver sapi4
INFO - synthDriverHandler.setSynth (09:05:16.782):
Loaded synthDriver sapi4
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.782):
Setting state to destroyed for instance: <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 0}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.783):
Setting state to destroyed for instance: <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.785):
Setting state to destroyed for instance: <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.786):
Setting state to destroyed for instance: <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.788):
Setting state to destroyed for instance: <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.788):
Setting state to destroyed for instance: <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.789):
Setting state to destroyed for instance: <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.790):
Setting state to destroyed for instance: <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.791):
Setting state to destroyed for instance: <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
IO - speech.speak (09:05:16.818):
Speaking [LangChangeCommand ('en_US'), 'NVDA Settings: Speech (normal configuration) dialog']
DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (09:05:16.818):
No CLDR data for locale en_US
DEBUGWARNING - synthDrivers.sapi4.SynthDriver.speak (09:05:16.818):
Unsupported speech command: LangChangeCommand ('en_US')
IO - speech.speak (09:05:16.865):
Speaking [LangChangeCommand ('en_US'), 'Speech property page']
IO - speech.speak (09:05:16.871):
Speaking [LangChangeCommand ('en_US'), 'Synthesizer grouping']
IO - speech.speak (09:05:16.877):
Speaking [LangChangeCommand ('en_US'), 'Synthesizer edit read only multi line Alt+s']
IO - speech.speak (09:05:16.878):
Speaking [LangChangeCommand ('en_US'), 'Microsoft Speech API version 4\r']
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.884):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.884):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.884):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.885):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.885):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.885):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.885):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.886):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.886):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.886):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.886):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.886):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.887):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.887):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.887):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.887):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.887):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.888):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.888):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.888):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.888):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.888):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.888):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.889):
Setting state to destroyed for instance: <gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState (09:05:16.923):
Setting state to destroyed for instance: <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>: 1}
DEBUGWARNING - synthDrivers.sapi4.SynthDriver.speak (09:05:21.520):
Unsupported speech command: LangChangeCommand ('en_US')
IO - inputCore.InputManager.executeGesture (09:05:23.035):
Input: kb(desktop):tab
IO - speech.speak (09:05:23.059):
Speaking [LangChangeCommand ('en_US'), 'Change... button Alt+h']
DEBUGWARNING - synthDrivers.sapi4.SynthDriver.speak (09:05:23.060):
Unsupported speech command: LangChangeCommand ('en_US')
IO - inputCore.InputManager.executeGesture (09:05:24.363):
Input: kb(desktop):tab
DEBUGWARNING - synthDrivers.sapi4.SynthDriverBufSink.IUnknown_Release (09:05:24.380):
ITTSBufNotifySink::Release called too many times by engine
IO - speech.speak (09:05:24.394):
Speaking [LangChangeCommand ('en_US'), 'Voice: combo box English-American: Reed (Adult Male) - ViaVoice Outloud 4.0 collapsed Alt+v']
DEBUGWARNING - synthDrivers.sapi4.SynthDriver.speak (09:05:24.395):
Unsupported speech command: LangChangeCommand ('en_US')
IO - inputCore.InputManager.executeGesture (09:05:30.315):
Input: kb(desktop):downArrow
DEBUGWARNING - synthDrivers.sapi4.SynthDriverBufSink.IUnknown_Release (09:05:30.321):
ITTSBufNotifySink::Release called too many times by engine
DEBUGWARNING - synthDrivers.sapi4.SynthDriverBufSink.IUnknown_Release (09:05:30.325):
ITTSBufNotifySink
::Release called too many times by engine


It has ground to a halt by this time.


NVDA version alpha-18420,a8e8db19
Using Windows version 6.1.7601 service pack 1 workstation


Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Mail app in Windows 10 (1903/next)

Andy B.
 

Hi,

 

I get the following in the NVDA log when pressing control+r to reply to an email:

 

ERROR - scriptHandler.executeScript (17:01:40.127):

error executing script: <bound method GlobalCommands.script_review_currentWord of <globalCommands.GlobalCommands object at 0x0591C230>> with gesture u'numpad 5'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 192, in executeScript

  File "globalCommands.pyc", line 1063, in script_review_currentWord

  File "treeInterceptorHandler.pyc", line 172, in copy

  File "NVDAObjects\UIA\__init__.pyc", line 686, in copy

  File "NVDAObjects\UIA\__init__.pyc", line 276, in __init__

RuntimeError: Could not clone range

Re: Mail app in Windows 10 (1903/next)

Brian's Mail list account
 

Just a thought, have you got the correct version of the win 10 essentials add on installed for the version of win 10 in use.
One of the bugbears I have is the awful email client though. I hate it if I have to use Win 10. They obviously want everyone to buy Outlook!
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Andy B." <sonfire11@...>
To: <nvda-devel@groups.io>
Sent: Monday, August 19, 2019 10:09 PM
Subject: [nvda-devel] Mail app in Windows 10 (1903/next)


Hi,

I get the following in the NVDA log when pressing control+r to reply to an email:

ERROR - scriptHandler.executeScript (17:01:40.127):
error executing script: <bound method GlobalCommands.script_review_currentWord of <globalCommands.GlobalCommands object at 0x0591C230>> with gesture u'numpad 5'
Traceback (most recent call last):
File "scriptHandler.pyc", line 192, in executeScript
File "globalCommands.pyc", line 1063, in script_review_currentWord
File "treeInterceptorHandler.pyc", line 172, in copy
File "NVDAObjects\UIA\__init__.pyc", line 686, in copy
File "NVDAObjects\UIA\__init__.pyc", line 276, in __init__
RuntimeError: Could not clone range

Add-on Updater and Enhanced Touch Gestures 19.09 going out early

 

Hi all,

 

Add-on Updater and Enhanced Touch Gestures 19.09 are on their way – will be out in about an hour or so. Originally I was planning to release them in September, but figured it is better to release them today so I can start my break a bit early.

 

IMPORTANT: today’s releases require NVDA 2019.2.

 

P.S. Windows 10 App Essentials 19.09 will also come out today, but that one won’t require NVDA 2019.2 for a while.

 

Cheers,

Joseph