Date   
Re: WX.Menu item help text: where is it used?

Robert Hänggi
 

I suppose that this text is never used because it is only applicable
for windows that have both, a menu bar and a status line.
That's obviously not the case for a systray icon that has just a bunch of menus.
The top window is actually hidden.
I can't say for sure but I think the status line availability is
defined through the window style attribute.
NVDA doesn't pay much heed to that fact.
Search for instance the status line in NVDA's settings panel (with NVDA+End).
What you get are the buttons and not some kind of informative
description of the item you're focused on (if it were defined in the
first place).
Naturally, it should say that there isn't any status line.
Robert

On 03/09/2019, Noelia Ruiz <nrm1977@...> wrote:
Hi, answering in devel in case lead developers would like to clarify
something or use this discussion for NVDA's improvements.
I think that, in practical terms, the optional help string is never
used by NVDA, never spoken or braillified.
I don't know if this would make sense with the new vision framework,
for instance if this can be highlighted or show in some way.

Cheers

2019-08-30 4:22 GMT+02:00, Luke Davis <luke@...>:
Hello

Perhaps a stupid question, but if I call something like:

gui.mainFrame.sysTrayIcon.preferencesMenu.Append(wx.ID_ANY,
_("&menuItemName..."), _("Some descriptive text"))

where will "Some descriptive text" be used?

WX calls this "help", so I thought I would find it in a mouse hover or
tooltip
of some kind, but in attempting this with both the keyboard and the
actual
mouse, in NVDA 2017.3, I can not get anything spoken.

The docs for WX.Menu 4.1.0 say:

An optional help string associated with the item. By default, the handler
for
the wxEVT_MENU_HIGHLIGHT event
displays this string in the status line.

Which helps me not at all.

Thanks

--
Luke Davis
Moderator: the new NVDA Help mailing list! (NVDAHelp+subscribe@groups.io)
Author: Debug Helper NVDA add-on
(https://github.com/XLTechie/debugHelper)





Errors when using outlook 365.

Andy B.
 

Hi,

 

When I open Outlook 365, I get the following error in the log window:

 

ERROR - RPC process 6260 (nvda_slave.exe) (07:15:05.269):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 93, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1247, in GetActiveObject

  File "_ctypes/callproc.c", line 946, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

 

 

 

Andy Borka

Accessibility Engineer

 

PR with appVeyor build failing

Cyrille
 

Hello

I have submitted a PR for NVDA: #10212.
However the appVeyor build fails with the following message:

vocalizeChangeTracking 97341fe0
Failed 4 hours ago in 1 min 38 sec
Error sending GitHubPullRequest notification: Error commenting on GitHub pull request: {"message":"Validation Failed","errors":[{"resource":"IssueComment","code":"unprocessable","field":"data","message":"Body cannot be blank"}],"documentation_url":"https://developer.github.com/v3/issues/comments/#create-a-comment"}

Any idea what it is due to?
If I need to make modifications, should I push a new commit? Will the PR be updated accordingly?
In this case, do I need to squash the 2 commit or let them independant.

Moreover, new commits have been pushed to master. Should I rebase my branch on master? Or merge master into my branch? (this seconde one seems a bad idea...)

Thanks,

Cyrille

Windows 7 explorer crash.

Brian's Mail list account
 

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

Re: Windows 7 explorer crash.

Luke Davis
 

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)

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
 

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)

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

Luke Davis
 

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

I never got that reply here, its obviously been eaten by the vigin media email servers.
This does happen from time to time, sadly.
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: 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 how do you get the output into the clipboard?
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: 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
 

At the moment of course there are none available to test it with.

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

Luke Davis
 

After you run the command, press F6 to reach a read-only window of your results, then select and copy as normal.

Luke

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

OK how do you get the output into the clipboard?
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)


--
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 Cyril,

I'm not sure, but apparently, your initial comment has a Markdown formatting error in the numbered list contained in the "Testing performed" section.

Try to re-edit your initial comment by correcting this formatting error and see if it corrects the problem.

Hope this helps.

Kind regards,
Abdel.


Le 13/09/2019 à 14:50, Cyrille via Groups.Io a écrit :
Hello

I have submitted a PR for NVDA: #10212.
However the appVeyor build fails with the following message:

vocalizeChangeTracking 97341fe0
Failed 4 hours ago in 1 min 38 sec
Error sending GitHubPullRequest notification: Error commenting on GitHub pull request: {"message":"Validation Failed","errors":[{"resource":"IssueComment","code":"unprocessable","field":"data","message":"Body cannot be blank"}],"documentation_url":"https://developer.github.com/v3/issues/comments/#create-a-comment"}

Any idea what it is due to?
If I need to make modifications, should I push a new commit? Will the PR be updated accordingly?
In this case, do I need to squash the 2 commit or let them independant.

Moreover, new commits have been pushed to master. Should I rebase my branch on master? Or merge master into my branch? (this seconde one seems a bad idea...)

Thanks,

Cyrille

NVDA, Python 3 and NVDA API

Vincent Le Goff
 

Hello everyone,


With Python 3 support and NVDA 2019.3, will we have problems using the DLL files to send information to NVDA?  I mean the nvdaControllerClient.dll file.  Will it need to be rebuilt for the new version?


Thanks,


Vincent

Re: PR with appVeyor build failing

Cyrille
 

Hello Abdel

 

Thanks for replying. What is the formatting issue and how to fix it?

Actually the code portion (gestures.ini modification) is not part of the list whereas I’d prefer it to be integrated in the 1. Item. However is this a formatting error?

 

Thanks,

Cheers,

 

Cyrille

 

De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Abdel
Envoyé : dimanche 15 septembre 2019 13:19
À : nvda-devel@groups.io
Objet : Re: [nvda-devel] PR with appVeyor build failing

 

Hi Cyril,

I'm not sure, but apparently, your initial comment has a Markdown formatting error in the numbered list contained in the "Testing performed" section.

Try to re-edit your initial comment by correcting this formatting error and see if it corrects the problem.

Hope this helps.

Kind regards,
Abdel.

Le 13/09/2019 à 14:50, Cyrille via Groups.Io a écrit :

Hello

I have submitted a PR for NVDA: #10212.
However the appVeyor build fails with the following message:

vocalizeChangeTracking 97341fe0
Failed 4 hours ago in 1 min 38 sec
Error sending GitHubPullRequest notification: Error commenting on GitHub pull request: {"message":"Validation Failed","errors":[{"resource":"IssueComment","code":"unprocessable","field":"data","message":"Body cannot be blank"}],"documentation_url":"https://developer.github.com/v3/issues/comments/#create-a-comment"}

Any idea what it is due to?
If I need to make modifications, should I push a new commit? Will the PR be updated accordingly?
In this case, do I need to squash the 2 commit or let them independant.

Moreover, new commits have been pushed to master. Should I rebase my branch on master? Or merge master into my branch? (this seconde one seems a bad idea...)

Thanks,

Cyrille

Re: PR with appVeyor build failing

Cyrille
 

Hello again

 

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

Thanks,

 

Cyrille

 

De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Cyrille via Groups.Io
Envoyé : dimanche 15 septembre 2019 22:39
À : nvda-devel@groups.io
Objet : Re: [nvda-devel] PR with appVeyor build failing

 

Hello Abdel

 

Thanks for replying. What is the formatting issue and how to fix it?

Actually the code portion (gestures.ini modification) is not part of the list whereas I’d prefer it to be integrated in the 1. Item. However is this a formatting error?

 

Thanks,

Cheers,

 

Cyrille

 

De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Abdel
Envoyé : dimanche 15 septembre 2019 13:19
À : nvda-devel@groups.io
Objet : Re: [nvda-devel] PR with appVeyor build failing

 

Hi Cyril,

I'm not sure, but apparently, your initial comment has a Markdown formatting error in the numbered list contained in the "Testing performed" section.

Try to re-edit your initial comment by correcting this formatting error and see if it corrects the problem.

Hope this helps.

Kind regards,
Abdel.

Le 13/09/2019 à 14:50, Cyrille via Groups.Io a écrit :

Hello

I have submitted a PR for NVDA: #10212.
However the appVeyor build fails with the following message:

vocalizeChangeTracking 97341fe0
Failed 4 hours ago in 1 min 38 sec
Error sending GitHubPullRequest notification: Error commenting on GitHub pull request: {"message":"Validation Failed","errors":[{"resource":"IssueComment","code":"unprocessable","field":"data","message":"Body cannot be blank"}],"documentation_url":"https://developer.github.com/v3/issues/comments/#create-a-comment"}

Any idea what it is due to?
If I need to make modifications, should I push a new commit? Will the PR be updated accordingly?
In this case, do I need to squash the 2 commit or let them independant.

Moreover, new commits have been pushed to master. Should I rebase my branch on master? Or merge master into my branch? (this seconde one seems a bad idea...)

Thanks,

Cyrille

Re: PR with appVeyor build failing

 

Hi,

You need to run scons lint base=origin/master and read the output carefully.

Cheers,

Joseph

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Cyrille via Groups.Io
Sent: Sunday, September 15, 2019 2:40 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] PR with appVeyor build failing

 

Hello again

 

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

Thanks,

 

Cyrille

 

De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Cyrille via Groups.Io
Envoyé : dimanche 15 septembre 2019 22:39
À : nvda-devel@groups.io
Objet : Re: [nvda-devel] PR with appVeyor build failing

 

Hello Abdel

 

Thanks for replying. What is the formatting issue and how to fix it?

Actually the code portion (gestures.ini modification) is not part of the list whereas I’d prefer it to be integrated in the 1. Item. However is this a formatting error?

 

Thanks,

Cheers,

 

Cyrille

 

De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Abdel
Envoyé : dimanche 15 septembre 2019 13:19
À : nvda-devel@groups.io
Objet : Re: [nvda-devel] PR with appVeyor build failing

 

Hi Cyril,

I'm not sure, but apparently, your initial comment has a Markdown formatting error in the numbered list contained in the "Testing performed" section.

Try to re-edit your initial comment by correcting this formatting error and see if it corrects the problem.

Hope this helps.

Kind regards,
Abdel.

Le 13/09/2019 à 14:50, Cyrille via Groups.Io a écrit :

Hello

I have submitted a PR for NVDA: #10212.
However the appVeyor build fails with the following message:

vocalizeChangeTracking 97341fe0
Failed 4 hours ago in 1 min 38 sec
Error sending GitHubPullRequest notification: Error commenting on GitHub pull request: {"message":"Validation Failed","errors":[{"resource":"IssueComment","code":"unprocessable","field":"data","message":"Body cannot be blank"}],"documentation_url":"https://developer.github.com/v3/issues/comments/#create-a-comment"}

Any idea what it is due to?
If I need to make modifications, should I push a new commit? Will the PR be updated accordingly?
In this case, do I need to squash the 2 commit or let them independant.

Moreover, new commits have been pushed to master. Should I rebase my branch on master? Or merge master into my branch? (this seconde one seems a bad idea...)

Thanks,

Cyrille

Re: PR with appVeyor build failing

Luke Davis
 

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?

Re: PR with appVeyor build failing

derek riemer
 

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.

Brian's Mail list account
 

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

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: Sunday, September 15, 2019 11:17 AM
Subject: Re: Re Alpha build snaps not auto updating even when set to do so.... was : [nvda-devel] Windows 7 explorer crash.


After you run the command, press F6 to reach a read-only window of your results, then select and copy as normal.

Luke

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

OK how do you get the output into the clipboard?
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)




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