Date   
Re: Re Alpha build snaps not auto updating even when set to do so.... was : [nvda-devel] Windows 7 explorer crash.

Brian's Mail list account
 

OK I know there is an update waiting but sitting in the alpha build now for some minutes its not being flagged unless I ask it..

Note this output was generated before I checked manually...

import updateCheck; print(updateCheck.state)
{'pendingUpdateAPIVersion': (0, 0, 0), 'pendingUpdateVersionTuple': None, 'dontRemindVersion': 'alpha-18633,65a2c3c2', 'removeFile': 'C:\\Users\\Brian\\AppData\\Local\\Temp\\nvda_update_vzilp1.exe', 'lastCheck': 1568541473.2267175, 'pendingUpdateFile': None, 'pendingUpdateVersion': None, 'pendingUpdateBackCompatToAPIVersion': (0, 0, 0)}

Now all the normal settings in the general section are set correctly, yet nothing apparently occurswhen the portable version is started.
I do not understand the info above but as it was asked for, I have provided it.
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: "Luke Davis" <luke@...>
To: <nvda-devel@groups.io>
Sent: Saturday, September 14, 2019 8:58 AM
Subject: Re: Re Alpha build snaps not auto updating even when set to do so.... was : [nvda-devel] Windows 7 explorer crash.


Actually, after writing that last message, I launched my alpha portable, and immediately got an update request.
So I retract my former message.

That said, responding to your below, did you see Leonard's message on August 29th, replying to thread "does alpha snap auto update on windows 7?"?:

Could you guys please provide the output of the following in a python console?

import updateCheck; print(updateCheck.state)


My output is as follows:

{'pendingUpdateAPIVersion': (0, 0, 0), 'pendingUpdateBackCompatToAPIVersion': (0, 0, 0), 'dontRemindVersion': '2019.2', 'lastCheck': 1567002250.28,
'pendingUpdateFile': None, 'pendingUpdateVersion': None}

Regards,

Leonard


On Sat, 14 Sep 2019, Brian's Mail list account via Groups.Io wrote:

Yes when I last asked about he update automation, somebody said they would look into it, but I never heard any more

I guess one could raise a ticket for it. However the log definitely says checking for updates as it boots in, so without a smoking gun, so to speak, I don't know where else to go with it.
Anyone out there actually get alpha snaps to automatically inform of updates?
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: "Luke Davis" <luke@...>
To: "NVDA Dev list on groups.io" <nvda-devel@groups.io>
Sent: Saturday, September 14, 2019 7:12 AM
Subject: Re: [nvda-devel] Windows 7 explorer crash.


Don't know, but mine never do either, or at least never seem to prompt for updates, and I'm on Win 10 1903.

On Fri, 13 Sep 2019, Brian's Mail list account via Groups.Io wrote:

It seems to be fixed as we have been running the try build for some weeks now.
I saw an update to put this into the main build the other day, is this now in the normal Alpha build.
Incidentally, has anyone any idea why my portable versions of Alpha snaps never ever seem to check for updates even though its on but it works if I do it manually? This is on windows 7.
I can see no obvious reason.
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

--
Luke Davis
Moderator: the new NVDA Help mailing list! (https://groups.io/g/NVDAHelp)
Author: Debug Helper NVDA add-on (https://addons.nvda-project.org/addons/debugHelper.en.html)




--
Luke Davis
Moderator: the new NVDA Help mailing list! (https://groups.io/g/NVDAHelp)
Author: Debug Helper NVDA add-on (https://addons.nvda-project.org/addons/debugHelper.en.html)

Re: PR with appVeyor build failing

Abdel
 

Hi Cyrille and all,

Derek is right, the detail of the error is present in the log.

Here is the log page and below, the detail from line 226 to 239:

https://ci.appveyor.com/project/NVAccess/nvda/builds/27387406


226
interfaceAction(["source\comInterfaces\FlashAccessibility.py", "source\comInterfaces\__pycache__\FlashAccessibility.cpython-37.pyc"], ["source\typelibs\FlashAccessibility.tlb"])
227
scons: *** [source\comInterfaces\FlashAccessibility.py] ModuleNotFoundError : No module named 'comtypes.gen.FlashAccessibility'
228
Traceback (most recent call last):
229
  File "C:\projects\nvda\include\scons\src\engine\SCons\Action.py", line 1202, in execute
230
    result = self.execfunction(target=target, source=rsources, env=env)
231
  File "C:\projects\nvda\source\comInterfaces_sconscript", line 27, in interfaceAction
232
    comtypes.client.GetModule(source)
233
  File "C:\projects\nvda\include\comtypes\comtypes\client\_generate.py", line 146, in GetModule
234
    return _my_import("comtypes.gen." + modulename)
235
  File "C:\projects\nvda\include\comtypes\comtypes\client\_generate.py", line 24, in _my_import
236
    return __import__(fullname, globals(), locals(), ['DUMMY'])
237
ModuleNotFoundError: No module named 'comtypes.gen.FlashAccessibility'
238
scons: building terminated because of errors.
239
Command exited with code 2


Kind regards,
Abdel.

Le 16/09/2019 à 02:12, derek riemer a écrit :
I believe there is a txt file in the appVeyor artifacts with the exact failures.

On Sun, Sep 15, 2019 at 4:13 PM Luke Davis <luke@...> wrote:
I saw that. There was a link in that email (which I no longer have), can you not
look at that to see the errors? I never tried looking through one of those,
other than seeing that they go to appveyor's site.

Would the Appveyor console messages have it?


On Sun, 15 Sep 2019, Cyrille via Groups.Io wrote:

> I have pushed a new commit with only translator comments modified. Now the build ends up with Flake8 error. How can I analyze it?





--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com




Re : Re: [nvda-devel] PR with appVeyor build failing

Cyrille
 

Hello all
Thanks for your various replies.
The issue was due to new code linting and I have fixed it in a third commit. AppVeyor check is now OK.
I still however do not understand why the build failed this way on the first commit (cf. e-mail from Abdel). In the second commit I have only modified translators comments, so nothing to do with 'comtypes.gen.FlashAccessibility' où^import issue.
Anyway since all seems fine now:
1. Should I ask for a reviewer? If yes, who?
2. Should I update with respect to master branch since new commits have been added to master meanwhile? If yes, is it allowed to rebase?
Thanks,
Regards,
Cyrille
----- Mail d'origine -----
De: Abdel <abdelkrim.bensaid@...>
À: nvda-devel@groups.io
Envoyé: Mon, 16 Sep 2019 12:18:01 +0200 (CEST)
Objet: Re: [nvda-devel] PR with appVeyor build failing

Hi Cyrille and all,


Derek is right, the detail of the error is present in the log.


Here is the log page and below, the detail from line 226 to 239:

https://ci.appveyor.com/project/NVAccess/nvda/builds/27387406

226

interfaceAction(["source\comInterfaces\FlashAccessibility.py",
"source\comInterfaces\__pycache__\FlashAccessibility.cpython-37.pyc"],
["source\typelibs\FlashAccessibility.tlb"])

227

scons: *** [source\comInterfaces\FlashAccessibility.py]
ModuleNotFoundError : No module named
'comtypes.gen.FlashAccessibility'

228

Traceback (most recent call last):

229

  File
"C:\projects\nvda\include\scons\src\engine\SCons\Action.py",
line 1202, in execute

230

    result = self.execfunction(target=target, source=rsources,
env=env)

231

  File "C:\projects\nvda\source\comInterfaces_sconscript", line
27, in interfaceAction

232

    comtypes.client.GetModule(source)

233

  File
"C:\projects\nvda\include\comtypes\comtypes\client\_generate.py",
line 146, in GetModule

234

    return _my_import("comtypes.gen." + modulename)

235

  File
"C:\projects\nvda\include\comtypes\comtypes\client\_generate.py",
line 24, in _my_import

236

    return __import__(fullname, globals(), locals(), ['DUMMY'])

237

ModuleNotFoundError: No module named
'comtypes.gen.FlashAccessibility'

238

scons: building terminated because of errors.

239

Command exited with code 2


Kind regards,

Abdel.

Le 16/09/2019 à 02:12, derek riemer a
écrit :
I believe there is a txt file in the appVeyor
artifacts with the exact failures.

On Sun, Sep 15, 2019 at 4:13
PM Luke Davis <luke@...> wrote:
I saw that. There was a link in
that email (which I no longer have), can you not

look at that to see the errors? I never tried looking through
one of those,

other than seeing that they go to appveyor's site.

Would the Appveyor console messages have it?


On Sun, 15 Sep 2019, Cyrille via Groups.Io wrote:

> I have pushed a new commit with only translator comments
modified. Now the build ends up with Flake8 error. How can I
analyze it?



--
Derek Riemer

Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺
⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖

•    Accessibility enthusiast.

•    Proud user of the NVDA screen reader.

•    Open source enthusiast.

•    Skier.

•    Personal website: https://derekriemer.com

Re: Re Alpha build snaps not auto updating even when set to do so.... was : [nvda-devel] Windows 7 explorer crash.

Luke Davis
 

You can cut and paste all you want. You just have to press F6 first to get to the results window. A little unusual, but not that big a deal.

Luke

On Mon, 16 Sep 2019, Brian's Mail list account via Groups.Io wrote:

OK Its a great pity that one cannot simply cut and paste from the readable window here. Seems a bit convoluted compared with other text windows.
Brian
--
Luke Davis
Moderator: the new NVDA Help mailing list! (https://groups.io/g/NVDAHelp)
Author: Debug Helper NVDA add-on (https://addons.nvda-project.org/addons/debugHelper.en.html)

Re: PR with appVeyor build failing

Abdel
 

Hi Cyrille and all,

You wrote:

I still however do not understand why the build failed this way on the first commit (cf. e-mail from Abdel).


It doesn't come from your code but from the new code linting that you fixed in your third commit.

Regarding your other questions, it is the reviewers who do this work.

Congratulations, Mick approved your 3 commits and merged them into the master branch.

Your PR will certainly be integrated in nvda-2019.3.

Thanks for your great work.

Kind regards,
Abdel.


Le 16/09/2019 à 15:19, Cyrille via Groups.Io a écrit :

Hello all
Thanks for your various replies.
The issue was due to new code linting and I have fixed it in a third commit. AppVeyor check is now OK.
I still however do not understand why the build failed this way on the first commit (cf. e-mail from Abdel). In the second commit I have only modified translators comments, so nothing to do with 'comtypes.gen.FlashAccessibility' où^import issue.
Anyway since all seems fine now:
1. Should I ask for a reviewer? If yes, who?
2. Should I update with respect to master branch since new commits have been added to master meanwhile? If yes, is it allowed to rebase?
Thanks,
Regards,
Cyrille
----- Mail d'origine -----
De: Abdel <abdelkrim.bensaid@...>
À: nvda-devel@groups.io
Envoyé: Mon, 16 Sep 2019 12:18:01 +0200 (CEST)
Objet: Re: [nvda-devel] PR with appVeyor build failing

Hi Cyrille and all,


Derek is right, the detail of the error is present in the log.


Here is the log page and below, the detail from line 226 to 239:

https://ci.appveyor.com/project/NVAccess/nvda/builds/27387406
226

interfaceAction(["source\comInterfaces\FlashAccessibility.py",
"source\comInterfaces\__pycache__\FlashAccessibility.cpython-37.pyc"],
["source\typelibs\FlashAccessibility.tlb"])

227

scons: *** [source\comInterfaces\FlashAccessibility.py]
ModuleNotFoundError : No module named
'comtypes.gen.FlashAccessibility'

228

Traceback (most recent call last):

229

  File
"C:\projects\nvda\include\scons\src\engine\SCons\Action.py",
line 1202, in execute

230

    result = self.execfunction(target=target, source=rsources,
env=env)

231

  File "C:\projects\nvda\source\comInterfaces_sconscript", line
27, in interfaceAction

232

    comtypes.client.GetModule(source)

233

  File
"C:\projects\nvda\include\comtypes\comtypes\client\_generate.py",
line 146, in GetModule

234

    return _my_import("comtypes.gen." + modulename)

235

  File
"C:\projects\nvda\include\comtypes\comtypes\client\_generate.py",
line 24, in _my_import

236

    return __import__(fullname, globals(), locals(), ['DUMMY'])

237

ModuleNotFoundError: No module named
'comtypes.gen.FlashAccessibility'

238

scons: building terminated because of errors.

239

Command exited with code 2


Kind regards,

Abdel.

Le 16/09/2019 à 02:12, derek riemer a
écrit :
I believe there is a txt file in the appVeyor
artifacts with the exact failures.

On Sun, Sep 15, 2019 at 4:13
PM Luke Davis <luke@...> wrote:
I saw that. There was a link in
that email (which I no longer have), can you not

look at that to see the errors? I never tried looking through
one of those,

other than seeing that they go to appveyor's site.

Would the Appveyor console messages have it?


On Sun, 15 Sep 2019, Cyrille via Groups.Io wrote:

> I have pushed a new commit with only translator comments
modified. Now the build ends up with Flake8 error. How can I
analyze it?



--
Derek Riemer

Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺
⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖

•    Accessibility enthusiast.

•    Proud user of the NVDA screen reader.

•    Open source enthusiast.

•    Skier.

•    Personal website: https://derekriemer.com

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

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@...

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@...

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@...


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

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

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: 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

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



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: 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

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?

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
 

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