Date   
Re: speech refactor things in the threshold snapshot and introduction

zvonimir stanečić, 9a5dsz
 

You can just use the tts from the link I posted, and test it like a 7 days trial

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Michael Curran
Sent: Wednesday, June 5, 2019 10:58 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] speech refactor things in the threshold snapshot and introduction

 

Jamie had already ported sapi5 in his initial work in 2017.

 

However, I will look into this. Perhaps the characterMode command is now somehow different to pre-speechRefactor.

 

Mick

 

 

On 6/5/2019 5:25 PM, Leonard de Ruijter wrote:

Hey Marco,

 

I was prett# sure that Mick also ported the sapi5 driver. I could be wrong, though.

 

Regards,

Leonard


Op 5 jun. 2019 om 09:11 heeft Marco Zehe <marco.zehe@...> het volgende geschreven:

Hi zvonimir,

 

this is totally expected. Threshold contains the refactored speech engine. And it appears that backwards compatibility is not yet fully restored. Neither the Vocalizer nor the SAPI 5 driver have been updated to the new interfaces yet. The only synths that are expected to work are eSpeak NG and Microsoft OneCore (Windows 10 voices).

 

Marco

 

 

Am Di., 4. Juni 2019 um 23:54 Uhr schrieb zvonimir stanečić, 9a5dsz <zvonimirek222@...>:

Hi to all,

My name is Zvonimir Stanecic, I am one of the NVDA translators for Croatian language.

I have an issue with the latest threshold snaps, with the codefactory vocalizer sapi5 synth, no matter which voice I use.

so… when trying to type individual letters, I hear the phoneme names, but not the names of the letters, i.e characters.

For example, in Russian, I don’t hear hardsign and softsign/

Here is the sapi version of the codefactory vocalizer to download.

https://yadi.sk/d/kAenU1FJay2vxQ

It’s the same problem with the vocalizer for NVDA package from codefactory.

Note that in alpha snaps this problem is not visible.

Best,

Zvonimir

Re: speech refactor things in the threshold snapshot and introduction

zvonimir stanečić, 9a5dsz
 

This caracter mode command somehow breaks vocalizer as an NVDA addon *codefactory

Sapi versio, too

It says for example, number followed by the word space

 

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Michael Curran
Sent: Wednesday, June 5, 2019 10:58 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] speech refactor things in the threshold snapshot and introduction

 

Jamie had already ported sapi5 in his initial work in 2017.

 

However, I will look into this. Perhaps the characterMode command is now somehow different to pre-speechRefactor.

 

Mick

 

 

On 6/5/2019 5:25 PM, Leonard de Ruijter wrote:

Hey Marco,

 

I was prett# sure that Mick also ported the sapi5 driver. I could be wrong, though.

 

Regards,

Leonard


Op 5 jun. 2019 om 09:11 heeft Marco Zehe <marco.zehe@...> het volgende geschreven:

Hi zvonimir,

 

this is totally expected. Threshold contains the refactored speech engine. And it appears that backwards compatibility is not yet fully restored. Neither the Vocalizer nor the SAPI 5 driver have been updated to the new interfaces yet. The only synths that are expected to work are eSpeak NG and Microsoft OneCore (Windows 10 voices).

 

Marco

 

 

Am Di., 4. Juni 2019 um 23:54 Uhr schrieb zvonimir stanečić, 9a5dsz <zvonimirek222@...>:

Hi to all,

My name is Zvonimir Stanecic, I am one of the NVDA translators for Croatian language.

I have an issue with the latest threshold snaps, with the codefactory vocalizer sapi5 synth, no matter which voice I use.

so… when trying to type individual letters, I hear the phoneme names, but not the names of the letters, i.e characters.

For example, in Russian, I don’t hear hardsign and softsign/

Here is the sapi version of the codefactory vocalizer to download.

https://yadi.sk/d/kAenU1FJay2vxQ

It’s the same problem with the vocalizer for NVDA package from codefactory.

Note that in alpha snaps this problem is not visible.

Best,

Zvonimir

Re: speech refactor things in the threshold snapshot and introduction

Michael Curran
 

Jamie had already ported sapi5 in his initial work in 2017.


However, I will look into this. Perhaps the characterMode command is now somehow different to pre-speechRefactor.


Mick



On 6/5/2019 5:25 PM, Leonard de Ruijter wrote:
Hey Marco,

I was prett# sure that Mick also ported the sapi5 driver. I could be wrong, though.

Regards,
Leonard

Op 5 jun. 2019 om 09:11 heeft Marco Zehe <marco.zehe@...> het volgende geschreven:

Hi zvonimir,

this is totally expected. Threshold contains the refactored speech engine. And it appears that backwards compatibility is not yet fully restored. Neither the Vocalizer nor the SAPI 5 driver have been updated to the new interfaces yet. The only synths that are expected to work are eSpeak NG and Microsoft OneCore (Windows 10 voices).

Marco


Am Di., 4. Juni 2019 um 23:54 Uhr schrieb zvonimir stanečić, 9a5dsz <zvonimirek222@...>:

Hi to all,

My name is Zvonimir Stanecic, I am one of the NVDA translators for Croatian language.

I have an issue with the latest threshold snaps, with the codefactory vocalizer sapi5 synth, no matter which voice I use.

so… when trying to type individual letters, I hear the phoneme names, but not the names of the letters, i.e characters.

For example, in Russian, I don’t hear hardsign and softsign/

Here is the sapi version of the codefactory vocalizer to download.

https://yadi.sk/d/kAenU1FJay2vxQ

It’s the same problem with the vocalizer for NVDA package from codefactory.

Note that in alpha snaps this problem is not visible.

Best,

Zvonimir

Re: speech refactor things in the threshold snapshot and introduction

zvonimir stanečić, 9a5dsz
 

You don’t understand:

Vocalizer on sapi5 works, but the character spelling is problematic.

I don’t know how vocalizer sends characters to the sapi5 itself.

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Marco Zehe
Sent: Wednesday, June 5, 2019 9:12 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] speech refactor things in the threshold snapshot and introduction

 

Hi zvonimir,

 

this is totally expected. Threshold contains the refactored speech engine. And it appears that backwards compatibility is not yet fully restored. Neither the Vocalizer nor the SAPI 5 driver have been updated to the new interfaces yet. The only synths that are expected to work are eSpeak NG and Microsoft OneCore (Windows 10 voices).

 

Marco

 

 

Am Di., 4. Juni 2019 um 23:54 Uhr schrieb zvonimir stanečić, 9a5dsz <zvonimirek222@...>:

Hi to all,

My name is Zvonimir Stanecic, I am one of the NVDA translators for Croatian language.

I have an issue with the latest threshold snaps, with the codefactory vocalizer sapi5 synth, no matter which voice I use.

so… when trying to type individual letters, I hear the phoneme names, but not the names of the letters, i.e characters.

For example, in Russian, I don’t hear hardsign and softsign/

Here is the sapi version of the codefactory vocalizer to download.

https://yadi.sk/d/kAenU1FJay2vxQ

It’s the same problem with the vocalizer for NVDA package from codefactory.

Note that in alpha snaps this problem is not visible.

Best,

Zvonimir

Re: speech refactor things in the threshold snapshot and introduction

 

Hey Marco,

I was prett# sure that Mick also ported the sapi5 driver. I could be wrong, though.

Regards,
Leonard

Op 5 jun. 2019 om 09:11 heeft Marco Zehe <marco.zehe@...> het volgende geschreven:

Hi zvonimir,

this is totally expected. Threshold contains the refactored speech engine. And it appears that backwards compatibility is not yet fully restored. Neither the Vocalizer nor the SAPI 5 driver have been updated to the new interfaces yet. The only synths that are expected to work are eSpeak NG and Microsoft OneCore (Windows 10 voices).

Marco


Am Di., 4. Juni 2019 um 23:54 Uhr schrieb zvonimir stanečić, 9a5dsz <zvonimirek222@...>:

Hi to all,

My name is Zvonimir Stanecic, I am one of the NVDA translators for Croatian language.

I have an issue with the latest threshold snaps, with the codefactory vocalizer sapi5 synth, no matter which voice I use.

so… when trying to type individual letters, I hear the phoneme names, but not the names of the letters, i.e characters.

For example, in Russian, I don’t hear hardsign and softsign/

Here is the sapi version of the codefactory vocalizer to download.

https://yadi.sk/d/kAenU1FJay2vxQ

It’s the same problem with the vocalizer for NVDA package from codefactory.

Note that in alpha snaps this problem is not visible.

Best,

Zvonimir

Re: speech refactor things in the threshold snapshot and introduction

Brian's Mail list account
 

You are lucky to get two. In my windows 7 box it is just Espeak, even the native sappi5 and speech platform are not selectable in the synth dialogue at all. I had assumed this was because the job was only half done so to speak, at least it stops you from selecting them, a little worrying that one can in fact attempt to use others.
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: "Marco Zehe" <marco.zehe@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, June 05, 2019 8:11 AM
Subject: Re: [nvda-devel] speech refactor things in the threshold snapshot and introduction


Hi zvonimir,

this is totally expected. Threshold contains the refactored speech engine.
And it appears that backwards compatibility is not yet fully restored.
Neither the Vocalizer nor the SAPI 5 driver have been updated to the new
interfaces yet. The only synths that are expected to work are eSpeak NG and
Microsoft OneCore (Windows 10 voices).

Marco


Am Di., 4. Juni 2019 um 23:54 Uhr schrieb zvonimir stanečić, 9a5dsz <
zvonimirek222@...>:

Hi to all,

My name is Zvonimir Stanecic, I am one of the NVDA translators for
Croatian language.

I have an issue with the latest threshold snaps, with the codefactory
vocalizer sapi5 synth, no matter which voice I use.

so… when trying to type individual letters, I hear the phoneme names, but
not the names of the letters, i.e characters.

For example, in Russian, I don’t hear hardsign and softsign/

Here is the sapi version of the codefactory vocalizer to download.

https://yadi.sk/d/kAenU1FJay2vxQ

It’s the same problem with the vocalizer for NVDA package from codefactory.

Note that in alpha snaps this problem is not visible.

Best,

Zvonimir


Re: speech refactor things in the threshold snapshot and introduction

Marco Zehe
 

Hi zvonimir,

this is totally expected. Threshold contains the refactored speech engine. And it appears that backwards compatibility is not yet fully restored. Neither the Vocalizer nor the SAPI 5 driver have been updated to the new interfaces yet. The only synths that are expected to work are eSpeak NG and Microsoft OneCore (Windows 10 voices).

Marco


Am Di., 4. Juni 2019 um 23:54 Uhr schrieb zvonimir stanečić, 9a5dsz <zvonimirek222@...>:

Hi to all,

My name is Zvonimir Stanecic, I am one of the NVDA translators for Croatian language.

I have an issue with the latest threshold snaps, with the codefactory vocalizer sapi5 synth, no matter which voice I use.

so… when trying to type individual letters, I hear the phoneme names, but not the names of the letters, i.e characters.

For example, in Russian, I don’t hear hardsign and softsign/

Here is the sapi version of the codefactory vocalizer to download.

https://yadi.sk/d/kAenU1FJay2vxQ

It’s the same problem with the vocalizer for NVDA package from codefactory.

Note that in alpha snaps this problem is not visible.

Best,

Zvonimir

speech refactor things in the threshold snapshot and introduction

zvonimir stanečić, 9a5dsz
 

Hi to all,

My name is Zvonimir Stanecic, I am one of the NVDA translators for Croatian language.

I have an issue with the latest threshold snaps, with the codefactory vocalizer sapi5 synth, no matter which voice I use.

so… when trying to type individual letters, I hear the phoneme names, but not the names of the letters, i.e characters.

For example, in Russian, I don’t hear hardsign and softsign/

Here is the sapi version of the codefactory vocalizer to download.

https://yadi.sk/d/kAenU1FJay2vxQ

It’s the same problem with the vocalizer for NVDA package from codefactory.

Note that in alpha snaps this problem is not visible.

Best,

Zvonimir

Re: The expected trashing of many current add ons when Python 3 version/sound changes comes out

Brian's Mail list account
 

I was just rather worried that as things tend to happen in this world, the urgency might tend to be lost and it might affect the usage of NVDA as a result.

I have not obviously exhaustedly tested add ons, but do intend to leave the current ones live on Threshold to see what happens.
At the moment the current beta breaks 3D sounds, and both it and of course Focus Highlight now no longer work in Threshold.

Pico stopped working in recent snaps but it may only be a manifest issue at present.

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: "Michael Curran" <mick@...>
To: <nvda-devel@groups.io>
Sent: Tuesday, June 04, 2019 12:54 PM
Subject: Re: [nvda-devel] The expected trashing of many current add ons when Python 3 version/sound changes comes out


There is no date planned yet. We will consider that once the Python 3 conversion has been completed. Again, we will then give people at least 2 months to update their add-ons before it hits an official release.


Mick


On 6/4/2019 9:36 PM, Marlon Brandão de Sousa wrote:
When is Treshold set to be released?

Obrigado,
Marlon

Em 4 de jun de 2019, à(s) 06:40, Michael Curran <mick@...> escreveu:

By all means we will be notifying people. Especially synthDriver manufacturers. However, we are not yet ready to do that. Once Python 3 work has completed in Threshold, we will then start notifying people including providing pointers and guides to how to update add-ons. Add-on maintainers will get plenty of time (at least 2 months) to update their add-ons before Threshold is finally in an official release.


Mick




On 6/4/2019 6:09 PM, Brian's Mail list account via Groups.Io wrote:
Some incompatibilities are already noticed in the beta and alpha snaps, but most of them seem quite minor, but I see in the main issues list a continuous stream of changes being required to make the normal nvda core perform correctly. Having already been monitoring some of the add ons I use for their ability to work under the ever changing conditions, it looks like most, if not all add ons will break.
Should somebody not look at the contacts for the add ons and make a mail list of them and suggest that they do some testing ahead of time and fix them as otherwise there will be a problem when the new version comes out all at once, add ons will fail to run or be disabled or behave strangely if you modify the manifest as I have done.

It was just a thought, as although it is obvious a supported version of Python has to be used for nvda, I do not believe many will be very happy when the new version basically resets the clock to a time when we had no add ons.

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: The expected trashing of many current add ons when Python 3 version/sound changes comes out

Michael Curran
 

There is no date planned yet. We will consider that once the Python 3 conversion has been completed. Again, we will then give people at least 2 months to update their add-ons before it hits an official release.


Mick

On 6/4/2019 9:36 PM, Marlon Brandão de Sousa wrote:
When is Treshold set to be released?

Obrigado,
Marlon

Em 4 de jun de 2019, à(s) 06:40, Michael Curran <mick@...> escreveu:

By all means we will be notifying people. Especially synthDriver manufacturers. However, we are not yet ready to do that. Once Python 3 work has completed in Threshold, we will then start notifying people including providing pointers and guides to how to update add-ons. Add-on maintainers will get plenty of time (at least 2 months) to update their add-ons before Threshold is finally in an official release.


Mick




On 6/4/2019 6:09 PM, Brian's Mail list account via Groups.Io wrote:
Some incompatibilities are already noticed in the beta and alpha snaps, but most of them seem quite minor, but I see in the main issues list a continuous stream of changes being required to make the normal nvda core perform correctly. Having already been monitoring some of the add ons I use for their ability to work under the ever changing conditions, it looks like most, if not all add ons will break.
Should somebody not look at the contacts for the add ons and make a mail list of them and suggest that they do some testing ahead of time and fix them as otherwise there will be a problem when the new version comes out all at once, add ons will fail to run or be disabled or behave strangely if you modify the manifest as I have done.

It was just a thought, as although it is obvious a supported version of Python has to be used for nvda, I do not believe many will be very happy when the new version basically resets the clock to a time when we had no add ons.

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: The expected trashing of many current add ons when Python 3 version/sound changes comes out

Marlon Brandão de Sousa
 

When is Treshold set to be released?

Obrigado,
Marlon

Em 4 de jun de 2019, à(s) 06:40, Michael Curran <mick@...> escreveu:

By all means we will be notifying people. Especially synthDriver manufacturers. However, we are not yet ready to do that. Once Python 3 work has completed in Threshold, we will then start notifying people including providing pointers and guides to how to update add-ons. Add-on maintainers will get plenty of time (at least 2 months) to update their add-ons before Threshold is finally in an official release.


Mick




On 6/4/2019 6:09 PM, Brian's Mail list account via Groups.Io wrote:
Some incompatibilities are already noticed in the beta and alpha snaps, but most of them seem quite minor, but I see in the main issues list a continuous stream of changes being required to make the normal nvda core perform correctly. Having already been monitoring some of the add ons I use for their ability to work under the ever changing conditions, it looks like most, if not all add ons will break.
Should somebody not look at the contacts for the add ons and make a mail list of them and suggest that they do some testing ahead of time and fix them as otherwise there will be a problem when the new version comes out all at once, add ons will fail to run or be disabled or behave strangely if you modify the manifest as I have done.

It was just a thought, as although it is obvious a supported version of Python has to be used for nvda, I do not believe many will be very happy when the new version basically resets the clock to a time when we had no add ons.

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: The expected trashing of many current add ons when Python 3 version/sound changes comes out

Michael Curran
 

By all means we will be notifying people. Especially synthDriver manufacturers. However, we are not yet ready to do that. Once Python 3 work has completed in Threshold, we will then start notifying people including providing pointers and guides to how to update add-ons. Add-on maintainers will get plenty of time (at least 2 months) to update their add-ons before Threshold is finally in an official release.


Mick

On 6/4/2019 6:09 PM, Brian's Mail list account via Groups.Io wrote:
Some incompatibilities are already noticed in the beta and alpha snaps, but most of them seem quite minor, but I see in the main issues list a continuous stream of changes being required to make the normal  nvda core perform correctly. Having already been monitoring some of the  add ons I use for their ability to work under the ever changing conditions, it looks like most, if not all add ons will break.
Should somebody not look at the contacts for the add ons and make a mail list of them and suggest that they  do some testing ahead of time and fix them as otherwise there will be a problem when the new version comes out all at once, add ons will fail to run or be disabled or behave strangely if you modify the manifest as I have done.

It was just a thought, as although it is obvious a supported version of Python has to be used for nvda, I do not believe many will be very happy when the new version  basically resets the clock to a time when we had no add ons.

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

The expected trashing of many current add ons when Python 3 version/sound changes comes out

Brian's Mail list account
 

Some incompatibilities are already noticed in the beta and alpha snaps, but most of them seem quite minor, but I see in the main issues list a continuous stream of changes being required to make the normal nvda core perform correctly. Having already been monitoring some of the add ons I use for their ability to work under the ever changing conditions, it looks like most, if not all add ons will break.
Should somebody not look at the contacts for the add ons and make a mail list of them and suggest that they do some testing ahead of time and fix them as otherwise there will be a problem when the new version comes out all at once, add ons will fail to run or be disabled or behave strangely if you modify the manifest as I have done.

It was just a thought, as although it is obvious a supported version of Python has to be used for nvda, I do not believe many will be very happy when the new version basically resets the clock to a time when we had no add ons.

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: Latest beta. a bit flaky when you try to install it

Brian's Mail list account
 

Yes and today's updates all went in without a problem. Its still a bit odd though to be constantly prodded by add on updates to threshold, when none of them will install of course.
Maybe there needs to be another bit in the manifest expected by threshold and if its missing then you won't get prompted.
I have possibly foolishly let all the current updates except those dealing with sound and synths be installed as per their last versions in any case.
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: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
To: <nvda-devel@groups.io>
Sent: Friday, May 31, 2019 10:28 AM
Subject: Re: [nvda-devel] Latest beta. a bit flaky when you try to install it


I have managed to get it to install by ignoring the errors and just pressing on, but it only works for a my portable install, and not the automatic as this crashed and I had to restart the computer.
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: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
To: "NVDA Dev list on groups.io" <nvda-devel@groups.io>
Sent: Friday, May 31, 2019 10:09 AM
Subject: [nvda-devel] Latest beta. a bit flaky when you try to install it


Windows 7 excerpt from log.

IO - speech.speak (09:47:21.661):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:21.668):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - speech.speak (09:47:21.704):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:21.710):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - inputCore.InputManager.executeGesture (09:47:28.551):
Input: kb(desktop):space
IO - speech._speakSpellingGen (09:47:28.565):
Speaking character u'space'
DEBUG - queueHandler.registerGeneratorObject (09:47:28.565):
Adding generator 1
IO - speech.speak (09:47:28.566):
Speaking [LangChangeCommand ('en_GB'), u'pressed']
DEBUG - queueHandler.pumpAll (09:47:28.575):
generator 1 finished
ERROR - unhandled exception (09:47:28.729):
Traceback (most recent call last):
File "updateCheck.pyc", line 514, in onInstallButton
wxAssertionError: C++ assertion "IsRunning()" failed at ..\..\src\common\evtloopcmn.cpp(83) in wxEventLoopBase::Exit(): Use ScheduleExit() on not running loop
IO - speech.speak (09:47:28.763):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:28.766):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - speech.speak (09:47:28.875):
Speaking [LangChangeCommand ('en_GB'), u'dialog Please wait while Setup is loading...']
IO - speech.speak (09:47:28.891):
Speaking [LangChangeCommand ('en_GB'), u'text']
IO - speech.speak (09:47:39.305):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:39.315):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (09:47:39.407):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
IO - speech.speak (09:47:39.421):
Speaking [LangChangeCommand ('en_GB'), u'Desktop list']
IO - speech.speak (09:47:39.430):
Speaking [LangChangeCommand ('en_GB'), u'Waterfox 18 of 74']

That was where it just stopped working.



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: Suggestion for the user guide from a user of spanish community

Brian's Mail list account
 

Actually there are lots of people everywhere who do not get it. It took me a while to figure it out by imagining a number of layers of glass each painted with a different pattern, but looked at from the front you could not tell they were on separate bits of glass.

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: "Ângelo Abrantes" <ampa4374@...>
To: <nvda-devel@groups.io>
Sent: Saturday, June 01, 2019 10:11 AM
Subject: Re: [nvda-devel] Suggestion for the user guide from a user of spanish community


Hi,


I Think it's a very good idea, because, in Portugal, there are lots of nvda's users who don't hunderstand this mechanisms

Thanks
Ângelo Abrantes
Às 08:31 de 01-06-2019, Noelia Ruiz escreveu:
Hello:

First of all, thanks for your attention: this is my first post on this list.
I would like to bring up a suggestion from an NVDA's user, member of an NVDA's mailing list created by me for the spanish community.
This person, named Carlos Esteban, is suggesting to include practical examples (like activities) to explain use cases for object navigation, review cursor and Windows 10 OCR. He argues that many users coming from JAWS ask how the NVDA's cursor can be activated, and that the hierarchical object navigation could be better understood including a section in the user guide, with an example as following:
- Press Windows+m to move to desktop.
- Use object navigation commands...
He explains that the basic training module has this kind of examples, but some people can't purchase it.
Should we create an issue or PR for this, or do you prefer to store this on wikis or dedicated websites?
You can see the topic in Spanish at

https://nvdaes.groups.io/g/lista/topic/31886737#708

Thanks

--
Cordiais Cumprimentos
Ângelo Abrantes, Equipa <Portuguesa do NVDA


---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus


Re: Suggestion for the user guide from a user of spanish community

Ângelo Abrantes
 

Hi,


I Think it's a very good idea, because, in Portugal, there are lots of nvda's users who don't hunderstand this mechanisms

Thanks
Ângelo Abrantes
Às 08:31 de 01-06-2019, Noelia Ruiz escreveu:

Hello:

First of all, thanks for your attention: this is my first post on this list.
I would like to bring up a suggestion from an NVDA's user, member of an NVDA's mailing list created by me for the spanish community.
This person, named Carlos Esteban, is suggesting to include practical examples (like activities) to explain use cases for object navigation, review cursor and Windows 10 OCR. He argues that many users coming from JAWS ask how the NVDA's cursor can be activated, and that the hierarchical object navigation could be better understood including a section in the user guide, with an example as following:
- Press Windows+m to move to desktop.
- Use object navigation commands...
He explains that the basic training module has this kind of examples, but some people can't purchase it.
Should we create an issue or PR for this, or do you prefer to store this on wikis or dedicated websites?
You can see the topic in Spanish at

https://nvdaes.groups.io/g/lista/topic/31886737#708

Thanks

--
Cordiais Cumprimentos
Ângelo Abrantes, Equipa <Portuguesa do NVDA


---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus

Suggestion for the user guide from a user of spanish community

Noelia Ruiz
 

Hello:

First of all, thanks for your attention: this is my first post on this list.
I would like to bring up a suggestion from an NVDA's user, member of an NVDA's mailing list created by me for the spanish community.
This person, named Carlos Esteban, is suggesting to include practical examples (like activities) to explain use cases for object navigation, review cursor and Windows 10 OCR. He argues that many users coming from JAWS ask how the NVDA's cursor can be activated, and that the hierarchical object navigation could be better understood including a section in the user guide, with an example as following:
- Press Windows+m to move to desktop.
- Use object navigation commands...
He explains that the basic training module has this kind of examples, but some people can't purchase it.
Should we create an issue or PR for this, or do you prefer to store this on wikis or dedicated websites?
You can see the topic in Spanish at

https://nvdaes.groups.io/g/lista/topic/31886737#708

Thanks

Re: Latest beta. a bit flaky when you try to install it

Brian's Mail list account
 

I have managed to get it to install by ignoring the errors and just pressing on, but it only works for a my portable install, and not the automatic as this crashed and I had to restart the computer.
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: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
To: "NVDA Dev list on groups.io" <nvda-devel@groups.io>
Sent: Friday, May 31, 2019 10:09 AM
Subject: [nvda-devel] Latest beta. a bit flaky when you try to install it


Windows 7 excerpt from log.

IO - speech.speak (09:47:21.661):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:21.668):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - speech.speak (09:47:21.704):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:21.710):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - inputCore.InputManager.executeGesture (09:47:28.551):
Input: kb(desktop):space
IO - speech._speakSpellingGen (09:47:28.565):
Speaking character u'space'
DEBUG - queueHandler.registerGeneratorObject (09:47:28.565):
Adding generator 1
IO - speech.speak (09:47:28.566):
Speaking [LangChangeCommand ('en_GB'), u'pressed']
DEBUG - queueHandler.pumpAll (09:47:28.575):
generator 1 finished
ERROR - unhandled exception (09:47:28.729):
Traceback (most recent call last):
File "updateCheck.pyc", line 514, in onInstallButton
wxAssertionError: C++ assertion "IsRunning()" failed at ..\..\src\common\evtloopcmn.cpp(83) in wxEventLoopBase::Exit(): Use ScheduleExit() on not running loop
IO - speech.speak (09:47:28.763):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:28.766):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - speech.speak (09:47:28.875):
Speaking [LangChangeCommand ('en_GB'), u'dialog Please wait while Setup is loading...']
IO - speech.speak (09:47:28.891):
Speaking [LangChangeCommand ('en_GB'), u'text']
IO - speech.speak (09:47:39.305):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:39.315):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (09:47:39.407):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
IO - speech.speak (09:47:39.421):
Speaking [LangChangeCommand ('en_GB'), u'Desktop list']
IO - speech.speak (09:47:39.430):
Speaking [LangChangeCommand ('en_GB'), u'Waterfox 18 of 74']

That was where it just stopped working.



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: Latest beta. a bit flaky when you try to install it

Brian's Mail list account
 

More woes in latest beta. Decided to try a manual install, it started throwing errors in the edit box in the select folder dialogue this time.

DEBUG - core.main (10:11:17.025):
entering wx application main loop
IO - speech.speak (10:11:17.094):
Speaking [LangChangeCommand ('en_GB'), u'NVDA dialog']
DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (10:11:17.094):
No CLDR data for locale en_GB
IO - speech.speak (10:11:17.242):
Speaking [LangChangeCommand ('en_GB'), u'License Agreement grouping']
IO - speech.speak (10:11:17.286):
Speaking [LangChangeCommand ('en_GB'), u'License Agreement edit read only multi line']
IO - speech.speak (10:11:17.289):
Speaking [LangChangeCommand ('en_GB'), u'align left', u'NVDA License\r']
DEBUGWARNING - Python warning (10:11:17.290):
C:\Users\Brian\AppData\Local\Temp\nsx7AFB.tmp\app\library.zip\api.py:274: DeprecationWarning: Yield() is deprecated
IO - inputCore.InputManager.executeGesture (10:11:19.858):
Input: kb(desktop):tab
IO - speech.speak (10:11:19.924):
Speaking [LangChangeCommand ('en_GB'), u'I agree check box not checked Alt+a']
IO - inputCore.InputManager.executeGesture (10:11:20.601):
Input: kb(desktop):space
IO - speech._speakSpellingGen (10:11:20.621):
Speaking character u'space'
DEBUG - queueHandler.registerGeneratorObject (10:11:20.622):
Adding generator 1
DEBUG - queueHandler.pumpAll (10:11:20.638):
generator 1 finished
IO - speech.speak (10:11:20.750):
Speaking [LangChangeCommand ('en_GB'), u'checked']
IO - inputCore.InputManager.executeGesture (10:11:22.338):
Input: kb(desktop):tab
IO - speech.speak (10:11:22.375):
Speaking [LangChangeCommand ('en_GB'), u'Install NVDA on this computer button Alt+i']
IO - inputCore.InputManager.executeGesture (10:11:24.825):
Input: kb(desktop):tab
IO - speech.speak (10:11:24.865):
Speaking [LangChangeCommand ('en_GB'), u'Create portable copy button Alt+p']
DEBUGWARNING - RPC process 4360 (nvda_update_hstdvn.exe) (10:11:24.950):
Thread 3912, build\x86\remote\ia2Support.cpp, IA2Support_inProcess_terminate, 152:
WaitForMultipleObjects returned 258

IO - inputCore.InputManager.executeGesture (10:11:27.009):
Input: kb(desktop):space
IO - speech._speakSpellingGen (10:11:27.019):
Speaking character u'space'
DEBUG - queueHandler.registerGeneratorObject (10:11:27.020):
Adding generator 2
IO - speech.speak (10:11:27.023):
Speaking [LangChangeCommand ('en_GB'), u'pressed']
DEBUG - queueHandler.pumpAll (10:11:27.033):
generator 2 finished
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (10:11:27.246):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
IO - speech.speak (10:11:27.278):
Speaking [LangChangeCommand ('en_GB'), u'Create Portable NVDA dialog To create a portable copy of NVDA, please select the path and other options and then press Continue']
IO - speech.speak (10:11:27.286):
Speaking [LangChangeCommand ('en_GB'), u'Portable directory: grouping']
IO - speech.speak (10:11:27.295):
Speaking [LangChangeCommand ('en_GB'), u'Portable directory: edit Alt+d']
IO - speech.speak (10:11:27.296):
Speaking [LangChangeCommand ('en_GB'), u'blank']
IO - inputCore.InputManager.executeGesture (10:11:35.779):
Input: kb(desktop):tab
IO - speech.speak (10:11:35.812):
Speaking [LangChangeCommand ('en_GB'), u'Browse... button']
IO - inputCore.InputManager.executeGesture (10:11:37.009):
Input: kb(desktop):space
IO - speech._speakSpellingGen (10:11:37.016):
Speaking character u'space'
DEBUG - queueHandler.registerGeneratorObject (10:11:37.016):
Adding generator 3
IO - speech.speak (10:11:37.017):
Speaking [LangChangeCommand ('en_GB'), u'pressed']
DEBUG - queueHandler.pumpAll (10:11:37.030):
generator 3 finished
IO - speech.speak (10:11:37.411):
Speaking [LangChangeCommand ('en_GB'), u'Select portable directory dialog']
IO - speech.speak (10:11:37.418):
Speaking [LangChangeCommand ('en_GB'), u'Folder: edit']
IO - speech.speak (10:11:37.420):
Speaking [LangChangeCommand ('en_GB'), u'blank']
IO - inputCore.InputManager.executeGesture (10:11:40.729):
Input: kb(desktop):tab
IO - speech.speak (10:11:40.788):
Speaking [LangChangeCommand ('en_GB'), u'Select Folder button']
IO - inputCore.InputManager.executeGesture (10:11:41.668):
Input: kb(desktop):tab
IO - speech.speak (10:11:41.694):
Speaking [LangChangeCommand ('en_GB'), u'Cancel button']
IO - inputCore.InputManager.executeGesture (10:11:42.323):
Input: kb(desktop):tab
IO - speech.speak (10:11:42.371):
Speaking [LangChangeCommand ('en_GB'), u'Address: C:\\ tool bar']
IO - speech.speak (10:11:42.385):
Speaking [LangChangeCommand ('en_GB'), u'Desktop split button']
IO - inputCore.InputManager.executeGesture (10:11:46.088):
Input: kb(desktop):tab
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (10:11:46.121):
oleacc.AccessibleObjectFromEvent with window 197542, objectID 11 and childID 0: [Error -2147467259] Unspecified error
IO - speech.speak (10:11:46.147):
Speaking [LangChangeCommand ('en_GB'), u' Search Windows (C:)']
ERROR - eventHandler.executeEvent (10:11:46.986):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1FBB0> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
IO - inputCore.InputManager.executeGesture (10:11:47.265):
Input: kb(desktop):tab
IO - speech.speak (10:11:47.421):
Speaking [LangChangeCommand ('en_GB'), u'Explorer Pane']
IO - inputCore.InputManager.executeGesture (10:11:49.688):
Input: kb(desktop):shift+tab
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (10:11:49.709):
oleacc.AccessibleObjectFromEvent with window 197542, objectID 14 and childID 0: [Error -2147467259] Unspecified error
IO - speech.speak (10:11:49.769):
Speaking [LangChangeCommand ('en_GB'), u' Search Windows (C:)']
ERROR - eventHandler.executeEvent (10:11:50.967):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F210> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:11:52.272):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F210> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
IO - inputCore.InputManager.executeGesture (10:11:52.513):
Input: kb(desktop):tab
IO - speech.speak (10:11:52.655):
Speaking [LangChangeCommand ('en_GB'), u'Explorer Pane']
IO - inputCore.InputManager.executeGesture (10:11:54.214):
Input: kb(desktop):shift+tab
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (10:11:54.272):
oleacc.AccessibleObjectFromEvent with window 197542, objectID 17 and childID 0: [Error -2147467259] Unspecified error
IO - speech.speak (10:11:54.299):
Speaking [LangChangeCommand ('en_GB'), u' Search Windows (C:)']
ERROR - eventHandler.executeEvent (10:11:55.334):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:11:56.673):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:11:57.357):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:11:58.667):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:11:59.447):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=-252 is greather than right=-25668, which is not allowed
ERROR - eventHandler.executeEvent (10:12:00.104):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:12:01.141):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:12:06.092):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:12:08.091):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:12:09.125):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:12:10.125):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:12:10.773):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
ERROR - eventHandler.executeEvent (10:12:12.428):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05A1F150> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\IAccessible\__init__.pyc", line 1465, in event_caret
File "NVDAObjects\__init__.pyc", line 1071, in event_caret
File "review.pyc", line 174, in handleCaretMove
File "documentBase.pyc", line 24, in makeTextInfo
File "displayModel.pyc", line 264, in __init__
File "textInfos\offsets.pyc", line 405, in __init__
File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 390, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed
IO - inputCore.InputManager.executeGesture (10:12:12.744):
Input: kb(desktop):control+alt+r
IO - speech.speak (10:12:12.858):
Speaking [LangChangeCommand ('en_GB'), u'Taskbar']
IO - speech.speak (10:12:12.934):
Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log terminal']
IO - speech.speak (10:12:12.937):
Speaking [LangChangeCommand ('en_GB'), u'80 space', u'blank']
INFO - core.main (10:12:13.081):
Exiting
DEBUG - core._terminate (10:12:13.081):
Terminating updateCheck
DEBUG - core._terminate (10:12:13.081):
Terminating watchdog
DEBUG - core._terminate (10:12:13.081):
Terminating global plugin handler
DEBUG - core._terminate (10:12:13.585):
Terminating gui
IO - speech.speak (10:12:13.660):
Speaking [LangChangeCommand ('en_GB'), u"Nvda_nouiaccess Error dialog Couldn't obtain folder name (error 87: the parameter is incorrect.)"]
IO - speech.speak (10:12:13.665):
Speaking [LangChangeCommand ('en_GB'), u'OK button']


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: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
To: "NVDA Dev list on groups.io" <nvda-devel@groups.io>
Sent: Friday, May 31, 2019 10:09 AM
Subject: [nvda-devel] Latest beta. a bit flaky when you try to install it


Windows 7 excerpt from log.

IO - speech.speak (09:47:21.661):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:21.668):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - speech.speak (09:47:21.704):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:21.710):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - inputCore.InputManager.executeGesture (09:47:28.551):
Input: kb(desktop):space
IO - speech._speakSpellingGen (09:47:28.565):
Speaking character u'space'
DEBUG - queueHandler.registerGeneratorObject (09:47:28.565):
Adding generator 1
IO - speech.speak (09:47:28.566):
Speaking [LangChangeCommand ('en_GB'), u'pressed']
DEBUG - queueHandler.pumpAll (09:47:28.575):
generator 1 finished
ERROR - unhandled exception (09:47:28.729):
Traceback (most recent call last):
File "updateCheck.pyc", line 514, in onInstallButton
wxAssertionError: C++ assertion "IsRunning()" failed at ..\..\src\common\evtloopcmn.cpp(83) in wxEventLoopBase::Exit(): Use ScheduleExit() on not running loop
IO - speech.speak (09:47:28.763):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:28.766):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - speech.speak (09:47:28.875):
Speaking [LangChangeCommand ('en_GB'), u'dialog Please wait while Setup is loading...']
IO - speech.speak (09:47:28.891):
Speaking [LangChangeCommand ('en_GB'), u'text']
IO - speech.speak (09:47:39.305):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:39.315):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (09:47:39.407):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
IO - speech.speak (09:47:39.421):
Speaking [LangChangeCommand ('en_GB'), u'Desktop list']
IO - speech.speak (09:47:39.430):
Speaking [LangChangeCommand ('en_GB'), u'Waterfox 18 of 74']

That was where it just stopped working.



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

Latest beta. a bit flaky when you try to install it

Brian's Mail list account
 

Windows 7 excerpt from log.

IO - speech.speak (09:47:21.661):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:21.668):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - speech.speak (09:47:21.704):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:21.710):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - inputCore.InputManager.executeGesture (09:47:28.551):
Input: kb(desktop):space
IO - speech._speakSpellingGen (09:47:28.565):
Speaking character u'space'
DEBUG - queueHandler.registerGeneratorObject (09:47:28.565):
Adding generator 1
IO - speech.speak (09:47:28.566):
Speaking [LangChangeCommand ('en_GB'), u'pressed']
DEBUG - queueHandler.pumpAll (09:47:28.575):
generator 1 finished
ERROR - unhandled exception (09:47:28.729):
Traceback (most recent call last):
File "updateCheck.pyc", line 514, in onInstallButton
wxAssertionError: C++ assertion "IsRunning()" failed at ..\..\src\common\evtloopcmn.cpp(83) in wxEventLoopBase::Exit(): Use ScheduleExit() on not running loop
IO - speech.speak (09:47:28.763):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:28.766):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
IO - speech.speak (09:47:28.875):
Speaking [LangChangeCommand ('en_GB'), u'dialog Please wait while Setup is loading...']
IO - speech.speak (09:47:28.891):
Speaking [LangChangeCommand ('en_GB'), u'text']
IO - speech.speak (09:47:39.305):
Speaking [LangChangeCommand ('en_GB'), u'NVDA Update dialog NVDA version beta-17404,e9faffa1 is ready to be installed.\n']
IO - speech.speak (09:47:39.315):
Speaking [LangChangeCommand ('en_GB'), u'Install update button Alt+i']
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (09:47:39.407):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
IO - speech.speak (09:47:39.421):
Speaking [LangChangeCommand ('en_GB'), u'Desktop list']
IO - speech.speak (09:47:39.430):
Speaking [LangChangeCommand ('en_GB'), u'Waterfox 18 of 74']

That was where it just stopped working.



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