Date   
Re: Is there anything in the whats new about errors from add ons?

Michael Curran
 

Thanks for the info.

I have filed https://github.com/nvaccess/nvda/issues/9824


Mick

On 6/26/2019 7:03 PM, Brian's Mail list account via Groups.Io wrote:
The stable version looks like this.
It seems some process has gone away or been renamed perhaps?

snip
INFO - core.main (09:54:30.305):
NVDA version 2019.1.1
INFO - core.main (09:54:30.305):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (09:54:30.305):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
INFO - core.main (09:54:30.305):
Using comtypes version 1.1.3
INFO - core.main (09:54:30.305):
Using configobj version 5.1.0 with validate version 1.0.1
DEBUG - core.main (09:54:30.305):
Initializing add-ons system

snip
But this time just a warning.

DEBUGWARNING - Python warning (09:54:30.901):
C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\backend\unspoken\mixer.py:30: DeprecationWarning: integer argument expected, got float
DEBUGWARNING - Python warning (09:54:30.908):
C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py:62: DeprecationWarning: NewId() is deprecated
DEBUGWARNING - Python warning (09:54:30.908):
C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py:70: DeprecationWarning: NewId() is deprecated
DEBUG - core.main (09:54:31.030):
Initializing core pump
DEBUG - core.main (09:54:31.032):
Initializing watchdog
DEBUG - core.main (09:54:31.032):
initializing updateCheck
INFO - core.main (09:54:31.032):
NVDA initialized
DEBUG - core.main (09:54:31.032):
entering wx application main loop



Hope these two messages clarify this. I think Joseph may know something of this.
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 25, 2019 11:24 AM
Subject: Re: [nvda-devel] Is there anything in the whats new about errors from add ons?


I was unaware that there were any breaking changes for add-ons in 2019.2. This was not deliberate.


Could you please provide an example error from your log?


Thanks

Mick


On 6/25/2019 6:23 PM, Brian's Mail list account via Groups.Io wrote:
I only ask as these betas for the next release give errors on the 3D sound add on I'm running and it won't work, where the previous version of nvda stable still has it working. I'd imagine there might be others like this too.
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 anything in the whats new about errors from add ons?

Brian's Mail list account
 

The stable version looks like this.
It seems some process has gone away or been renamed perhaps?

snip
INFO - core.main (09:54:30.305):
NVDA version 2019.1.1
INFO - core.main (09:54:30.305):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (09:54:30.305):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
INFO - core.main (09:54:30.305):
Using comtypes version 1.1.3
INFO - core.main (09:54:30.305):
Using configobj version 5.1.0 with validate version 1.0.1
DEBUG - core.main (09:54:30.305):
Initializing add-ons system

snip
But this time just a warning.

DEBUGWARNING - Python warning (09:54:30.901):
C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\backend\unspoken\mixer.py:30: DeprecationWarning: integer argument expected, got float
DEBUGWARNING - Python warning (09:54:30.908):
C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py:62: DeprecationWarning: NewId() is deprecated
DEBUGWARNING - Python warning (09:54:30.908):
C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py:70: DeprecationWarning: NewId() is deprecated
DEBUG - core.main (09:54:31.030):
Initializing core pump
DEBUG - core.main (09:54:31.032):
Initializing watchdog
DEBUG - core.main (09:54:31.032):
initializing updateCheck
INFO - core.main (09:54:31.032):
NVDA initialized
DEBUG - core.main (09:54:31.032):
entering wx application main loop



Hope these two messages clarify this. I think Joseph may know something of this.
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 25, 2019 11:24 AM
Subject: Re: [nvda-devel] Is there anything in the whats new about errors from add ons?


I was unaware that there were any breaking changes for add-ons in 2019.2. This was not deliberate.


Could you please provide an example error from your log?


Thanks

Mick


On 6/25/2019 6:23 PM, Brian's Mail list account via Groups.Io wrote:
I only ask as these betas for the next release give errors on the 3D sound add on I'm running and it won't work, where the previous version of nvda stable still has it working. I'd imagine there might be others like this too.
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 anything in the whats new about errors from add ons?

Brian's Mail list account
 

Snipped first bit of log then.
INFO - core.main (09:28:14.200):
NVDA version 2019.2beta2
INFO - core.main (09:28:14.200):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (09:28:14.200):
Using Python version 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)]
INFO - core.main (09:28:14.200):
Using comtypes version 1.1.7
INFO - core.main (09:28:14.200):
Using configobj version 5.1.0 with validate version 1.0.1
DEBUG - core.main (09:28:14.200):
Initializing add-ons system

snipped all the boring stuff that works then..
from the middle of add on checking...
DEBUG - addonHandler.Addon.addToPackagePath (09:28:14.842):
Addon textnav added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (09:28:14.842):
Addon toolbarsExplorer added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (09:28:14.842):
Addon virtualRevision added to globalPlugins package path
DEBUGWARNING - Python warning (09:28:15.092):
C:\nvdaclean\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\backend\unspoken\mixer.py:30: DeprecationWarning: integer argument expected, got float
ERROR - globalPluginHandler.listPlugins (09:28:15.091):
Error importing global plugin audioThemes
Traceback (most recent call last):
File "globalPluginHandler.pyo", line 22, in listPlugins
File "C:\nvdaclean\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py", line 23, in <module>
File "C:\nvdaclean\userConfig\addons\AudioThemes3D\globalPlugins\audioThemes\dialogs\manage_dg.py", line 17, in <module>
ImportError: cannot import name VoiceSettingsSlider
DEBUG - core.main (09:28:15.109):
Initializing core pump
DEBUG - core.main (09:28:15.109):
Initializing watchdog
DEBUG - core.main (09:28:15.111):
initializing updateCheck
INFO - core.main (09:28:15.111):
NVDA initialized
DEBUG - core.main (09:28:15.111):
entering wx application main loop

As far as I'm aware I'm using the same version, as here is only one, on all my versions and its working on the current stable but nothing else.
It still has deprication warnings but these are just warnings and the sounds still appear to work.
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 25, 2019 11:24 AM
Subject: Re: [nvda-devel] Is there anything in the whats new about errors from add ons?


I was unaware that there were any breaking changes for add-ons in 2019.2. This was not deliberate.


Could you please provide an example error from your log?


Thanks

Mick


On 6/25/2019 6:23 PM, Brian's Mail list account via Groups.Io wrote:
I only ask as these betas for the next release give errors on the 3D sound add on I'm running and it won't work, where the previous version of nvda stable still has it working. I'd imagine there might be others like this too.
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: Issues related to UIA Console

Bill Dengler
 

Great to hear the positive feedback!!

Bill

On 21 Jun 2019, at 12:05, francisco del roio <francipvb@...> wrote:

Hello bill,

El 21/6/2019 a las 01:13, Bill Dengler escribió:
Could you please test to see if these issues are still present in the latest master snapshot?

Thanks,
Bill
In latest build (alpha-17750,27694a31) I cannot reproduce these bugs
anymore.

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.


Re: Is there anything in the whats new about errors from add ons?

Michael Curran
 

I was unaware that there were any breaking changes for add-ons in 2019.2. This was not deliberate.


Could you please provide an example error from your log?


Thanks

Mick

On 6/25/2019 6:23 PM, Brian's Mail list account via Groups.Io wrote:
I only ask as these betas for the next release give errors on the 3D sound add on I'm running and it won't work, where the previous version of nvda stable still has it working. I'd imagine there might be others like this too.
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

Is there anything in the whats new about errors from add ons?

Brian's Mail list account
 

I only ask as these betas for the next release give errors on the 3D sound add on I'm running and it won't work, where the previous version of nvda stable still has it working. I'd imagine there might be others like this too.
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: Issues related to UIA Console

francisco del roio
 

Hello bill,

El 21/6/2019 a las 01:13, Bill Dengler escribió:
Could you please test to see if these issues are still present in the latest master snapshot?

Thanks,
Bill
In latest build (alpha-17750,27694a31) I cannot reproduce these bugs
anymore.

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Re: Issues related to UIA Console

 

Hey Bill,


I'm now running latest Alpha with Windows 10 1903 and must see that you did a pretty good job. It is pretty much working as expected and way faster than the legacy implementation. Keep up the good work!


Regards,

Leonard

Op 21-6-2019 om 06:13 schreef Bill Dengler:

 Could you please test to see if these issues are still present in the latest master snapshot?

Thanks,
Bill 
On Jun 20, 2019, at 18:09, francisco del roio <francipvb@...> wrote:

El 20/6/2019 a las 19:04, francisco del roio escribió:
Hello bill,

I have to add another one:

In 1903, when you edit in the terminal, the review cursor is placed on
the next line.
I have to add that if there is not an empty line, a new fake blank line
is added. Do a git log under the NVDA repository and then read the
current line with the review command, then go to the previous and try to
go down again.

Cheers,-- 
Cuando tus fuerzas terminan, las de mi Dios comienzan.





Re: Issues related to UIA Console

Bill Dengler
 

Could you please test to see if these issues are still present in the latest master snapshot?

Thanks,
Bill

On Jun 20, 2019, at 18:09, francisco del roio <francipvb@...> wrote:

El 20/6/2019 a las 19:04, francisco del roio escribió:
Hello bill,

I have to add another one:

In 1903, when you edit in the terminal, the review cursor is placed on
the next line.
I have to add that if there is not an empty line, a new fake blank line
is added. Do a git log under the NVDA repository and then read the
current line with the review command, then go to the previous and try to
go down again.

Cheers,--
Cuando tus fuerzas terminan, las de mi Dios comienzan.


Re: Issues related to UIA Console

francisco del roio
 

El 20/6/2019 a las 19:04, francisco del roio escribió:
Hello bill,

I have to add another one:

In 1903, when you edit in the terminal, the review cursor is placed on
the next line.
I have to add that if there is not an empty line, a new fake blank line
is added. Do a git log under the NVDA repository and then read the
current line with the review command, then go to the previous and try to
go down again.

Cheers,--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Re: Issues related to UIA Console

francisco del roio
 

Hello bill,

I have to add another one:

In 1903, when you edit in the terminal, the review cursor is placed on
the next line.

Please, if you can do, add a new project to the NVDA repository to keep
track of all these issues and ease everyone check them and eventually
help you.

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Default issue template on issue tracker

Brian's Mail list account
 

I may have missed it but should not one of the items also ask the user to check the errors with add ons disabled as I see a lot of questions asking people to do this very thing on email lists etc.

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: Issues related to UIA Console

francisco del roio
 

El 18/6/2019 a las 10:33, francisco del roio escribió:
(...)> I am not in insider ... Yep, this happen to me.

In 1903, I mean

--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Re: Issues related to UIA Console

francisco del roio
 

Hello bill,

El 17/6/2019 a las 17:46, Bill Dengler escribió:
Francisco,
Thanks for trying out the UIA console!
The following known issues can't be fixed without work from Microsoft:

* When "speak passwords in UIA consoles" is disabled and one of "speak typed
characters" or "speak typed words" is enabled, `typedCharacter` events are
only dispatched once `textChange` is received. This may introduce a small
performance penalty. (this issue is theoretical, I haven't experienced it in
practice)
* Reporting of text selection is incorrect on Windows 10 version 1809 and
earlier.
I am not in insider ... Yep, this happen to me.

* After all characters of the input line have been deleted, further presses
of backspace read the last character of the output line.
* On Windows 10 1903, the space character is not announced when deleting
text.
* On Windows 10 1903, pressing down arrow does not read back the prompt.
* On Windows 10 1809 and earlier, space is read as "blank" when deleting
text (but is read properly in review).
This is a bit random, at least for me.

The following issues will be fixed once PR #9761 is merged:
* If the system language is not English, the name of the UIA console is not
localized.
* The windows 10 detection function always returns True if the
currently-running version is at least the supplied one. For example, this
makes it difficult to enable UIA consoles for Windows 10 1809 and later
except 1903.
* Since #9673, the last-typed word was sometimes still announced after
pressing enter with "speak typed words" enabled, including deleted
characters in some cases.
Can't reproduce this.

I have to add another to your list, but I don't know if you're aware of it:

When the console is full of lines, review commands only report the last
line. For example when you type git log on the NVDA repository.

Curiously, you can read the lines normally by using touchscreen
interaction. Is there a difference?

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Re: Issues related to UIA Console

Bill Dengler
 

Francisco,
Thanks for trying out the UIA console!
The following known issues can't be fixed without work from Microsoft:

* When "speak passwords in UIA consoles" is disabled and one of "speak typed
characters" or "speak typed words" is enabled, `typedCharacter` events are
only dispatched once `textChange` is received. This may introduce a small
performance penalty. (this issue is theoretical, I haven't experienced it in
practice)
* Reporting of text selection is incorrect on Windows 10 version 1809 and
earlier.
* After all characters of the input line have been deleted, further presses
of backspace read the last character of the output line.
* On Windows 10 1903, the space character is not announced when deleting
text.
* On Windows 10 1903, pressing down arrow does not read back the prompt.
* On Windows 10 1809 and earlier, space is read as "blank" when deleting
text (but is read properly in review).

The following issues will be fixed once PR #9761 is merged:
* If the system language is not English, the name of the UIA console is not
localized.
* The windows 10 detection function always returns True if the
currently-running version is at least the supplied one. For example, this
makes it difficult to enable UIA consoles for Windows 10 1809 and later
except 1903.
* Since #9673, the last-typed word was sometimes still announced after
pressing enter with "speak typed words" enabled, including deleted
characters in some cases.

Bill

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of francisco del
roio
Sent: Monday, 17 June, 2019 08:25
To: NVDA Development <nvda-devel@groups.io>
Subject: [nvda-devel] Issues related to UIA Console

Hello Bill,

Do you have a place to store centralized issues related to UIA console
support? I want to check if there is an issue I have.

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Issues related to UIA Console

francisco del roio
 

Hello Bill,

Do you have a place to store centralized issues related to UIA console
support? I want to check if there is an issue I have.

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Re: UIAutomation problems

Brian's Mail list account
 

Yes it would be interesting to know whether the fact that a certain shark like screenreader still having a display chaain driver might be their fix for this shortcoming in uia.
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 -----
Sent: Tuesday, June 11, 2019 11:04 AM
Subject: UIAutomation problems


Hello,

I again, posting problems regarding to UIAutomation support.

Sometimes focus events aren't reported by NVDA, as well occurs with
other events such elementSelected, or liveRegionChange, or reported too
late, about 3 seconds later than expected (instantly).

It occurs in various applications, but this is particularly annoying in
Visual Studio and (sometimes) in windows explorer.

Note that I have a good machine and it is ridiculous to have these
problems these days, taking account the time UIA is with us.

Some of you that know more about UIAutomation, please talk about it and
let's find a solution for these problems, or (almost) the source.

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

NVDA loses the compatibility with android studio when is restarted.

DaVid
 

Hi, I thought that its a very known issue but I searched on the issues
and didn't find it.
If I'm using android studio and restart NVDA, NVDA doesn't read the
ide interface, then I need to restart the ide.
I discovered yesterday that it can be easily solved.
If I open the console and initialize the JABHandler manually, now
accessibility works again. I don't understand why it doesn't work when
NVDA initializes the JABHandler when is starting. I do:
import JABHandler
JABHandler.initialize()
So NVDA should try to re initialize JABHandler automaticcally when
detects a java application.

Regards,
DaVid.

Re: UIAutomation problems

francisco del roio
 

Hello,

El 11/6/2019 a las 09:04, Leonard de Ruijter escribió:
Hello there,

To make sure, could you also test this with last alpha builds?

Regards,
Leonard
I'm running the latest alpha build.

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Re: UIAutomation problems

 

Hello there,

To make sure, could you also test this with last alpha builds?

Regards,
Leonard

Op 11 jun. 2019 om 12:04 heeft francisco del roio <francipvb@...> het volgende geschreven:

Hello,

I again, posting problems regarding to UIAutomation support.

Sometimes focus events aren't reported by NVDA, as well occurs with
other events such elementSelected, or liveRegionChange, or reported too
late, about 3 seconds later than expected (instantly).

It occurs in various applications, but this is particularly annoying in
Visual Studio and (sometimes) in windows explorer.

Note that I have a good machine and it is ridiculous to have these
problems these days, taking account the time UIA is with us.

Some of you that know more about UIAutomation, please talk about it and
let's find a solution for these problems, or (almost) the source.

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.