Date   
Re: nvdaControllerClient.dll

Vincent Le Goff
 

That's a good news, thanks.

On 9/24/2019 1:56 PM, James Scholes wrote:
The controller client is implemented in C++, so is not necessarily subject to direct changes during the Python 3 transition.  I would expect any internal changes to NVDA's speech and other frameworks to be handled in a backward-compatible way.

Regards,

James Scholes

On 24/09/2019 at 11:44 am, Vincent Le Goff wrote:
Hi everyone,


Sorry for insisting on this topic, but as a developer I would appreciate if my applications remain accessible despite the change in NVDA's programming language.  In short: will I need to update the nvdaControllerClient.dll*file to "talk" to NVDA?  And if so, how will I maintain compatibility with people using older versions of NVDA?  I admit I have no idea if a dll file built for Python 2 will need to be updated for Python 3, but the date is drawing near and I will need to know what to do, if I don't want to run the risk of my applications becoming inaccessible to NVDA users.*

*
*

*Thanks in advance!*

*
*

*Vincent*

Re: nvdaControllerClient.dll

James Scholes
 

The controller client is implemented in C++, so is not necessarily subject to direct changes during the Python 3 transition. I would expect any internal changes to NVDA's speech and other frameworks to be handled in a backward-compatible way.

Regards,

James Scholes

On 24/09/2019 at 11:44 am, Vincent Le Goff wrote:
Hi everyone,
Sorry for insisting on this topic, but as a developer I would appreciate if my applications remain accessible despite the change in NVDA's programming language.  In short: will I need to update the nvdaControllerClient.dll*file to "talk" to NVDA?  And if so, how will I maintain compatibility with people using older versions of NVDA?  I admit I have no idea if a dll file built for Python 2 will need to be updated for Python 3, but the date is drawing near and I will need to know what to do, if I don't want to run the risk of my applications becoming inaccessible to NVDA users.*
*
*
*Thanks in advance!*
*
*
*Vincent*

Re : [nvda-devel] nvdaControllerClient.dll

Cyrille
 

Hello Vincent
I have no knowledge on how this DLL is interfaced with NVDA.
However, I had created once an exe linking this DLL to control NVDA speaking via command line. I have not modified or recompiled the exe neither the DLL I was using and I can confirm you that this is still working with latest alpha.
Cyrille
----- Mail d'origine -----
De: Vincent Le Goff <vincent.legoff.srs@...>
À: nvda-devel@groups.io
Envoyé: Tue, 24 Sep 2019 12:44:10 +0200 (CEST)
Objet: [nvda-devel] nvdaControllerClient.dll

Hi everyone,

Sorry for insisting on this topic, but as a developer I would
appreciate if my applications remain accessible despite the change
in NVDA's programming language.  In short: will I need to update
the nvdaControllerClient.dll file to "talk" to NVDA?  And if
so, how will I maintain compatibility with people using older
versions of NVDA?  I admit I have no idea if a dll file built
for Python 2 will need to be updated for Python 3, but the date
is drawing near and I will need to know what to do, if I don't
want to run the risk of my applications becoming inaccessible to
NVDA users.

 

Thanks in advance!

 

Vincent

nvdaControllerClient.dll

Vincent Le Goff
 

Hi everyone,


Sorry for insisting on this topic, but as a developer I would appreciate if my applications remain accessible despite the change in NVDA's programming language.  In short: will I need to update the nvdaControllerClient.dll file to "talk" to NVDA?  And if so, how will I maintain compatibility with people using older versions of NVDA?  I admit I have no idea if a dll file built for Python 2 will need to be updated for Python 3, but the date is drawing near and I will need to know what to do, if I don't want to run the risk of my applications becoming inaccessible to NVDA users.


Thanks in advance!


Vincent

Re: Latest alpha, cannot create portable copy

Brian's Mail list account
 

Seems to work on this mornings update thus far.

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: Monday, September 23, 2019 4:51 PM
Subject: Re: [nvda-devel] Latest alpha, cannot create portable copy


I see this has caused some activity on the ticket I raised, best wait till the fix is approved as its not in the current snap as yet.
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: Monday, September 23, 2019 9:57 AM
Subject: Re: [nvda-devel] Latest alpha, cannot create portable copy


here is the log entry. This straight from the auto download of the version.

entering wx application main loop
ERROR - gui.installerGui.doCreatePortable (09:47:32.418) - MainThread (4576):
Failed to create portable copy
Traceback (most recent call last):
File "gui\installerGui.pyc", line 359, in doCreatePortable
File "gui\__init__.pyc", line 900, in __init__
File "threading.pyc", line 1077, in name
AssertionError: Thread.__init__() not called
IO - speech.speak (09:47:32.444) - MainThread (4576):
Speaking [LangChangeCommand ('en_GB'), 'Desktop list']


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: Monday, September 23, 2019 9:50 AM
Subject: [nvda-devel] Latext alpha, Cannot creae portable copy


thread.init not called.
No idea what this means.
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: A new error?

Brian's Mail list account
 

Well not entirely true. I have been around long enough to have seen some that show no immediate issues but end up in a crash due to memory leaks and the like so I always mention something different, just in 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: "James Scholes" <james@...>
To: <nvda-devel@groups.io>
Sent: Monday, September 23, 2019 8:49 PM
Subject: Re: [nvda-devel] A new error?


If there's no problematic behaviour, it's not a problem.

Regards,

James Scholes

On 23/09/2019 at 8:46 pm, Brian's Mail list account via Groups.Io wrote:
Oh It was mine, I was just intrigued what it mean, as I see it a lot in alpha snaps but there seems to be no ding or indeed any kind of obvious issue.

Sorry if it confused you!

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: "Cyrille via Groups.Io" <cyrille.bougot2=laposte.net@groups.io>
To: <nvda-devel@groups.io>
Sent: Monday, September 23, 2019 8:00 PM
Subject: Re: [nvda-devel] A new error?


Hello Brian

This unique line tells us that you were reading a line of the log where this
error occurred.
But without context, we cannot know if you were reading your log or the one
of someone else, e.g. in an e-mail or on Github. We cannot know what you
were doing...

Cyrille



-----Message d'origine-----
De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Brian's Mail
list account via Groups.Io
Envoyé : lundi 23 septembre 2019 17:54
À : NVDA Dev list on groups.io <nvda-devel@groups.io>
Objet : [nvda-devel] A new error?

Don't think I've seen this one before. should I be worried?
IO - speech.speak (16:40:58.573) - MainThread (5604):
Speaking [LangChangeCommand ('en_GB'), 'oleacc.AccessibleObjectFromEvent
with window 327702, objectID 475 and childID 0: [WinError -2147467259]
Unspecified error\r']

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: A new error?

James Scholes
 

If there's no problematic behaviour, it's not a problem.

Regards,

James Scholes

On 23/09/2019 at 8:46 pm, Brian's Mail list account via Groups.Io wrote:
Oh It was mine, I was just intrigued what it mean, as I see it a lot in alpha snaps but there seems to be no ding or indeed any kind of obvious issue.
Sorry if it confused you!
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: "Cyrille via Groups.Io" <cyrille.bougot2=laposte.net@groups.io>
To: <nvda-devel@groups.io>
Sent: Monday, September 23, 2019 8:00 PM
Subject: Re: [nvda-devel] A new error?
Hello Brian
This unique line tells us that you were reading a line of the log where this
error occurred.
But without context, we cannot know if you were reading your log or the one
of someone else, e.g. in an e-mail or on Github. We cannot know what you
were doing...
Cyrille
-----Message d'origine-----
De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Brian's Mail
list account via Groups.Io
Envoyé : lundi 23 septembre 2019 17:54
À : NVDA Dev list on groups.io <nvda-devel@groups.io>
Objet : [nvda-devel] A new error?
Don't think I've seen this one before. should I be worried?
IO - speech.speak (16:40:58.573) - MainThread (5604):
Speaking [LangChangeCommand ('en_GB'), 'oleacc.AccessibleObjectFromEvent
with window 327702, objectID 475 and childID 0: [WinError -2147467259]
Unspecified error\r']
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: A new error?

Brian's Mail list account
 

Oh It was mine, I was just intrigued what it mean, as I see it a lot in alpha snaps but there seems to be no ding or indeed any kind of obvious issue.

Sorry if it confused you!

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: "Cyrille via Groups.Io" <cyrille.bougot2=laposte.net@groups.io>
To: <nvda-devel@groups.io>
Sent: Monday, September 23, 2019 8:00 PM
Subject: Re: [nvda-devel] A new error?


Hello Brian

This unique line tells us that you were reading a line of the log where this
error occurred.
But without context, we cannot know if you were reading your log or the one
of someone else, e.g. in an e-mail or on Github. We cannot know what you
were doing...

Cyrille



-----Message d'origine-----
De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Brian's Mail
list account via Groups.Io
Envoyé : lundi 23 septembre 2019 17:54
À : NVDA Dev list on groups.io <nvda-devel@groups.io>
Objet : [nvda-devel] A new error?

Don't think I've seen this one before. should I be worried?
IO - speech.speak (16:40:58.573) - MainThread (5604):
Speaking [LangChangeCommand ('en_GB'), 'oleacc.AccessibleObjectFromEvent
with window 327702, objectID 475 and childID 0: [WinError -2147467259]
Unspecified error\r']

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: A new error?

Cyrille
 

Hello Brian

This unique line tells us that you were reading a line of the log where this
error occurred.
But without context, we cannot know if you were reading your log or the one
of someone else, e.g. in an e-mail or on Github. We cannot know what you
were doing...

Cyrille

-----Message d'origine-----
De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Brian's Mail
list account via Groups.Io
Envoyé : lundi 23 septembre 2019 17:54
À : NVDA Dev list on groups.io <nvda-devel@groups.io>
Objet : [nvda-devel] A new error?

Don't think I've seen this one before. should I be worried?
IO - speech.speak (16:40:58.573) - MainThread (5604):
Speaking [LangChangeCommand ('en_GB'), 'oleacc.AccessibleObjectFromEvent
with window 327702, objectID 475 and childID 0: [WinError -2147467259]
Unspecified error\r']

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

A new error?

Brian's Mail list account
 

Don't think I've seen this one before. should I be worried?
IO - speech.speak (16:40:58.573) - MainThread (5604):
Speaking [LangChangeCommand ('en_GB'), 'oleacc.AccessibleObjectFromEvent with window 327702, objectID 475 and childID 0: [WinError -2147467259] Unspecified error\r']

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 alpha, cannot create portable copy

Brian's Mail list account
 

I see this has caused some activity on the ticket I raised, best wait till the fix is approved as its not in the current snap as yet.
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: Monday, September 23, 2019 9:57 AM
Subject: Re: [nvda-devel] Latest alpha, cannot create portable copy


here is the log entry. This straight from the auto download of the version.

entering wx application main loop
ERROR - gui.installerGui.doCreatePortable (09:47:32.418) - MainThread (4576):
Failed to create portable copy
Traceback (most recent call last):
File "gui\installerGui.pyc", line 359, in doCreatePortable
File "gui\__init__.pyc", line 900, in __init__
File "threading.pyc", line 1077, in name
AssertionError: Thread.__init__() not called
IO - speech.speak (09:47:32.444) - MainThread (4576):
Speaking [LangChangeCommand ('en_GB'), 'Desktop list']


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: Monday, September 23, 2019 9:50 AM
Subject: [nvda-devel] Latext alpha, Cannot creae portable copy


thread.init not called.
No idea what this means.
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 alpha, cannot create portable copy

Brian's Mail list account
 

here is the log entry. This straight from the auto download of the version.

entering wx application main loop
ERROR - gui.installerGui.doCreatePortable (09:47:32.418) - MainThread (4576):
Failed to create portable copy
Traceback (most recent call last):
File "gui\installerGui.pyc", line 359, in doCreatePortable
File "gui\__init__.pyc", line 900, in __init__
File "threading.pyc", line 1077, in name
AssertionError: Thread.__init__() not called
IO - speech.speak (09:47:32.444) - MainThread (4576):
Speaking [LangChangeCommand ('en_GB'), 'Desktop list']


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: Monday, September 23, 2019 9:50 AM
Subject: [nvda-devel] Latext alpha, Cannot creae portable copy


thread.init not called.
No idea what this means.
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

Latext alpha, Cannot creae portable copy

Brian's Mail list account
 

thread.init not called.
No idea what this means.
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: NVDA 2019.3 and add-ons: progress update for September 2019

zvonimir stanečić, 9a5dsz
 

Hi to all!

I should tackle the following question here:

What’s the status of the NVDA remote add-on?

As you mentioned speech synthesizers, the codefactory vocalizer is also in the alpha testing phase.

They added new voices for korean and farsi

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Joseph Lee
Sent: Thursday, September 19, 2019 4:40 AM
To: nvda-devel@groups.io
Subject: [nvda-devel] NVDA 2019.3 and add-ons: progress update for September 2019

 

Dear NVDA community,

 

For those on the users list, a more user-friendly version will be sent soon.

 

Some updates on NVDA 2019.3 and add-on porting efforts:

 

  • How far are we: as of September 19, out of 68 add-ons hosted on community add-ons website, 43 (63%) are compatible with NVDA 2019.3 (Python 3). This count does not include one or two latest additions, but status for these will be added soon. Also, combined with ones in progress and planned ones, we got vast majority of add-ons covered.
  • Notable recent efforts: as you may have heard, Rui Fontes announced a Python 3 version of Vocalizer Direct (version 2.x) driver is under testing, and more speech synthesizer vendors are starting to notice how important it is for them to port their add-ons. Also, Tony’s various navigation add-ons are now Python 3 compatible – both Python 2 and 3 versions are ready, and DictationBridge team has committed to releasing a Python 3 version of DictationBridge soon (a public beta is scheduled to go out shortly after NVDA 2019.3 beta 1 is released).

 

The next progress update will be sent shortly after NVDA 2019.3 beta 1 is released.

Cheers,

Joseph

News on the python 3 auto update issue

Brian's Mail list account
 

It seems to have been due to some files left over in the folders from the old python 2 installation. Unfortunately I'm not sure which one was the problem as I went in and manually weeded out files and folders I knew did not exist in the Python 3 clean install.
So, the moral here would seem to be, apart from add ons that are known to work and settings, anything else take them away, or do a clean install completely and import the bits you want to manually.
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

NVDA 2019.3 and add-ons: progress update for September 2019

 

Dear NVDA community,

 

For those on the users list, a more user-friendly version will be sent soon.

 

Some updates on NVDA 2019.3 and add-on porting efforts:

 

  • How far are we: as of September 19, out of 68 add-ons hosted on community add-ons website, 43 (63%) are compatible with NVDA 2019.3 (Python 3). This count does not include one or two latest additions, but status for these will be added soon. Also, combined with ones in progress and planned ones, we got vast majority of add-ons covered.
  • Notable recent efforts: as you may have heard, Rui Fontes announced a Python 3 version of Vocalizer Direct (version 2.x) driver is under testing, and more speech synthesizer vendors are starting to notice how important it is for them to port their add-ons. Also, Tony’s various navigation add-ons are now Python 3 compatible – both Python 2 and 3 versions are ready, and DictationBridge team has committed to releasing a Python 3 version of DictationBridge soon (a public beta is scheduled to go out shortly after NVDA 2019.3 beta 1 is released).

 

The next progress update will be sent shortly after NVDA 2019.3 beta 1 is released.

Cheers,

Joseph

Re: The Alpha and Java Access Bridge

Karl-Otto Rosenqvist
 

Thanks!
Yes, the problem was that I didn't have the 32-bit version up and running. I found a version of Open JDK 11 for 32-bit Windows and now the Arduino IDE talks to me when I'm running NVDA too.

I do understand that NVAccess can't keep others installation packages around so it's a hard nut to crack, the ease of access to installation that works.

Anyway, big thanks again.

Karl-Otto

Karl-Otto Rosenqvist
Mawingu
Orgnr: 750804-3937
0701- 75 98 56
karl-otto@...
https://mawingu.se

Den 2019-09-18 kl. 15:55, skrev Jens Gierke:

Can't confirm that.
Using:
- NVDA alpha 18677
- Win 10 1903 64bit
- OpenJDK 11.0.4.11
"it works with JAWS" is not a helpful information.
Does it work with the latest stable of NVDA? If not, my first guess is
that your Java setup is not correct. When you run the IDE using a 64bit
JVM you must have installed a 32bit JVM which can NVDA use as
interconnect for the 64bit Access Bridge.
Best regards,
Jens
Am 17.09.2019 um 18:52 schrieb Karl-Otto Rosenqvist:
Hi!
I have the version: alpha-18677,348c3500 and it doesn't seem to work
with Java Access Bridge. I know it works because JAWS makes the Arduino
IDE accessible after I've installed Java Access Bridge but NVDA doesn't
work.

Is this due to me running an alpha version or is it something else?


Kind regards

Karl-Otto


Karl-Otto Rosenqvist
Mawingu
Orgnr: 750804-3937
+46 (0)701 75 98 56
karl-otto@...


Re: The Alpha and Java Access Bridge

Jens Gierke
 

Can't confirm that.
Using:
- NVDA alpha 18677
- Win 10 1903 64bit
- OpenJDK 11.0.4.11

"it works with JAWS" is not a helpful information.
Does it work with the latest stable of NVDA? If not, my first guess is
that your Java setup is not correct. When you run the IDE using a 64bit
JVM you must have installed a 32bit JVM which can NVDA use as
interconnect for the 64bit Access Bridge.

Best regards,
Jens

Am 17.09.2019 um 18:52 schrieb Karl-Otto Rosenqvist:

Hi!
I have the version: alpha-18677,348c3500 and it doesn't seem to work
with Java Access Bridge. I know it works because JAWS makes the Arduino
IDE accessible after I've installed Java Access Bridge but NVDA doesn't
work.

Is this due to me running an alpha version or is it something else?


Kind regards

Karl-Otto


Karl-Otto Rosenqvist
Mawingu
Orgnr: 750804-3937
+46 (0)701 75 98 56
karl-otto@...

The Alpha and Java Access Bridge

Karl-Otto Rosenqvist
 

Hi!
I have the version: alpha-18677,348c3500 and it doesn't seem to work with Java Access Bridge. I know it works because JAWS makes the Arduino IDE accessible after I've installed Java Access Bridge but NVDA doesn't work.

Is this due to me running an alpha version or is it something else?


Kind regards

Karl-Otto


Karl-Otto Rosenqvist
Mawingu
Orgnr: 750804-3937
+46 (0)701 75 98 56
karl-otto@...

2019.2.1 coming?

Brian's Mail list account
 

Hi I sae ref to this possibility recently on one of the lists, could I remind somebody that if this is being done, the anti Explorer crash code would be nice in this version???please

It would help Windows 7 folk. I am at the moment running the try build made some weeks ago of the Python 3 version, and it has some other minor bugs of course because its an alpha.
Thanks.
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