Date   

NVDA remote

Robert Doc Wright godfearer
 


A friend has the latest NVDA remote installed but when you go to addon manager it says will install after restart. We have restarted several times and we get the same report in the addon manager. We have even rebooted the pc and yet remote does not show under tools in the NVDA menu.

 

                                                                                                                                If all I have left in this world is God, I have everything!                                                                                                                                                                                                                                                                                                                                                Sent from Mail for Windows 10

 


Re: NVDA addon: Community feedback on new Developer toolkitfeature requested

Andy B.
 

Yes, already had this in mind.

 

 

Sent from Mail for Windows 10

 

From: Jacob Kruger
Sent: Monday, July 29, 2019 2:11 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA addon: Community feedback on new Developer toolkitfeature requested

 

Andy, relative positioning would definitely be useful at times, but, it would be better as an option you could toggle on and off?


Jacob Kruger
Blind Biker
Skype: BlindZA
"...resistance is futile...but, acceptance is versatile..."

On 2019-07-28 5:17 AM, Andy B. wrote:

Hi,

I am requesting the community’s feedback on a feature for Developer toolkit. Before proceeding with the new feature’s description, I must provide a sample problem a user might encounter while using DTK. Imagine you are a user of DTK. You wish to make a dialog in the top-right corner of your display with a button centered in the dialog. The dialog is to have the dimensions of 100px wide and 100px high. The button is to have the dimensions of 75px wide and 25px high. You know the display resolution is 1920px wide and 1080px high.

You confidently code up the dialog to sit in the top-right corner of the display. To verify, you launch the dialog, turn on DTK, navigate to the dialog, then obtain its size and location. After checking the size and location, you are happy with its placement: (left, top, right, bottom): 1820, 0, 1920, 100 [100px wide and 100px high]. You proceed to place a button in the dialog. To verify the button’s size and location, you launch the dialog, put focus on the button, turn on DTK features, and obtain the button’s size and location. To your horror, the location is (left, top, right, bottom): 1820, 0, 1904, 25) [75px wide and 25px high]. It is a reasonable guess that the button is in the top-left corner of the dialog. However, you might have to perform some math to figure it out. Now, imagine what this would look like with a fairly complex design or layout… Messy at best! The problem is that all object locations are reported relative to the entire display. This method is useful for gross layouts such as setting up foreground window placement, or header, footer, multicolumn website layouts. Even the web layouts provide their own issues. Wait though, there is a solution to the problem!

The proposed feature I would like comments on is the ability for DTK to provide location information relative to the focused object’s parent. In the example given, you could ask DTK to give you the locations of the left, top, right, and bottom edges based on the distance between the focused object and its parent’s edges. For instance, DTK would report the button location as (left, top, right, bottom): 0, 0, 75, 25. You could still obtain locations based on the entire display’s size though. Implementing this isn’t difficult, but I need feature requests and implementation ideas from a user’s point of view. How would you see this feature implemented?

 

 

 

Sent from Mail for Windows 10

 

 


Re: Deleting network shares was: Re: [nvda] Anybody have accessible NAS recommendations?

John Isige
 

That on a Mybook? Thanks! I don't think I'll end up going with WD though. The Mybook is crazy slow, which is why I'm replacing it, and I'm seeing references to similar issues and network dropouts with their MyCloud replacement. Good to know I might actually be able to delete shares though.

On 7/29/2019 0:14, Mobeen Iqbal wrote:

Hi.

I'm using NVDA latest version with firefox latest on windows 10. Press enter on your share. After the shares list on mine, NVDA says blank twice before the next item. the first blank is the delete share option, the second is edit.

cheers,

Mo.

On 29/07/2019 03:55, John Isige wrote:
I don't know that I'd go with WD again, but just in case, how accessible is it? I have a WD MyBook Live and it's mostly accessible. I can't delete shares I've made though and some of the other operations for manipulating them don't really work that reliably. So I'd like to make sure I can get something that's really accessible if I'm going to spend money to update.


NVDA moving to Python 3

Quentin Christensen
 

Hi everyone,

There has been a bit of confusion over NVDA's move to "Python 3".  I wanted to share a short message to clarify a couple of issues and concerns people have raised:

First and most importantly; the upcoming NVDA 2019.2 is not affected.  NVDA 2019.2 still uses code based on "Python 2", just like NVDA 2019.1 and earlier.  So, for the most part, anything which works in NVDA 2019.1, should work in 2019.2.

Please do test NVDA 2019.2 beta 3, which is available here: https://www.nvaccess.org/files/nvda/releases/2019.2beta3/nvda_2019.2beta3.exe.  If you do find any issues, particularly things which worked in NVDA 2019.1 which no longer work, please do let us know.  The "Release Candidate" for 2019.2 is due out shortly, and we would encourage all users to test that when it comes out.

So what are we doing?  We're updating NVDA's code from being largely based on Python 2, to Python 3.  Python 3 was first introduced in 2008, and Python 2 will reach end-of-life early next year.   Python's Wikipedia page succinctly explains why Python 3 is important:   Python 3 was "... designed to rectify fundamental design flaws in the language—the changes required could not be implemented while retaining full backwards compatibility with the 2.x series".  https://en.wikipedia.org/wiki/History_of_Python#Version_3

So why are we doing this?   Partly to ensure the ongoing stability and security of NVDA.  We cannot release a product based on a programming language which is no longer supported.  Not only would functionality be increasingly likely to break with updates to Windows and other programs, but it would not be secure.  As well as this, developers learning Python over the past few years have not been taught Python 2, they have been taught Python 3.  Moving to Python 3 ensures that we have access to this growing pool of developers.

NV Access and the community have worked together to ensure the process to transition add-ons is as smooth as possible.  There is a Wiki page with information on the transition at: https://github.com/nvaccess/nvda/wiki/nvdaPy3  Any developers with questions are encouraged to join in the discussion on the NVDA Developers mailing list: https://groups.io/g/nvda-devel  As much as users are concerned about the ongoing viability of add-ons they rely on, we are also keen to maintain stability and continuity of functionality for everyone.

We have just released a first Alpha build of NVDA updated to Python 3.  This is really only aimed at developers at this point.  What we would like end-users to know is that we have been in contact with the major synth and add-on developers.  We knew that would be the first question many people had about this process so we have involved them from early on.

If you are wondering whether "Synthesizer X" or "Add-on Y" will work under Python 3, the manufacturer of that Synthesizer or add-on is the first port of call.  If they have already updated and tested, they will be happy to let you know that.  Remember that we have only just released a first alpha build using Python 3 ourselves, so don't panic if your favourite hasn't been updated yet!

Joseph Lee has helpfully curated a list of add-ons, their known status and the contact details for the developer.  This list is on the official add-ons site:  https://addons.nvda-project.org/addons/nvdapy3.en.html

We will continue to work with add-on and synthesizer developers.  We don't have a choice about making this change, but like you, we don't want to see anyone left with decreased functionality due to an "upgrade".
 
Rest assured we will continue to test these changes to NVDA's codebase prior to pushing them out to users.  If you do still have any questions or concerns, please feel free to ask.

Regards

Quentin

--
Quentin Christensen
Training and Support Manager

NVDA 2019.2beta3 now available!


NVDA add-ons and Python 3: at least a third of add-ons hosted on community add-ons website are compatible

 

Hi all,

 

As a way to inform the community about ongoing Python 3 transition (which began last week but may pick up speed starting in August), I (as the add-ons community coordinator on Python 3 transition) will provide updates on how various add-ons are doing in terms of Python 3 transition. Most status updates will coincide with NVDA milestones e.g. 2019.2 release candidate, 2019.3 beta 1, and so on. I’ll do my best to provide updates once or twice a month.

 

Notes:

 

  1. There are tons of add-ons out there, which includes add-ons not hosted on community add-ons website (addons.nvda-project.org).
  2. Add-on compatibility status is based on reports from add-on authors and testing done by at least one user or author.
  3. Some status updates will feature notable add-ons and their compatibility statuses. Some will feature community-wide directives if warranted (first one is below).
  4. You are encouraged to assist in Python 3 transition. Note that although you can make an add-on “compatible” by editing its manifest, not all add-ons will suddenly come to life in NVDA 2019.3 alpha.

 

Python 3 and add-ons status as of July 29, 2019:

 

  • Add-on count on community add-ons website: 66 stable add-ons (more if we count add-ons under development section)
  • Compatible: 22
  • Notable compatible add-ons: Add-on Updater, Unicode Braille Input, Resource Monitor, Windows 10 App Essentials, Day Of The Week, MP3 Direct Cut, SystrayList, Golden Cursor.
  • Notable incompatible add-ons: many speech synthesizers, Braille Extender, Clip Contents Designer, Place Markers, Read Feeds, Text Information.
  • Status to be determined: 32 add-ons (although by tomorrow most of them will have their compatibility status determined, and I expect some to be compatible while others will not for the time being).

 

Community directive (July 2019 no. 1): contact add-on authors. Because many add-ons (including some notable ones) are not compatible at this point, please ask add-on authors about their thoughts about porting their add-ons to Python 3. Depending on which add-ons you are using and author:

 

  • Speech synthesizers and braille displays: highest of highest of priorities (a few days ago I wrote to an NVDA mailing list regarding it and promised I’ll initiate a community directive on this, and now is the time to start contacting vendors).
  • Control Usage Assistant (Joseph Lee/end of life): I will release a “nightlight” i.e. emergency add-on update in August that will make this add-on Python 3 ready.
  • Add-ons from Noelia Martinez: Noelia says she is aware of community feedback and will get her add-ons ready by 2019.3 beta.

 

Notable add-ons hosted outside community add-ons website:

 

  • DictationBridge: developers are aware of Python 3 compatibility issues and will provide an update in an upcoming release.
  • Remote Support: I have contacted at least one of the authors regarding their thoughts on Python 3 compatibility.

 

Thank you.

Cheers,

Joseph


Re: NVDA addon: Community feedback on new Developer toolkit feature requested

Jacob Kruger
 

Andy, relative positioning would definitely be useful at times, but, it would be better as an option you could toggle on and off?


Jacob Kruger
Blind Biker
Skype: BlindZA
"...resistance is futile...but, acceptance is versatile..."

On 2019-07-28 5:17 AM, Andy B. wrote:

Hi,

I am requesting the community’s feedback on a feature for Developer toolkit. Before proceeding with the new feature’s description, I must provide a sample problem a user might encounter while using DTK. Imagine you are a user of DTK. You wish to make a dialog in the top-right corner of your display with a button centered in the dialog. The dialog is to have the dimensions of 100px wide and 100px high. The button is to have the dimensions of 75px wide and 25px high. You know the display resolution is 1920px wide and 1080px high.

You confidently code up the dialog to sit in the top-right corner of the display. To verify, you launch the dialog, turn on DTK, navigate to the dialog, then obtain its size and location. After checking the size and location, you are happy with its placement: (left, top, right, bottom): 1820, 0, 1920, 100 [100px wide and 100px high]. You proceed to place a button in the dialog. To verify the button’s size and location, you launch the dialog, put focus on the button, turn on DTK features, and obtain the button’s size and location. To your horror, the location is (left, top, right, bottom): 1820, 0, 1904, 25) [75px wide and 25px high]. It is a reasonable guess that the button is in the top-left corner of the dialog. However, you might have to perform some math to figure it out. Now, imagine what this would look like with a fairly complex design or layout… Messy at best! The problem is that all object locations are reported relative to the entire display. This method is useful for gross layouts such as setting up foreground window placement, or header, footer, multicolumn website layouts. Even the web layouts provide their own issues. Wait though, there is a solution to the problem!

The proposed feature I would like comments on is the ability for DTK to provide location information relative to the focused object’s parent. In the example given, you could ask DTK to give you the locations of the left, top, right, and bottom edges based on the distance between the focused object and its parent’s edges. For instance, DTK would report the button location as (left, top, right, bottom): 0, 0, 75, 25. You could still obtain locations based on the entire display’s size though. Implementing this isn’t difficult, but I need feature requests and implementation ideas from a user’s point of view. How would you see this feature implemented?

 

 

 

Sent from Mail for Windows 10

 


Re: A Question About NVDA, Python 3 and Espeak

 

Hi,
How?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mattias
Sent: Sunday, July 28, 2019 10:54 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A Question About NVDA, Python 3 and Espeak

no addon updater is broken

Den 2019-07-28 kl. 23:51, skrev David Csercsics:
The only add-ons I usually use are braille extender and the Windows 10
essential ones, and the add-on updater, but it looks like all of those
are either being updated, or already work fine with the new Python 3,
but I'd be happy to help with this if I can.





Re: A Question About NVDA, Python 3 and Espeak

mattias
 

no addon updater is broken

Den 2019-07-28 kl. 23:51, skrev David Csercsics:

The only add-ons I usually use are braille extender and the Windows 10 essential ones, and the add-on updater, but it looks like all of those are either being updated, or already work fine with the new Python 3, but I'd be happy to help with this if I can.




Deleting network shares was: Re: [nvda] Anybody have accessible NAS recommendations?

Mobeen Iqbal
 

Hi.

I'm using NVDA latest version with firefox latest on windows 10. Press enter on your share. After the shares list on mine, NVDA says blank twice before the next item. the first blank is the delete share option, the second is edit.

cheers,

Mo.

On 29/07/2019 03:55, John Isige wrote:
I don't know that I'd go with WD again, but just in case, how accessible is it? I have a WD MyBook Live and it's mostly accessible. I can't delete shares I've made though and some of the other operations for manipulating them don't really work that reliably. So I'd like to make sure I can get something that's really accessible if I'm going to spend money to update.


Re: Anybody have accessible NAS recommendations?

 

Well if you jack the processers in your nas to as high as they can fit and install the ram you need, you can probably ditch the os entirely and run your own linux distribution because a few audio geeks did it that way and bang you have not only a backup solution but a media server and other things as well but I have no idea how to do that.

These guys also have huge cloud backups of things.



On 29/07/2019 3:14 PM, Tyler Wood wrote:

Hi,

I’ve heard good things about sonology.

The thing that’s turning me off any of these NAS devices is the fact that software can change at a moments notice with a firmware update, as happened with netgear, and said firmware downgrade may be impossible. I’d rather get a refurbished computer (after all, all these NAS’s are is a computer), get one of those mediasonic proraid drive enclosures and install one of the pre-existing NAS programs for either Windows or Linux – this way you’re in complete control of what you get and when you get it. Of course, it all depends on what you do, but initial setup for most things really doesn’t sound difficult.

 

Just my opinion, however. After I was unable to downgrade the firmware of a netgear NAS for a friend, that turned me off of them quite a lot. Of course your mileage may vary, and certain companies may be better than others.

 

Best of luck!

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John Isige
Sent: July 28, 2019 9:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Anybody have accessible NAS recommendations?

 

I don't know that I'd go with WD again, but just in case, how accessible is it? I have a WD MyBook Live and it's mostly accessible. I can't delete shares I've made though and some of the other operations for manipulating them don't really work that reliably. So I'd like to make sure I can get something that's really accessible if I'm going to spend money to update.


Re: Anybody have accessible NAS recommendations?

Tyler Wood
 

Hi,

I’ve heard good things about sonology.

The thing that’s turning me off any of these NAS devices is the fact that software can change at a moments notice with a firmware update, as happened with netgear, and said firmware downgrade may be impossible. I’d rather get a refurbished computer (after all, all these NAS’s are is a computer), get one of those mediasonic proraid drive enclosures and install one of the pre-existing NAS programs for either Windows or Linux – this way you’re in complete control of what you get and when you get it. Of course, it all depends on what you do, but initial setup for most things really doesn’t sound difficult.

 

Just my opinion, however. After I was unable to downgrade the firmware of a netgear NAS for a friend, that turned me off of them quite a lot. Of course your mileage may vary, and certain companies may be better than others.

 

Best of luck!

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John Isige
Sent: July 28, 2019 9:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Anybody have accessible NAS recommendations?

 

I don't know that I'd go with WD again, but just in case, how accessible is it? I have a WD MyBook Live and it's mostly accessible. I can't delete shares I've made though and some of the other operations for manipulating them don't really work that reliably. So I'd like to make sure I can get something that's really accessible if I'm going to spend money to update.


Re: Anybody have accessible NAS recommendations?

John Isige
 

I don't know that I'd go with WD again, but just in case, how accessible is it? I have a WD MyBook Live and it's mostly accessible. I can't delete shares I've made though and some of the other operations for manipulating them don't really work that reliably. So I'd like to make sure I can get something that's really accessible if I'm going to spend money to update.


Re: Anybody have accessible NAS recommendations?

John Isige
 


Could you explain a bit about what 97% accessible means? Specifically, what things aren't accessible?


Re: Braille Extender not saving tables

David Csercsics <bleeblat@...>
 

It is definitely a bug! I can duplicate it here as well as a couple other things. But the add-on will likely no longer work as of 2019.3 because of the move to Python 3 support, so we may have to find another solution.

 A pity for me because I really enjoy my braille display, but I'll see what I can learn to sort this out.


Braille Extender not saving tables

Deborah Armstrong <debee@...>
 

Nvda 2019.1.1 current stable. Braille Extender 2019.07.10, also current stable.
This problem was reported on the list by Rob Hudson back in January.
 
Though the settings let you configure two Braille tables, a primary and a secondary, pressing OK does not save them. I've tried ENTER, I've tried space, I've tried going to another field and pressing Enter.
 
The secondary table does save but not the primary so when you try to switch tables you get the message:
"you must choose at least two tables for this feature. Please fill in the settings."
 
I've tried going to the Braille extender settings through preferences  and Settings, then Braille extender.  also finding the same dialog just under Preferences.
 
I don't know how you can save more than two tables though documentation implies you can. 
Why aren't the tables I specify saving? Is this a bug or a misunderstanding on how the settings interface works?
 
--Debee
 


Re: A Question About NVDA, Python 3 and Espeak

David Csercsics <bleeblat@...>
 

Alright, well, I'll poke around for another solution then, or see what can be done. At least there is time, and I do think the Python 3 changes are necessary. It is great the good work everyone is doing to make this stuff useful. Thank you!


Re: A Question About NVDA, Python 3 and Espeak

 

Hi,
Braille Extender is broken, and it appears the site used for updating that add-on is gone somehow. Others are compatible and working.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of David Csercsics
Sent: Sunday, July 28, 2019 2:52 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A Question About NVDA, Python 3 and Espeak

The only add-ons I usually use are braille extender and the Windows 10 essential ones, and the add-on updater, but it looks like all of those are either being updated, or already work fine with the new Python 3, but I'd be happy to help with this if I can.


Re: A Question About NVDA, Python 3 and Espeak

David Csercsics <bleeblat@...>
 

The only add-ons I usually use are braille extender and the Windows 10 essential ones, and the add-on updater, but it looks like all of those are either being updated, or already work fine with the new Python 3, but I'd be happy to help with this if I can.


Re: A Question About NVDA, Python 3 and Espeak

Quentin Christensen
 

Also,

Just to be clear, the upcoming NVDA 2019.2 release is still based on the existing python 2 code, so any add-ons and synthesizers etc should still work.

We are also working with synth manufacturers, to ensure ongoing compatibility of their add-ons with NVDA into the future.

Regards

Quentin.

On Sat, Jul 27, 2019 at 6:27 PM Luke Davis <luke@...> wrote:
No, espeak works fine in Python 3 versions of NVDA.

On Sat, 27 Jul 2019, Marcio via Groups.Io wrote:

> Considering all the Python 3 porting conversation I have a question. It's been said that some synthesizers would stop working. Is it the case about Espeak?





--
Quentin Christensen
Training and Support Manager

NVDA 2019.2beta1 now available!


Re: Anybody have accessible NAS recommendations?

John Isige
 

actually, you can apparently run their software for a long while even on
older stuff. This will run the latest, and there was a critical update
from this year. So yeah, it should run the latest and greatest. Also, I
won't be opening it up to the internet, which is what all of these
people seem to have done. Well OK, I guess I can't say I'll never do it,
but right now it's just gonna be a media server behind a router, totally
local stuff. Good advice though, thanks!

On 7/27/2019 22:33, Luke Davis wrote:
While I don't know anything about that particular gear--I have always
built my own NASes using Linux--I will say that I would have
misgivings about buying a piece of 2013 computing equipment of any kind.

If it is not still receiving security patches, I would definitely not
buy it. See the conversations here recently about Windows XP. Embedded
systems are often even worse than old operating systems, when it comes
to security and patching security holes.

So if that thing has an ARM, Intel, or AMD processor (or one of
several others), for example, and it hasn't received 2018 software
updates, it's vulnerable to several processor level hacks that can
allow someone to read anything in its memory. That aside, depending on
what software it's running, it could even become part of a botnet,
like most Windows XP systems are.

So be very careful with buying old equipment like this. If it's not
still getting software updates, stay far away from it, or only use it
in a situation where it never touches the internet.

Some links:

read the comment by archagon, and some others:
https://news.ycombinator.com/item?id=8128521

And perhaps: https://arstechnica.com/civis/viewtopic.php?f=2&t=1247263
https://www.reddit.com/r/synology/comments/9qzooz/hacked_2_factor_authentication_doesnt_prevent/


Luke