Date   

new version of Nvda

Brian's Mail list account
 

2020.2 beta 1 is out


Is there anything in particular which we windows 7 folk need to check?
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


Important community add-ons notice: Image Describer by Oliver Edholm is no longer maintained, replaced by Online image Describer by Larry Wang

 

Hello all,

I was notified that several NVDA users (on users list) cannot use Image Describer add-on originally developed by Oliver Edholm. The add-ons community was notified, and an add-ons reviewer suggested looking into Larry Wang’s Online Image Describer as a potential alternative (and also let our GSoC 2020 student use that add-on as basis for his project). A user also noted that he tried contacting Oliver and got no response so far.

 

Therefore, please:

 

  1. Disable Image Describer add-on (original version, not Larry’s version).
  2. Test Larry Wang’s version (found under development section on community add-ons website).

 

The add-ons community will provide further guidance once more information becomes available.

Cheers,

Joseph


Re: Finding components on an application from addon - asking for stategies and insights to do it

Luke Davis
 

Is there anything that even slightly works on Postman?

It seems on the cusp of being accessible, but doesn't pass the threshold.

On Fri, 12 Jun 2020, Marlon Brandão de Sousa wrote:

I use and appreciate your addon. This question was exactly because I wanted to send a pull request to it. Glad your are here.


I know VS Code is an electron application. What I do not know is how to, via NVDA, navigate through the accessibility tree to find and read what I need. I also do not know how to access the accessibility tree so that I know beforehand what I am looking for. This is what I am trying to figure out so that I can collaborate with addons that will work on vscode, discord and postman and other apps.


Do you have any insight?


On 12/06/2020 08:28, Pawel Urbanski wrote:
I've worked on an VS Code add-on. VSC is an Electron application. I
guess you could read though the code of Development Kit by Andy who
recently used Beautiful Soup library to parse HTML. The line number is
in teh status bar, which itself is hosted in some DIV container.
I will try to figure out if I could add line announcement to my add-on
by using textInfos offsets.
On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
Hello,
I have a need for an addom. Basically, in VSCode, I many times need to
know the line / column I am at the moment.
I know that performing now a read status line will give me this
information, but there are many other things that I don't need on the
status bar when quickly in needs to know the line / collumn positions.
Further more, this is a specific case for a generic question so that
others can also learn the strategy to achieve the goals I am trying to
reach at the moment.
Basically, when scripting an addon, we are trying to do one of three
things:
- Modify the way a given component is handled by NVDA so that it is read
correctly.
- Query information from parts of the application and present them in an
easier way for the addon user, so that they can gater needed information
that is visually easy to get but that without sight would require the
user to perform object navigation and to visit several parts of the UI
to get.
- Similarly to the above, perform clicks or other manipulations on the
UI to achieve actions that are common to the work flow of the
application but that are either inaccessible via keyboard or very hard
to perform in a productive way, many times making an efficient use of
that application not viable at all.
My need with VS Code can be classified at the item 2 of the above list.
Unfortunately I get pretty lost when achieving second and third items.
The first is achievable by using an overlay class thus overwiting the
component NVDA uses to handle a given component. About The second and
third would involve navigating through the window structure and
searching components by some kind of id and then querying information or
sending actions too that component.
In the old times when NVDA didn't exist other screen readers offered
higher level API's to do just this kind of thing. Speaking of JAWS, the
home row utility helped a lot when exploring an application internal
structure so that we could try to find an id, a class, a Window name and
such and then search for that identifier to get access to the wanted
component state. How can I do something similar via NVDA addon? Is there
any addon, any piece of the source code I should look into to start
figuring it out?
Thanks,
Marlon


Re: Finding components on an application from addon - asking for stategies and insights to do it

Pawel Urbanski
 

Unfortunately, this weekend can be tricky, but almost any day
throughout the week. Just drop me a line at: pawel@... so
we take it of this thread and do not polute the list with messages.

On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
Definitely. Tomorrow or sundae what utc are you?

Obrigado,
Marlon

Em 12 de jun de 2020, à(s) 09:26, Pawel Urbanski <pawel@...>
escreveu:

Marlon - would you mind having a Hangout call to talk about use cases
on the line of VS Code and NVDA? On a side note: I am porting my
add-on to some other IDEs. ;)

On 12/06/2020, Pawel Urbanski via groups.io
<pawel=e-urbanski.com@groups.io> wrote:
Give me this weekend to investigate. ;)

On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
I use and appreciate your addon. This question was exactly because I
wanted to send a pull request to it. Glad your are here.


I know VS Code is an electron application. What I do not know is how
to,
via NVDA, navigate through the accessibility tree to find and read what
I need. I also do not know how to access the accessibility tree so that
I know beforehand what I am looking for. This is what I am trying to
figure out so that I can collaborate with addons that will work on
vscode, discord and postman and other apps.


Do you have any insight?


On 12/06/2020 08:28, Pawel Urbanski wrote:
I've worked on an VS Code add-on. VSC is an Electron application. I
guess you could read though the code of Development Kit by Andy who
recently used Beautiful Soup library to parse HTML. The line number is
in teh status bar, which itself is hosted in some DIV container.
I will try to figure out if I could add line announcement to my add-on
by using textInfos offsets.

On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
Hello,

I have a need for an addom. Basically, in VSCode, I many times need
to
know the line / column I am at the moment.

I know that performing now a read status line will give me this
information, but there are many other things that I don't need on the
status bar when quickly in needs to know the line / collumn
positions.

Further more, this is a specific case for a generic question so that
others can also learn the strategy to achieve the goals I am trying
to
reach at the moment.

Basically, when scripting an addon, we are trying to do one of three
things:
- Modify the way a given component is handled by NVDA so that it is
read
correctly.
- Query information from parts of the application and present them in
an
easier way for the addon user, so that they can gater needed
information
that is visually easy to get but that without sight would require the
user to perform object navigation and to visit several parts of the
UI
to get.
- Similarly to the above, perform clicks or other manipulations on
the
UI to achieve actions that are common to the work flow of the
application but that are either inaccessible via keyboard or very
hard
to perform in a productive way, many times making an efficient use of
that application not viable at all.

My need with VS Code can be classified at the item 2 of the above
list.

Unfortunately I get pretty lost when achieving second and third
items.
The first is achievable by using an overlay class thus overwiting the
component NVDA uses to handle a given component. About The second and
third would involve navigating through the window structure and
searching components by some kind of id and then querying information
or
sending actions too that component.

In the old times when NVDA didn't exist other screen readers offered
higher level API's to do just this kind of thing. Speaking of JAWS,
the
home row utility helped a lot when exploring an application internal
structure so that we could try to find an id, a class, a Window name
and
such and then search for that identifier to get access to the wanted
component state. How can I do something similar via NVDA addon? Is
there
any addon, any piece of the source code I should look into to start
figuring it out?


Thanks,

Marlon













Re: Finding components on an application from addon - asking for stategies and insights to do it

Marlon Brandão de Sousa
 

Definitely. Tomorrow or sundae what utc are you?

Obrigado,
Marlon

Em 12 de jun de 2020, à(s) 09:26, Pawel Urbanski <pawel@...> escreveu:

Marlon - would you mind having a Hangout call to talk about use cases
on the line of VS Code and NVDA? On a side note: I am porting my
add-on to some other IDEs. ;)

On 12/06/2020, Pawel Urbanski via groups.io
<pawel=e-urbanski.com@groups.io> wrote:
Give me this weekend to investigate. ;)

On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
I use and appreciate your addon. This question was exactly because I
wanted to send a pull request to it. Glad your are here.


I know VS Code is an electron application. What I do not know is how to,
via NVDA, navigate through the accessibility tree to find and read what
I need. I also do not know how to access the accessibility tree so that
I know beforehand what I am looking for. This is what I am trying to
figure out so that I can collaborate with addons that will work on
vscode, discord and postman and other apps.


Do you have any insight?


On 12/06/2020 08:28, Pawel Urbanski wrote:
I've worked on an VS Code add-on. VSC is an Electron application. I
guess you could read though the code of Development Kit by Andy who
recently used Beautiful Soup library to parse HTML. The line number is
in teh status bar, which itself is hosted in some DIV container.
I will try to figure out if I could add line announcement to my add-on
by using textInfos offsets.

On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
Hello,

I have a need for an addom. Basically, in VSCode, I many times need to
know the line / column I am at the moment.

I know that performing now a read status line will give me this
information, but there are many other things that I don't need on the
status bar when quickly in needs to know the line / collumn positions.

Further more, this is a specific case for a generic question so that
others can also learn the strategy to achieve the goals I am trying to
reach at the moment.

Basically, when scripting an addon, we are trying to do one of three
things:
- Modify the way a given component is handled by NVDA so that it is
read
correctly.
- Query information from parts of the application and present them in
an
easier way for the addon user, so that they can gater needed
information
that is visually easy to get but that without sight would require the
user to perform object navigation and to visit several parts of the UI
to get.
- Similarly to the above, perform clicks or other manipulations on the
UI to achieve actions that are common to the work flow of the
application but that are either inaccessible via keyboard or very hard
to perform in a productive way, many times making an efficient use of
that application not viable at all.

My need with VS Code can be classified at the item 2 of the above list.

Unfortunately I get pretty lost when achieving second and third items.
The first is achievable by using an overlay class thus overwiting the
component NVDA uses to handle a given component. About The second and
third would involve navigating through the window structure and
searching components by some kind of id and then querying information
or
sending actions too that component.

In the old times when NVDA didn't exist other screen readers offered
higher level API's to do just this kind of thing. Speaking of JAWS, the
home row utility helped a lot when exploring an application internal
structure so that we could try to find an id, a class, a Window name
and
such and then search for that identifier to get access to the wanted
component state. How can I do something similar via NVDA addon? Is
there
any addon, any piece of the source code I should look into to start
figuring it out?


Thanks,

Marlon











Re: Finding components on an application from addon - asking for stategies and insights to do it

Pawel Urbanski
 

Marlon - would you mind having a Hangout call to talk about use cases
on the line of VS Code and NVDA? On a side note: I am porting my
add-on to some other IDEs. ;)

On 12/06/2020, Pawel Urbanski via groups.io
<pawel=e-urbanski.com@groups.io> wrote:
Give me this weekend to investigate. ;)

On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
I use and appreciate your addon. This question was exactly because I
wanted to send a pull request to it. Glad your are here.


I know VS Code is an electron application. What I do not know is how to,
via NVDA, navigate through the accessibility tree to find and read what
I need. I also do not know how to access the accessibility tree so that
I know beforehand what I am looking for. This is what I am trying to
figure out so that I can collaborate with addons that will work on
vscode, discord and postman and other apps.


Do you have any insight?


On 12/06/2020 08:28, Pawel Urbanski wrote:
I've worked on an VS Code add-on. VSC is an Electron application. I
guess you could read though the code of Development Kit by Andy who
recently used Beautiful Soup library to parse HTML. The line number is
in teh status bar, which itself is hosted in some DIV container.
I will try to figure out if I could add line announcement to my add-on
by using textInfos offsets.

On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
Hello,

I have a need for an addom. Basically, in VSCode, I many times need to
know the line / column I am at the moment.

I know that performing now a read status line will give me this
information, but there are many other things that I don't need on the
status bar when quickly in needs to know the line / collumn positions.

Further more, this is a specific case for a generic question so that
others can also learn the strategy to achieve the goals I am trying to
reach at the moment.

Basically, when scripting an addon, we are trying to do one of three
things:
- Modify the way a given component is handled by NVDA so that it is
read
correctly.
- Query information from parts of the application and present them in
an
easier way for the addon user, so that they can gater needed
information
that is visually easy to get but that without sight would require the
user to perform object navigation and to visit several parts of the UI
to get.
- Similarly to the above, perform clicks or other manipulations on the
UI to achieve actions that are common to the work flow of the
application but that are either inaccessible via keyboard or very hard
to perform in a productive way, many times making an efficient use of
that application not viable at all.

My need with VS Code can be classified at the item 2 of the above list.

Unfortunately I get pretty lost when achieving second and third items.
The first is achievable by using an overlay class thus overwiting the
component NVDA uses to handle a given component. About The second and
third would involve navigating through the window structure and
searching components by some kind of id and then querying information
or
sending actions too that component.

In the old times when NVDA didn't exist other screen readers offered
higher level API's to do just this kind of thing. Speaking of JAWS, the
home row utility helped a lot when exploring an application internal
structure so that we could try to find an id, a class, a Window name
and
such and then search for that identifier to get access to the wanted
component state. How can I do something similar via NVDA addon? Is
there
any addon, any piece of the source code I should look into to start
figuring it out?


Thanks,

Marlon










Re: Finding components on an application from addon - asking for stategies and insights to do it

Pawel Urbanski
 

Give me this weekend to investigate. ;)

On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
I use and appreciate your addon. This question was exactly because I
wanted to send a pull request to it. Glad your are here.


I know VS Code is an electron application. What I do not know is how to,
via NVDA, navigate through the accessibility tree to find and read what
I need. I also do not know how to access the accessibility tree so that
I know beforehand what I am looking for. This is what I am trying to
figure out so that I can collaborate with addons that will work on
vscode, discord and postman and other apps.


Do you have any insight?


On 12/06/2020 08:28, Pawel Urbanski wrote:
I've worked on an VS Code add-on. VSC is an Electron application. I
guess you could read though the code of Development Kit by Andy who
recently used Beautiful Soup library to parse HTML. The line number is
in teh status bar, which itself is hosted in some DIV container.
I will try to figure out if I could add line announcement to my add-on
by using textInfos offsets.

On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
Hello,

I have a need for an addom. Basically, in VSCode, I many times need to
know the line / column I am at the moment.

I know that performing now a read status line will give me this
information, but there are many other things that I don't need on the
status bar when quickly in needs to know the line / collumn positions.

Further more, this is a specific case for a generic question so that
others can also learn the strategy to achieve the goals I am trying to
reach at the moment.

Basically, when scripting an addon, we are trying to do one of three
things:
- Modify the way a given component is handled by NVDA so that it is read
correctly.
- Query information from parts of the application and present them in an
easier way for the addon user, so that they can gater needed information
that is visually easy to get but that without sight would require the
user to perform object navigation and to visit several parts of the UI
to get.
- Similarly to the above, perform clicks or other manipulations on the
UI to achieve actions that are common to the work flow of the
application but that are either inaccessible via keyboard or very hard
to perform in a productive way, many times making an efficient use of
that application not viable at all.

My need with VS Code can be classified at the item 2 of the above list.

Unfortunately I get pretty lost when achieving second and third items.
The first is achievable by using an overlay class thus overwiting the
component NVDA uses to handle a given component. About The second and
third would involve navigating through the window structure and
searching components by some kind of id and then querying information or
sending actions too that component.

In the old times when NVDA didn't exist other screen readers offered
higher level API's to do just this kind of thing. Speaking of JAWS, the
home row utility helped a lot when exploring an application internal
structure so that we could try to find an id, a class, a Window name and
such and then search for that identifier to get access to the wanted
component state. How can I do something similar via NVDA addon? Is there
any addon, any piece of the source code I should look into to start
figuring it out?


Thanks,

Marlon








Re: Finding components on an application from addon - asking for stategies and insights to do it

Marlon Brandão de Sousa
 

I use and appreciate your addon. This question was exactly because I wanted to send a pull request to it. Glad your are here.


I know VS Code is an electron application. What I do not know is how to, via NVDA, navigate through the accessibility tree to find and read what I need. I also do not know how to access the accessibility tree so that I know beforehand what I am looking for. This is what I am trying to figure out so that I can collaborate with addons that will work on vscode, discord and postman and other apps.


Do you have any insight?

On 12/06/2020 08:28, Pawel Urbanski wrote:
I've worked on an VS Code add-on. VSC is an Electron application. I
guess you could read though the code of Development Kit by Andy who
recently used Beautiful Soup library to parse HTML. The line number is
in teh status bar, which itself is hosted in some DIV container.
I will try to figure out if I could add line announcement to my add-on
by using textInfos offsets.

On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
Hello,

I have a need for an addom. Basically, in VSCode, I many times need to
know the line / column I am at the moment.

I know that performing now a read status line will give me this
information, but there are many other things that I don't need on the
status bar when quickly in needs to know the line / collumn positions.

Further more, this is a specific case for a generic question so that
others can also learn the strategy to achieve the goals I am trying to
reach at the moment.

Basically, when scripting an addon, we are trying to do one of three
things:
- Modify the way a given component is handled by NVDA so that it is read
correctly.
- Query information from parts of the application and present them in an
easier way for the addon user, so that they can gater needed information
that is visually easy to get but that without sight would require the
user to perform object navigation and to visit several parts of the UI
to get.
- Similarly to the above, perform clicks or other manipulations on the
UI to achieve actions that are common to the work flow of the
application but that are either inaccessible via keyboard or very hard
to perform in a productive way, many times making an efficient use of
that application not viable at all.

My need with VS Code can be classified at the item 2 of the above list.

Unfortunately I get pretty lost when achieving second and third items.
The first is achievable by using an overlay class thus overwiting the
component NVDA uses to handle a given component. About The second and
third would involve navigating through the window structure and
searching components by some kind of id and then querying information or
sending actions too that component.

In the old times when NVDA didn't exist other screen readers offered
higher level API's to do just this kind of thing. Speaking of JAWS, the
home row utility helped a lot when exploring an application internal
structure so that we could try to find an id, a class, a Window name and
such and then search for that identifier to get access to the wanted
component state. How can I do something similar via NVDA addon? Is there
any addon, any piece of the source code I should look into to start
figuring it out?


Thanks,

Marlon






Re: Finding components on an application from addon - asking for stategies and insights to do it

Pawel Urbanski
 

I've worked on an VS Code add-on. VSC is an Electron application. I
guess you could read though the code of Development Kit by Andy who
recently used Beautiful Soup library to parse HTML. The line number is
in teh status bar, which itself is hosted in some DIV container.
I will try to figure out if I could add line announcement to my add-on
by using textInfos offsets.

On 12/06/2020, Marlon Brandão de Sousa <splyt.lists@...> wrote:
Hello,

I have a need for an addom. Basically, in VSCode, I many times need to
know the line / column I am at the moment.

I know that performing now a read status line will give me this
information, but there are many other things that I don't need on the
status bar when quickly in needs to know the line / collumn positions.

Further more, this is a specific case for a generic question so that
others can also learn the strategy to achieve the goals I am trying to
reach at the moment.

Basically, when scripting an addon, we are trying to do one of three
things:
- Modify the way a given component is handled by NVDA so that it is read
correctly.
- Query information from parts of the application and present them in an
easier way for the addon user, so that they can gater needed information
that is visually easy to get but that without sight would require the
user to perform object navigation and to visit several parts of the UI
to get.
- Similarly to the above, perform clicks or other manipulations on the
UI to achieve actions that are common to the work flow of the
application but that are either inaccessible via keyboard or very hard
to perform in a productive way, many times making an efficient use of
that application not viable at all.

My need with VS Code can be classified at the item 2 of the above list.

Unfortunately I get pretty lost when achieving second and third items.
The first is achievable by using an overlay class thus overwiting the
component NVDA uses to handle a given component. About The second and
third would involve navigating through the window structure and
searching components by some kind of id and then querying information or
sending actions too that component.

In the old times when NVDA didn't exist other screen readers offered
higher level API's to do just this kind of thing. Speaking of JAWS, the
home row utility helped a lot when exploring an application internal
structure so that we could try to find an id, a class, a Window name and
such and then search for that identifier to get access to the wanted
component state. How can I do something similar via NVDA addon? Is there
any addon, any piece of the source code I should look into to start
figuring it out?


Thanks,

Marlon






Finding components on an application from addon - asking for stategies and insights to do it

Marlon Brandão de Sousa
 

Hello,

I have a need for an addom. Basically, in VSCode, I many times need to know the line / column I am at the moment.

I know that performing now a read status line will give me this information, but there are many other things that I don't need on the status bar when quickly in needs to know the line / collumn positions.

Further more, this is a specific case for a generic question so that others can also learn the strategy to achieve the goals I am trying to reach at the moment.

Basically, when scripting an addon, we are trying to do one of three things:
- Modify the way a given component is handled by NVDA so that it is read correctly.
- Query information from parts of the application and present them in an easier way for the addon user, so that they can gater needed information that is visually easy to get but that without sight would require the user to perform object navigation and to visit several parts of the UI to get.
- Similarly to the above, perform clicks or other manipulations on the UI to achieve actions that are common to the work flow of the application but that are either inaccessible via keyboard or very hard to perform in a productive way, many times making an efficient use of that application not viable at all.

My need with VS Code can be classified at the item 2 of the above list.

Unfortunately I get pretty lost when achieving second and third items. The first is achievable by using an overlay class thus overwiting the component NVDA uses to handle a given component. About The second and third would involve navigating through the window structure and searching components by some kind of id and then querying information or sending actions too that component.

In the old times when NVDA didn't exist other screen readers offered higher level API's to do just this kind of thing. Speaking of JAWS, the home row utility helped a lot when exploring an application internal structure so that we could try to find an id, a class, a Window name and such and then search for that identifier to get access to the wanted component state. How can I do something similar via NVDA addon? Is there any addon, any piece of the source code I should look into to start figuring it out?


Thanks,

Marlon


Re: Auto language switching - Voice selection

Deenadayalan Moodley
 

Hi,

 

I want to add that I would like to see the ability to specify speech synth, and the voice to be used.  At this stage, if you have a number of voices, NVDA just picks the first one and uses it.  This is not always the best one for the job.

 

I did send a sample to NVDA where even things like Language tags in headings in tables is not being honoured.

 

Thanks.

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Julien Cochuyt
Sent: Thursday, 11 June 2020 17:38
To: nvda-devel@groups.io
Subject: [nvda-devel] Auto language switching - Voice selection

 

Dear all,

 

Does anyone know how to influence the selected voice when automatic language switching occurs?

In case this is synth-specific, the request comes from a customer using Microsoft OneCore as his primary synth.

Still, I'd be personally interested by info for other synth drivers, like eSpeak (my own daily horse) or SAPI 5.

I know there are some efforts made towards generalizing language detection and switching synth altogether (#279 / Dual Voice), but these go far beyond the simple configuration problem my customer is facing, which is comfortably reading his well tagged English/French/German documents.

 


Best regards,

 

Julien Cochuyt

Accessolutions


Joining Speech Chunks

Michael Chen
 

Hello All,


I've noticed with the new speech framework, the last spoken item in the NVDA log is now split into chunks of the spoken text. For example:


Speaking ['User Promoted Notification Area', 'tool bar']


I am used to using regular expressions in the speech dictionaries to customize commonly spoken text. In this example, I previously had a regular expression entry that would silence this text, but now with the "tool bar' chunk split off, I can nolonger match that part of the spoken text.


Is there any way to match the entire spoken list of chunks using the speech dictionary regular expressions?


Thanks for any help.


Sincerely,

Michael


Auto language switching - Voice selection

Julien Cochuyt
 

Dear all,

Does anyone know how to influence the selected voice when automatic language switching occurs?
In case this is synth-specific, the request comes from a customer using Microsoft OneCore as his primary synth.
Still, I'd be personally interested by info for other synth drivers, like eSpeak (my own daily horse) or SAPI 5.

I know there are some efforts made towards generalizing language detection and switching synth altogether (#279 / Dual Voice), but these go far beyond the simple configuration problem my customer is facing, which is comfortably reading his well tagged English/French/German documents.


Best regards,

Julien Cochuyt
Accessolutions


Re: WXPython Submodule Issue When Running From Source

Nathaniel Schmidt
 

Hi Joseph,

Works now. Thanks.

On 10 Jun 2020, at 2:15 am, Joseph Lee <@joslee> wrote:

Hi,
Because wxPython includes C extension code (pyd file), you'll need to run Python 3.7 specific and 32-bit wxPython 4.0.3.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Nathaniel Schmidt
Sent: Thursday, June 4, 2020 1:59 AM
To: nvda-devel@groups.io
Subject: [nvda-devel] WXPython Submodule Issue When Running From Source

Hi all,

I am not sure how simple or difficult this problem is to fix but I am trying to run NVDA from source, and the following problem has been encountered when executing pythonw nvda.pyw from the command line. Is anyone able to help? Also sorry if there is already a topic on this
issue: I have been off the list temporarily. I thought I would post here to see if anyone else is having the issue before creating one on
GitHub:

From log:
---begin---
INFO - __main__ (18:25:49.265) - MainThread (23044):
Starting NVDA version source-master-44d8a31 CRITICAL - __main__ (18:25:49.940) - MainThread (23044):
core failure
Traceback (most recent call last):
File "nvda.pyw", line 214, in <module>
import core
File "core.py", line 31, in <module>
import nvwave
File "nvwave.py", line 15, in <module>
import wx
File "c:\GitInit\njsch\nvda\include\wxPython\wx\__init__.py", line 17, in <module>
from wx.core import *
File "c:\GitInit\njsch\nvda\include\wxPython\wx\core.py", line 12, in <module>
from ._core import *
ModuleNotFoundError: No module named 'wx._core'
--end---

At face-value, this sounds to me like a dependency-specific issue with WXPython's code.
Is anyone else having this issue? Has the classic WXPython submodule been updated recently?

Also, please note that I have set my cloned njsch/nvda/master branch to remote-track nvaccess/nvda/master.

Should I pip uninstall wxpython? I don't think I installed it before successfully creating my python virtual environment for the NVDA source distribution. Although under the circumstances, I don't really see how this would make a difference, since the log history indicates that the nvwave module is looking in the Git submodule-included dependency directory anyway.

Kind regards,

Nathaniel Schmidt






Re: WXPython Submodule Issue When Running From Source

Nathaniel Schmidt
 

Hi Lukasz,

I have both editions installed but I did use the wrong one via the system environment variable...

Nathaniel

On 10 Jun 2020, at 4:31 am, Lukasz Golonka <lukasz.golonka@...> wrote:

Hello,

It looks like you've launched NVDA with the wrong version of Python -
NVDA can be started only with 3.7 32-bit.

--
Regards
Lukasz

On Thu, 4 Jun 2020 18:59:15 +1000
"Nathaniel Schmidt" <schmidty2244@...> wrote:

Hi all,

I am not sure how simple or difficult this problem is to fix but I am
trying to run NVDA from source, and the following problem has been
encountered when executing pythonw nvda.pyw from the command line. Is
anyone able to help? Also sorry if there is already a topic on this
issue: I have been off the list temporarily. I thought I would post
here to see if anyone else is having the issue before creating one on
GitHub:

From log:
---begin---
INFO - __main__ (18:25:49.265) - MainThread (23044):
Starting NVDA version source-master-44d8a31
CRITICAL - __main__ (18:25:49.940) - MainThread (23044):
core failure
Traceback (most recent call last):
File "nvda.pyw", line 214, in <module>
import core
File "core.py", line 31, in <module>
import nvwave
File "nvwave.py", line 15, in <module>
import wx
File "c:\GitInit\njsch\nvda\include\wxPython\wx\__init__.py", line
17, in <module>
from wx.core import *
File "c:\GitInit\njsch\nvda\include\wxPython\wx\core.py", line 12, in <module>
from ._core import *
ModuleNotFoundError: No module named 'wx._core'
--end---

At face-value, this sounds to me like a dependency-specific issue with
WXPython's code.
Is anyone else having this issue? Has the classic WXPython submodule
been updated recently?

Also, please note that I have set my cloned njsch/nvda/master branch
to remote-track nvaccess/nvda/master.

Should I pip uninstall wxpython? I don't think I installed it before
successfully creating my python virtual environment for the NVDA
source distribution. Although under the circumstances, I don't really
see how this would make a difference, since the log history indicates
that the nvwave module is looking in the Git submodule-included
dependency directory anyway.

Kind regards,

Nathaniel Schmidt




Re: WXPython Submodule Issue When Running From Source

Lukasz Golonka
 

Hello,

It looks like you've launched NVDA with the wrong version of Python -
NVDA can be started only with 3.7 32-bit.

--
Regards
Lukasz

On Thu, 4 Jun 2020 18:59:15 +1000
"Nathaniel Schmidt" <schmidty2244@...> wrote:

Hi all,

I am not sure how simple or difficult this problem is to fix but I am
trying to run NVDA from source, and the following problem has been
encountered when executing pythonw nvda.pyw from the command line. Is
anyone able to help? Also sorry if there is already a topic on this
issue: I have been off the list temporarily. I thought I would post
here to see if anyone else is having the issue before creating one on
GitHub:

From log:
---begin---
INFO - __main__ (18:25:49.265) - MainThread (23044):
Starting NVDA version source-master-44d8a31
CRITICAL - __main__ (18:25:49.940) - MainThread (23044):
core failure
Traceback (most recent call last):
File "nvda.pyw", line 214, in <module>
import core
File "core.py", line 31, in <module>
import nvwave
File "nvwave.py", line 15, in <module>
import wx
File "c:\GitInit\njsch\nvda\include\wxPython\wx\__init__.py", line
17, in <module>
from wx.core import *
File "c:\GitInit\njsch\nvda\include\wxPython\wx\core.py", line 12, in <module>
from ._core import *
ModuleNotFoundError: No module named 'wx._core'
--end---

At face-value, this sounds to me like a dependency-specific issue with
WXPython's code.
Is anyone else having this issue? Has the classic WXPython submodule
been updated recently?

Also, please note that I have set my cloned njsch/nvda/master branch
to remote-track nvaccess/nvda/master.

Should I pip uninstall wxpython? I don't think I installed it before
successfully creating my python virtual environment for the NVDA
source distribution. Although under the circumstances, I don't really
see how this would make a difference, since the log history indicates
that the nvwave module is looking in the Git submodule-included
dependency directory anyway.

Kind regards,

Nathaniel Schmidt


Re: WXPython Submodule Issue When Running From Source

 

Hi,
Because wxPython includes C extension code (pyd file), you'll need to run Python 3.7 specific and 32-bit wxPython 4.0.3.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Nathaniel Schmidt
Sent: Thursday, June 4, 2020 1:59 AM
To: nvda-devel@groups.io
Subject: [nvda-devel] WXPython Submodule Issue When Running From Source

Hi all,

I am not sure how simple or difficult this problem is to fix but I am trying to run NVDA from source, and the following problem has been encountered when executing pythonw nvda.pyw from the command line. Is anyone able to help? Also sorry if there is already a topic on this
issue: I have been off the list temporarily. I thought I would post here to see if anyone else is having the issue before creating one on
GitHub:

From log:
---begin---
INFO - __main__ (18:25:49.265) - MainThread (23044):
Starting NVDA version source-master-44d8a31 CRITICAL - __main__ (18:25:49.940) - MainThread (23044):
core failure
Traceback (most recent call last):
File "nvda.pyw", line 214, in <module>
import core
File "core.py", line 31, in <module>
import nvwave
File "nvwave.py", line 15, in <module>
import wx
File "c:\GitInit\njsch\nvda\include\wxPython\wx\__init__.py", line 17, in <module>
from wx.core import *
File "c:\GitInit\njsch\nvda\include\wxPython\wx\core.py", line 12, in <module>
from ._core import *
ModuleNotFoundError: No module named 'wx._core'
--end---

At face-value, this sounds to me like a dependency-specific issue with WXPython's code.
Is anyone else having this issue? Has the classic WXPython submodule been updated recently?

Also, please note that I have set my cloned njsch/nvda/master branch to remote-track nvaccess/nvda/master.

Should I pip uninstall wxpython? I don't think I installed it before successfully creating my python virtual environment for the NVDA source distribution. Although under the circumstances, I don't really see how this would make a difference, since the log history indicates that the nvwave module is looking in the Git submodule-included dependency directory anyway.

Kind regards,

Nathaniel Schmidt


WXPython Submodule Issue When Running From Source

Nathaniel Schmidt
 

Hi all,

I am not sure how simple or difficult this problem is to fix but I am
trying to run NVDA from source, and the following problem has been
encountered when executing pythonw nvda.pyw from the command line. Is
anyone able to help? Also sorry if there is already a topic on this
issue: I have been off the list temporarily. I thought I would post
here to see if anyone else is having the issue before creating one on
GitHub:

From log:
---begin---
INFO - __main__ (18:25:49.265) - MainThread (23044):
Starting NVDA version source-master-44d8a31
CRITICAL - __main__ (18:25:49.940) - MainThread (23044):
core failure
Traceback (most recent call last):
File "nvda.pyw", line 214, in <module>
import core
File "core.py", line 31, in <module>
import nvwave
File "nvwave.py", line 15, in <module>
import wx
File "c:\GitInit\njsch\nvda\include\wxPython\wx\__init__.py", line
17, in <module>
from wx.core import *
File "c:\GitInit\njsch\nvda\include\wxPython\wx\core.py", line 12, in <module>
from ._core import *
ModuleNotFoundError: No module named 'wx._core'
--end---

At face-value, this sounds to me like a dependency-specific issue with
WXPython's code.
Is anyone else having this issue? Has the classic WXPython submodule
been updated recently?

Also, please note that I have set my cloned njsch/nvda/master branch
to remote-track nvaccess/nvda/master.

Should I pip uninstall wxpython? I don't think I installed it before
successfully creating my python virtual environment for the NVDA
source distribution. Although under the circumstances, I don't really
see how this would make a difference, since the log history indicates
that the nvwave module is looking in the Git submodule-included
dependency directory anyway.

Kind regards,

Nathaniel Schmidt


The read lloud voices in edge

Brian's Mail list account
 

I notice these are very good and seem to work well on windows 7. I don't suppose Microsoft offer any way to use these voices outside of Edge? It would be great if they did as a say all voice for example outside of the browser.
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: PowerShell not found error

Cyrille
 

Hello

I am posting this thread on the nvda-devel mailing list since it seems more adapted.

I tried to build on last parent commits master~4, master~2 and master~1. It worked well.

Then I have turned back to master and it builds well... Very strange.

Cyrille

Le 04/06/2020 à 15:51, Lukasz Golonka a écrit :
Hello Cyrille,

On Thu, 4 Jun 2020 11:08:05 +0200
"Cyrille via groups.io" <cyrille.bougot2=laposte.net@groups.io> wrote:

i Lukasz

I have installed scons as you did and it is now working on add-on builds.


Regarding NVDA build, I get the following error log:


scons: Reading SConscript files ...
TypeError: find_vc_pdir() missing 1 required positional argument: 'msvc_version'
:
  File "D:\Cyrille\DevP\nvdaNew2\SConstruct", line 236:
env32.SConscript('nvdaHelper/archBuild_sconscript',exports={'env':env32,'cli
entInstallDir':clientDir.Dir('x86'),'libInstallDir':sourceLibDir},variant_dir='b
uild/x86')
  File "c:\users\cyrille\appdata\local\programs\python\python37-32\lib\site-pack
ages\scons\SCons\Script\SConscript.py", line 597:
    return _SConscript(self.fs, *files, **subst_kw)
  File "c:\users\cyrille\appdata\local\programs\python\python37-32\lib\site-pack
ages\scons\SCons\Script\SConscript.py", line 286:
    exec(compile(scriptdata, scriptname, 'exec'), call_stack[-1].globals)
  File "D:\Cyrille\DevP\nvdaNew2\build\x86\archBuild_sconscript", line 190:
    win10localLib=env.SConscript('localWin10/sconscript',)
  File "c:\users\cyrille\appdata\local\programs\python\python37-32\lib\site-pack
ages\scons\SCons\Script\SConscript.py", line 597:
    return _SConscript(self.fs, *files, **subst_kw)
  File "c:\users\cyrille\appdata\local\programs\python\python37-32\lib\site-pack
ages\scons\SCons\Script\SConscript.py", line 286:
    exec(compile(scriptdata, scriptname, 'exec'), call_stack[-1].globals)
  File "D:\Cyrille\DevP\nvdaNew2\build\x86\localWin10\sconscript", line 46:
    find_vc_pdir(msvc),

Do you think it is linked or is it totally something else?
Huh, it turns out I also cannot build NVDA with latest master of Scons -
I had slightly older version installed previously. It is a change in
Scons which unfortunately breaks NVDA's Sconscripts.