Some programs don't track properly in terms of where the mouse should be
when you move it. Others who may know more may have suggestions. I imagine
the sighted person is asking you about focus because they are trying to
learn what you are doing. Isn't there a way that a sighted user can see
what a blind person is doing in terms of their position on screen? Not
where the mouse is, but where they are working. If that is correct, could
that feature be used instead of the unreliable mouse tracking that evidently
exists in the program?

Gene
----- Original Message -----

From: aikeo koomanivong
Sent: Thursday, September 20, 2018 7:41 PM
To: nvda
Subject: [nvda] mouse cursor and NVDA cursor problems.


Dear all
I’m using NVDA for training Daisy book making with Obie software
While training, sighted person always asking me for where’s the mouse
cursor focus but NVDA speaking correctly.
I’m trying to Move mouse to current navigator object by pressing
NVDA+shift+m [laptop layout]
but not really working
Looking for your comments.
regards


--
AIKEO KOOMANIVONG
CFBT-ICEVI coordinator of LAO PDR.
vise president
accessible ICT and musical development for the blind

Vocational development for LAO-blind association [VDBA]
Office e-mail: vdba.lao@gmail.com
Facebook page:
www.facebook.com/laoblind.org
my personal e-mail: mlp_keo@yahoo.com
skype name: peba_007
mobile phone: +8562099993423
Facebook:
www.facebook.com/keo.laoblind
Linkedin:
https://www.linkedin.com/pub/aikeo-koomanivong/a7/156/b8b

Hi everyone,

Although the below post is a bit technical, please keep an eye on it. You won’t feel the impact of what I outline regarding Python 3 transition for a while, but when it does, please listen to notices from NV Access and add-on authors regarding Python 3. And no, wxPython 4 is not the same thing as Python 3.

Thanks.

Dear NVDA development and add-ons communities:

This is Joseph Lee, a student at California State University, Los Angeles and a long-time NVDA add-on author and code contributor. I’d like to announce some important updates regarding Project Pylennium.

For a while, some NVDA developers (mostly third-party contributors) have been working on how to bring Project Pylennium – Python 3 transition – to life. After much discussion, NV Access and other developers agreed to wait until a stable NVDA version powered by wxPython 4.0.3 (Phoenix) is released before working on this project. Now that NVDA 2018.3.x (powered by wxPython 4) has been released, it is time to move forward with this project a bit, starting with pre-transition activities.

To kick this off, I’m delighted to announce that a prototype archive of NVDA source code and dependencies powered by Python 3 is now available. Apart from removal of data generated by SCons, the archive is ready to run on Python 3.7 with some preparations, and… are you ready for it: IT RUNS! Well, I must add that there are some important features missing or not working as intended, but I’m sure this will be rectified as the project moves forward.

Note that the archive is a prototype – please do not test this unless your intention is to provide contributions to Python 3 transition workflow once NV Access is ready to accept pull requests.

Archive link:

https://www.josephsl.net/files/pylennium/nvdapy37.zip

Things working:

• Windows OneCore synthesizer
• Python Console
• Sending log output to log file
• Object navigation commands
• Commands to configure options (NVDA+number row 2, for instance)
• Loading app modules

Things to be aware of:

• Requires Windows 10 until Espeak NG is ready.
• NVDA menu won’t open due to division operator differences between Python 2 nad 3
• Add-ons won’t load
• Certain synth settings ring commands won’t work
• Some braille displays won’t work

The idea is to let seasoned developers (preferably third-party contributors and/or a group of mainstream Python developers) test ideas and porting issues and report their findings to NV Access. In turn, when it comes time to actually transition NVDA source code and add-ons to Python 3, data can be used to guide future work.

Second, a wiki page is being written to help you all move smoothly to Python 3 and to coordinate this workflow. The document is subject to change based on progress of pre-transition activities. The page in its current form can be found at:

https://github.com/nvaccess/nvda/wiki/nvdapy3

As always, the umbrella issue on Python 3 transition can be found on GitHub at:

https://github.com/nvaccess/nvda/issues/7105

Along with other issues having “python 3” label added to them.

Lastly, I’d like to announce that I’m stepping back from Python 3 transition workflow at this time (and, for that matter, NVDA code contributions for a while). Besides automatic braille display detection (written by Babbage B.V.) and various Windows 10 features support (mostly my work), the biggest change (and the most controversial one) in NVDA 2018.3.x has been moving to wxPython 4 (mostly my work with assistance from many). The results matched my predictions from earlier this year: some notable add-ons not being compatible with wxPython 4, hence notices throughout this summer (winter for those living in southern hemisphere).

At the moment I have mixed feelings about how we (NvDA community) handled this change. Yes, wxPython 4 is a necessary stepping stone for moving to Python 3, and yes, I understand that I was rather forceful in handling certain parts of this journey. There are good things we did, and lessons we have learned so we can make Python 3 transition a smoother experience. Even for me, it was an interesting ride for the last three years (wxPython Phoenix research began in 2015), and I know that I could have done things better.

Recently, I hinted to some that my time as an active contributor to NVDA screen reader is slowly coming to a close. As a first step, I’d like to ask that the community take an initiative to move forward with Python 3 transition (including other pre-transition activities); I feel that the best thing I can do for this work now is to provide the prototype archive and a vision for its conclusion, along with some pull requests (one of them is pending review). There is a feature I’d like to present as a token of appreciation to those who’ve helped me for the past six years: add-on update checks, which will be impacted by Python 3 transition as well. But this does not mean I’m leaving the community: I’ll still be around to give advice regarding Project Pylennium.

Thank you.

Cheers,

Joseph

Dear NVDA development and add-ons communities:

This is Joseph Lee, a student at California State University, Los Angeles and a long-time NVDA add-on author and code contributor. I’d like to announce some important updates regarding Project Pylennium.

For a while, some NVDA developers (mostly third-party contributors) have been working on how to bring Project Pylennium – Python 3 transition – to life. After much discussion, NV Access and other developers agreed to wait until a stable NVDA version powered by wxPython 4.0.3 (Phoenix) is released before working on this project. Now that NVDA 2018.3.x (powered by wxPython 4) has been released, it is time to move forward with this project a bit, starting with pre-transition activities.

To kick this off, I’m delighted to announce that a prototype archive of NVDA source code and dependencies powered by Python 3 is now available. Apart from removal of data generated by SCons, the archive is ready to run on Python 3.7 with some preparations, and… are you ready for it: IT RUNS! Well, I must add that there are some important features missing or not working as intended, but I’m sure this will be rectified as the project moves forward.

Note that the archive is a prototype – please do not test this unless your intention is to provide contributions to Python 3 transition workflow once NV Access is ready to accept pull requests.

Archive link:

https://www.josephsl.net/files/pylennium/nvdapy37.zip

Things working:

• Windows OneCore synthesizer
• Python Console
• Sending log output to log file
• Object navigation commands
• Commands to configure options (NVDA+number row 2, for instance)
• Loading app modules

Things to be aware of:

• Requires Windows 10 until Espeak NG is ready.
• NVDA menu won’t open due to division operator differences between Python 2 nad 3
• Add-ons won’t load
• Certain synth settings ring commands won’t work
• Some braille displays won’t work

The idea is to let seasoned developers (preferably third-party contributors and/or a group of mainstream Python developers) test ideas and porting issues and report their findings to NV Access. In turn, when it comes time to actually transition NVDA source code and add-ons to Python 3, data can be used to guide future work.

Second, a wiki page is being written to help you all move smoothly to Python 3 and to coordinate this workflow. The document is subject to change based on progress of pre-transition activities. The page in its current form can be found at:

https://github.com/nvaccess/nvda/wiki/nvdapy3

As always, the umbrella issue on Python 3 transition can be found on GitHub at:

https://github.com/nvaccess/nvda/issues/7105

Along with other issues having “python 3” label added to them.

Lastly, I’d like to announce that I’m stepping back from Python 3 transition workflow at this time (and, for that matter, NVDA code contributions for a while). Besides automatic braille display detection (written by Babbage B.V.) and various Windows 10 features support (mostly my work), the biggest change (and the most controversial one) in NVDA 2018.3.x has been moving to wxPython 4 (mostly my work with assistance from many). The results matched my predictions from earlier this year: some notable add-ons not being compatible with wxPython 4, hence notices throughout this summer (winter for those living in southern hemisphere).

At the moment I have mixed feelings about how we (NvDA community) handled this change. Yes, wxPython 4 is a necessary stepping stone for moving to Python 3, and yes, I understand that I was rather forceful in handling certain parts of this journey. There are good things we did, and lessons we have learned so we can make Python 3 transition a smoother experience. Even for me, it was an interesting ride for the last three years (wxPython Phoenix research began in 2015), and I know that I could have done things better.

Recently, I hinted to some that my time as an active contributor to NVDA screen reader is slowly coming to a close. As a first step, I’d like to ask that the community take an initiative to move forward with Python 3 transition (including other pre-transition activities); I feel that the best thing I can do for this work now is to provide the prototype archive and a vision for its conclusion, along with some pull requests (one of them is pending review). There is a feature I’d like to present as a token of appreciation to those who’ve helped me for the past six years: add-on update checks, which will be impacted by Python 3 transition as well. But this does not mean I’m leaving the community: I’ll still be around to give advice regarding Project Pylennium.

Thank you.

Cheers,

Joseph

--

Hello,

I am teaching myself Python, and C Sharp, and have just downloaded and installed the Free Microsoft Visual Studio 2017.

NVDA and Jaws 2018 will read some things in Visual Studio, and was wondering if any here use Visual Studio to do your programing?

I am either using it wrong, or not enough is getting read by either Screen Reader. So am asking if any here use this program to do your programing.


Thanks again, for any reply,

Dave

Hello,

I am teaching myself Python, and C Sharp, and have just downloaded and installed the Free Microsoft Visual Studio 2017.

NVDA and Jaws 2018 will read some things in Visual Studio, and was wondering if any here use Visual Studio to do your programing?

I am either using it wrong, or not enough is getting read by either Screen Reader. So am asking if any here use this program to do your programing.


Thanks again, for any reply,

Dave

Hi Dave,


As far as the NVDA total uninstall, as with most programs, you should do the normal uninstall routine and then delete the folders under programs file or program files X86 and/or program data that refer to NVDA.


As far as the issue with Code Factory voices, the website for that check up seems to have issues. E-mail the owners and tell them that you are having issues with the serial number/installation. They will fix it at their end. It happened to me twice so far when I installed the voices on a different system after a crash.



On 9/20/2018 9:59 AM, Dave wrote:

Hello,

Am New to the List, and have a couple of Questions that will be covered in this, and another post.

I am having problems reinstalling NVDA to a Win 7 64 bit System.

It was installed and working fine. Then I purchased the Code Factory Voices, and this is when I started to have issues.

I installed the Code Factory voices, and inserted the Authorization Key, so the Voices would work correctly.

However, when ever I started up NVDA, it would start, but I would always receive a Code Factory Message telling me that the 30 Day Demo of the voices has Expired, and that I would need to purchase the Code Factory voices if I wanted to use them.

I had already purchased them, installed them, and installed the Authorization key. And when I Clicked on the OK to make the message go away, NVDA and the Selected Code Factory Voice would work as it should.

Well, I wanted to clean up the false warning message, so I thought of re-installing the Authorization key. This hade no effect on the problem.

I then thought uninstalling NVDA and Code Factory and then reinstalling would fix the problem.

So, NVDA was uninstalled, and I was not able to find an uninstall for the Code Factory voices.

I attempted to reinstall the latest NVDA program, and I get to the License agreement screen. I agree, and when the install goes to the next screen, the System begins Beeping about one Beep per second.

I have left the NVDA install running, and Beeping for up to 40 minutes with no change, and there was No install.

Does anyone know how to remove all vestiges of NVDA and of the Code Factory Voices?

Hope so, because I now have one System that will not allow me to install NVDA.

Thanks for any reply,

Dave

--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"

Exactly, Jackie. I think there is an e-mail addy with the name of hiss
addon. I'm going to try that.

Hi Kevin. If you sign into the bookmarks sync in Waterfox you can still get your bookmarks back like you did in FF.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986>; for Windows 10
________________________________
From: nvda@nvda.groups.io <nvda@nvda.groups.io> on behalf of Kevin Cussick via Groups.Io <the.big.white.shepherd=googlemail.com@groups.io>
Sent: Wednesday, September 19, 2018 6:13:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Waterfox works with NVDA
I don't think so, How do I get book marks from say firefox into water
fox? sorry I suppose I have somewhat high jacked this sorry mods. but
to answer the question I am sure it will not work portable version of an
older ff and the webvisum might work.
On 19/09/2018 21:57, David Mehler wrote:

Hi,

Does Waterfox and Webvisum work with each other?

Thanks.
Dave.


On 9/19/18, JM Casey <crystallogic@ca.inter.net> wrote:

Interesting thoughts. Thanks.

But of course, Firefox Quantum is not inaccessible; NVDA quite nicely got up
to speed and I was even able to use version 57 with it for a time.
Not so with jAWS, where there still seem to be problems.
It is rather unfortunate about the add-ons, though.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: September 19, 2018 3:21 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Waterfox works with NVDA

The quantom engine itself is not a bad thing.

But the fact to fix security they block direct access to windows well thats
debaitable.

Put it this way, 16 bit stuff especially old dos stuff trying to access the
hardware directly.

There can be issues with windows because of that.

Before that, software used to get in other software's way.

The issue now though is that just about everything ie registry, standard
windows controls and accessibility libs need direct access, now just about
every addon author has to write their own interface.

Thats why firefox quantom is totally inaccessible.

Its a security trade off there is no solution, I understand why they do it
even aplord them for doing so but its a trade off.

Waterfox will use classic addons as well as the new quantom engine and the
web extention apis.

So in short we should be able to run both libraries eventually.

Sadly older addons as long as they will be available like noscript will
continue but newer ones will not work but eventually waterfox will go
quantom.

But will continue using classic libraries as well as the new ones.

So in theory we should be able to run most of everything.

Think of windows 10 linux or vmware or talking dosbox or something like
that.

There will probably be a few limitations.

Its unknown what those are.

However this is a community developed project based on the mozilla code
without all the extra mozilla addons etc.

Sadly its also indicated it can't stay in the happy place it is now because
the current engine has limitations.

With thunderbird quantom, addons are just not accessible at all.

Thats fine because I never used them and I find most of the rest of the
engine actually usable.

I'd like the addons to work but chances are I wouldn't be accessing them
anyway.



On 9/19/2018 7:11 PM, Brian's Mail list account via Groups.Io wrote:

Yes I have to say this is a cleaner faster browser altogether from the
64 bit standpoint but anyone running 32 bit windows cannot use it, as
its been optimised for the 64 bit system and that may well be why its
snappier generally. They say they are inheriting all the classic add
ons so we assume from that that they have no intention of going Quantum,.

They are seemingly attacking any security issues through other means.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Clive Pallett"
<clive.pallett@ptplace.co.uk>
To: "NVDA" <nvda@nvda.groups.io>
Sent: Wednesday, September 19, 2018 12:46 AM
Subject: [nvda] Waterfox works with NVDA


Hello everyone,

Further to my previous post, I noticed that Waterfox was recommended
as an alternative browser to Mozilla Firefox. I have installed
Waterfox 56.2.3 and updated NVDA to 2018.3 and Waterfox works fine.
If anything, it loads faster than Firefox and takes me straight to
Google, my preferred home page.

Best wishes,

Clive Pallett

The main purpose to using an external synthesizer, (which most folks seem to miss), is the fact that if you use an external synthesizer,
your computer doesn't have to perform the speech generation, and especially on a low resource pc, this can make a world of difference as to how responsive your system is.  If the cpu doesn't have to spend time rendering the speech, it will be free to do other things like calculating that huge spreadsheet, or converting that audio file for you.  Admittedly, this isn't as critical as it used to be, what with cpus generally having cpu cycles to burn these days, but for those who are on low end hardware, or just want to leave all the available computing power to the applications and the os, using an external synthesizer makes plenty of sense.

 On Thu, 20 Sep 2018, Ron Canazzi wrote:

Hi Group,


I used to use hardware synthesizers years ago: Dectalk Serial, double talks ISA and Triple Talk USB.  Now of days, I find it easier if indeed you need a separate sound source for screen reader and system audio to use a cheaper sound card separate from the system audio.  I am using a sound blaster SBX Figo! that cost less than 40 dollars and run it into a cheap set of speakers for the screen reader and the onboard Realtech sound chip that sound good when separate from the sound blaster.  This is much cheaper and works just as well as any hardware synthesizer that costs hundreds of dollars.




On 9/20/2018 11:53 AM, Brian's Mail list account via Groups.Io wrote:

The point is this. Did it work with the previous version of nvda. If it did then plainly you need to alert the writer of the add on and see if they can fix it. I suspect the person has vanished by now, but its worth a try looking at the add ons internals for a contact. This is why we try to get add on authors to submit them for testing as this sort of issue can be alerted during the beta testing and the add on modified to work. The Tripletalk was controlled by special characters as I recall, you could also get in and alter some of them, but it was a long time ago and I doubt if the utilities that we had then will work on current versions of windows. 16bit software refused to run at all on a 64 bit machine.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Jackie" <abletec@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, September 20, 2018 4:12 PM
Subject: Re: [nvda] Jackie and all - - Update -- NVDA saying "Less Than" before everything I read and do

So, Nancy, I just know you're gonna think I'm a pest for asking *so*
many questions, & I don't blame you--I think I'm a pest too--but, is
this the USB TT or is it the mini? I should've asked my 1st question
in a different way before, & I apologize for that.

This sounds like another really dumb question, but have you tried
different USB ports?

On 9/20/18, Nancy Shackelford <n.k.nancelady@gmail.com> wrote:

I removed the Triple Talk USB addon and found a download of it and
reinstalled. The Less
 than problem still exists with the Triple Talk. I hope a solution can
be found for this. Only addons I have are the E T I Eloquence and the
Triple Talk synths. Thanks for all thNance


On 9/20/18, Nancy Shackelford <n.k.nancelady@gmail.com> wrote:

Triple Talk USB. Does not need battery. I can't find the addon for
this on N V D A site.

 >

Nance

On 9/20/18, Jackie <abletec@gmail.com> wrote:

Nance, is this a triple talk USB or another variant? Does it have a
battery?

On 9/20/18, Nancy Shackelford <n.k.nancelady@gmail.com> wrote:

I need to research and find how to do that restart, but I just
discovered something:  When I use a synth such as ETI Eloquence, the
"less than" is not spoken as it is when using my Triple Talk device.
Any suggestions?? Absolutely weird!

Thanks in advance,

Nance

On 9/20/18, Quentin Christensen <quentin@nvaccess.org> wrote:

Failing that, have you tried restarting NVDA with add-ons disabled,
just
in
case it's an add-on playing funny?  If it is an add-on, check to see
if
there are updates to any, and try enabling them one at a time to see
what
causes it.  If you do find the culprit, do please let us know.

--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael
Reid--

--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--

--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com

--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--

--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--

--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com

--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"

can you guys suggest some application to convert epub to word offline? or epub to pdf?
--
Regards,
Sociohack