Date   

Re: a settings question

Gene
 

I haven't looked into what most of the settings do in this category, though I have seen a little discussion and read a bit at some point.  Unless you experiment or know some reason why you would benefit from a settings change, I generally leave defaults as they are.  In this case, the defaults are as follows:
Follow system focus, checked.
Follow system caret, checked.
Follow mouse cursor, unchecked and
simple review mode, checked.

Gene   
On 6/17/2022 3:00 AM, mcLeod stinnett wrote:

under preferances, settings, review cursor. i have follow system focus checked, and the 2 boxes after that unchecked. for best results should all of the boxes in that category be checked? thanks.


Re: a settings question

Jacob Kruger
 

Explanation of those settings, from documentation:

12.1.11. Review Cursor
The Review Cursor category in the NVDA Settings dialog is used to configure NVDA's review cursor behaviour. This category contains the following options:
Follow System Focus
Key: NVDA+7
When enabled, The review cursor will always be placed in the same object as the current system focus whenever the focus changes.


Follow System Caret
Key: NVDA+6
When enabled, the review cursor will automatically be moved to the position of the System caret each time it moves.


Follow mouse cursor
When enabled, the review cursor will follow the mouse as it moves.


Simple Review mode
When enabled, NVDA will filter the hierarchy of objects that can be navigated to exclude objects that aren't of interest to the user; e.g. invisible objects and objects used only for layout purposes.
To toggle simple review mode from anywhere, please assign a custom gesture using the Input Gestures dialog.


In other words, up to you, and might also depend on context?


Jacob Kruger
Skype: BlindZA
"Resistance is futile...but, acceptance is versatile..."

On 2022-06-17 10:00 AM, mcLeod stinnett wrote:
under preferances, settings, review cursor. i have follow system focus checked, and the 2 boxes after that unchecked. for best results should all of the boxes in that category be checked? thanks.


Re: a settings question

Quentin Christensen
 

As Lukasz said,

The best suggestion is to be aware of what the options do and how the review cursor works, and then you will work out the best set of options for you.

Here is the User Guide section on navigating, which includes the review cursor: https://www.nvaccess.org/files/nvda/documentation/userGuide.html#NavigatingWithNVDA


Now, if you aren't familiar with the review cursor, or how it works, I would strongly suggest that the Basic Training for NVDA guide, although not free, is worth it for the sections on the Review Cursor and Object Navigation alone: https://www.nvaccess.org/product/basic-training-for-nvda-ebook/

Basically though, those three options will set whether the review cursor follows:

System Focus: This includes things like the current ribbon option when navigating the ribbon in Word or File Manager, the current menu item in the start menu, the button or checkbox on a web page, the options in the NVDA settings dialog etc. 

System Caret: The text cursor anytime you are somewhere editing text such as an email, Word document or web form.  (In this way, you can think of the System Focus as whatever NVDA is currently on any time you are NOT in an edit field).

Mouse cursor: This will follow the mouse around - this is mostly useful (but possibly very much so) if you have some sight and use the mouse.

Quentin.

On Fri, Jun 17, 2022 at 6:12 PM Lukasz Golonka via groups.io <lukasz.golonka=mailbox.org@groups.io> wrote:

On Fri, 17 Jun 2022 01:00:47 -0700
"mcLeod stinnett" <macks75205@...> wrote:

> under preferances, settings, review cursor. i have follow system focus checked, and the 2 boxes after that unchecked. for best results should all of the boxes in that category be checked?

Assuming that by "2 boxes after that" you mean "Follow System Caret" and
"Follow mouse cursor" there is no single good answer.
The best way to determine how these options should be set for your use
cases would be to read their description in the user guide. I personally
prefer to work with all options in the review settings panel except
"Simple review mode" unchecked, but that is of course pretty subjective,
and requires moving review cursor manually to the focus position rather
than this being done automatically.


--
Regards
Lukasz







--
Quentin Christensen
Training and Support Manager


Re: holding off on 2022.1 due to Code Factory dragging their feet

Brian's Mail list account
 

Yes look at the poor record on commercial software on accessibility for example. So often a new incarnation trashes something while fixing something else. And these are pay for programs. One case in point is Quick Books, but there are others of course.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 17, 2022 7:15 AM
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet


Just to confirm NVDA will remain free and open source. Re the suggestion
that we should charge for it so users can demand excellent, I would argue
you have every right to expect excellence now. And I like to think we
generally deliver on that ideal. Not always, sure, but we do aim to set
the bar high!

Re add-ons, which, arguably, seem to be the main complaint (well, add-ons
and the breaking of them) - as Brian rightfully pointed out, almost all of
them are made and maintained by people other than NV Access, so we can't
make any guarantees about them. What we can say, is that we advise the
add-on community often a year in advance, of breaking changes. Case in
point, if you look at the what's new for NVDA 2022.2 Beta 1:
https://www.nvaccess.org/files/nvda/releases/2022.2beta1/documentation/changes.html

Under the Changes for developers section, you will find:

"Deprecations
These are proposed API breaking changes. The deprecated part of the API
will continue to be available until the specified release. If no release is
specified, the plan for removal has not been determined. Note, the roadmap
for removals is 'best effort' and may be subject to change. Please test the
new API and provide feedback. For add-on authors, please open a GitHub
issue if these changes stop the API from meeting your needs."

There are a handful of depreciated functions and their replacements
listed. So we do try to give people as much notice as possible.

Kind regards

Quentin.

On Fri, Jun 17, 2022 at 3:58 PM Monte Single <mrsingle@...> wrote:

Yes, Ron,



And there is also a large group of people, in any aspect of society, who
trumpet loud and wide, “you get what you pay for”.

I am glad to make a small contribution to nvda rather than supporting
jaws.



*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Ron
Canazzi
*Sent:* June 16, 2022 11:50 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] holding off on 2022.1 due to Code Factory dragging
their feet



Hi Group,

I hope NVDA never goes commercial. In the US now-of-days, there is a
persistent and radical libertarian philosophy that has taken hold of a
large minority of the people saying in essence: 'If you don't pay, you
don't play.' Without getting into a political discussion on this issue,
people who advocate this don't realize just what profound changes would
result if this philosophy (as it appears likely) takes over the body
politic entirely. Just think of Europe from the middle ages to the
nineteenth century.

Having said that, people should be appreciative of the great work done by
the creators of NVDA and should be grateful and not complain so much. A
small donation--even from unemployed blind people to NVDA would be in
order. Since it is well known that millions (I believe over 70 million at
last report) of people in the world use NVDA, just imagine if everyone gave
the equivalence of five dollars US a year. That would be 350 million
dollars US yearly.

As far s as code factory Eloquence, I am having no problem with the SAPI 5
version of the product. What issues are there with this product?

On 6/16/2022 11:31 PM, Ravindran V.S. wrote:

Dear Mike,

If my understanding is correct of your message,

Please note, ever since NVDA released as a free screen reader millions of
Blind users have got into some kind of technical or computer literacy and
use of technology.

If not still a vast majority would not be able to access computers due to
the high cost of the commercial products.

Also, NVDA has created many job opportunities to many Visually Impaired
Persons in several countries.

So, I urge that this should continue as the current way it is as an open
source product and accessible to all Blind people.

People in the poor countries, and the developing countries are mainly
depending on this screen reader. Who may be heavily using the product, but
may not be in a position or afford to donate towards this cause.

Therefore, I kindly request to all the developers and contributors to
keep and continue this as an open source and free product, or at least to
the people in the poor countries.

We even get the computers through donations, under this circumstances how
could we spend hundreds or thousands of Dollars to the commercial Screen
Readers?

I live in Sri Lanka, and now even we almost starving , under this
situation cannot think of purchasing any screen reader or anything other
than considered to be essential items.

Which some time may cost the job of the Blind people as well, who are
depending on NVDA for their work .

So, for delay of any Add-Ons should not deny access of a screen reader for
many Blind people.

Thank you in advance for understanding. NVDA is a blessing to many Blind.

Ravi.



*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> <nvda@nvda.groups.io> *On
Behalf Of *mike mcglashon
*Sent:* Thursday, June 16, 2022 9:44 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] holding off on 2022.1 due to Code Factory dragging
their feet



Quoting:

My own view is that these add-ons should be updated in the Alpha or Beta
stages, not after release. Either that, or NVDA should not keep breaking
compatibility with them.

End quote:



Amen to this.

If NVDA were a commercial software instead of “charitable open source
code”, these practices might not be tolerated as easily.

I wish sometimes that NVDA would “actually charge” for its software
instead of hiding behind “donations” then we could demand excellence.

It is strictly my belief that we as a society give too much leeway to
“charitable” products.



I say these things as a “donor” to NVDA.





Please advise as you like.



Mike M.



Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331



*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Steve
Nutt
*Sent:* Thursday, June 16, 2022 12:06 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] holding off on 2022.1 due to Code Factory dragging
their feet



No, you’re not alone. It makes work also for the average user, who gets
their NVDA just right with add-ons, only to find them broken in the next
version.



My own view is that these add-ons should be updated in the Alpha or Beta
stages, not after release. Either that, or NVDA should not keep breaking
compatibility with them.



All the best


Steve



*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Tyler
Wood
*Sent:* 23 May 2022 20:16
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] holding off on 2022.1 due to Code Factory dragging
their feet



As a random interjection I find it quite disturbing how easily add ons are
losing compatibility from one minor version to the next. This is a trend I
as a user am not a fan of. It means more work for developers, more issues
by the end user if add ons become unsupported, or at least, unsupported
according to NVDA itself, and less time to actually make improvements for
the developers who are already placing their doubtlessly limited and free
time into this wonderful hobby of creating resources for NVDA to take
advantage of.

I am truly curious to know what I, as a user, am benefiting from with this
so called fragmentation. Previously add ons would work without issue, now
it’s a guessing game as to which add ons will be disabled and stop working
when I’d like to update NVDA from, again, one minor version to the next.



As it stands right now, I’m running a portable version of the latest NVDA
due to the above, with my main install remaining an older version. Am I
alone in viewing this slightly worrying trend?



*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *mattias
*Sent:* Monday, May 23, 2022 10:38 AM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] holding off on 2022.1 due to Code Factory dragging
their feet



Lol we got the same answer..



Skickades från E-post <https://go.microsoft.com/fwlink/?LinkId=550986>
för Windows



*Från: *Supanut Leepaisomboon <supanut2000@...>
*Skickat: *den 23 maj 2022 12:18
*Till: *nvda@nvda.groups.io
*Ämne: *Re: [nvda] holding off on 2022.1 due to Code Factory dragging
their feet



So I just got a reply from Codefactory, to a ticket regarding
compatibility with NVDA 2022.1 that I submitted way back in April. Below is
their response:
Good morning,
We are aware that a breaking NVDA update was released today.
We've been working on the addon, but unfortunately our update will take a
few more days to complete.
Thank you for your patience.
The Code Factory technical team.





--

Signature:

For a nation to admit it has done grievous wrongs and will strive to correct them for the betterment of all is no vice;

For a nation to claim it has always been great, needs no improvement and to cling to its past achievements is no virtue!



--
Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>


Re: holding off on 2022.1 due to Code Factory dragging their feet

Brian's Mail list account
 

I disagree actually. NVDA has no control over third party add on writers, and can only advise of changes.
IE at some time in the Future when they move to Python compilers that cannot code for Windows 7 machines. then all of those will have to use older versions, and add ons written may well be a mix of old and new code.
I used to have Dolphin Software and some of their scripts, which you could write yourself often stopped working and needed you to tweak them or not update. I'd also hazard a guess that Jaws is much the same.
It is very hard to keep up with developments in features and use optimised code when you have to decide to use older compilers or newer ones that make more efficient code. We have seen it often in Microsoft compilers, anyone go back to the sse 2 instruction set not included in some amd processors during XPs time?
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "mike mcglashon" <michael.mcglashon@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, June 16, 2022 5:14 PM
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet


Quoting:

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

End quote:



Amen to this.

If NVDA were a commercial software instead of “charitable open source code”, these practices might not be tolerated as easily.

I wish sometimes that NVDA would “actually charge” for its software instead of hiding behind “donations” then we could demand excellence.

It is strictly my belief that we as a society give too much leeway to “charitable” products.



I say these things as a “donor” to NVDA.





Please advise as you like.



Mike M.



Mike mcglashon

Email: <mailto:Michael.mcglashon@...> Michael.mcglashon@...

Ph: 618 783 9331



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, June 16, 2022 12:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet



No, you’re not alone. It makes work also for the average user, who gets their NVDA just right with add-ons, only to find them broken in the next version.



My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.



All the best


Steve



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> > On Behalf Of Tyler Wood
Sent: 23 May 2022 20:16
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet



As a random interjection I find it quite disturbing how easily add ons are losing compatibility from one minor version to the next. This is a trend I as a user am not a fan of. It means more work for developers, more issues by the end user if add ons become unsupported, or at least, unsupported according to NVDA itself, and less time to actually make improvements for the developers who are already placing their doubtlessly limited and free time into this wonderful hobby of creating resources for NVDA to take advantage of.

I am truly curious to know what I, as a user, am benefiting from with this so called fragmentation. Previously add ons would work without issue, now it’s a guessing game as to which add ons will be disabled and stop working when I’d like to update NVDA from, again, one minor version to the next.



As it stands right now, I’m running a portable version of the latest NVDA due to the above, with my main install remaining an older version. Am I alone in viewing this slightly worrying trend?



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> > On Behalf Of mattias
Sent: Monday, May 23, 2022 10:38 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet



Lol we got the same answer..



Skickades från E-post <https://go.microsoft.com/fwlink/?LinkId=550986> för Windows



Från: Supanut Leepaisomboon <mailto:supanut2000@...>
Skickat: den 23 maj 2022 12:18
Till: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Ämne: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet



So I just got a reply from Codefactory, to a ticket regarding compatibility with NVDA 2022.1 that I submitted way back in April. Below is their response:
Good morning,
We are aware that a breaking NVDA update was released today.
We've been working on the addon, but unfortunately our update will take a few more days to complete.
Thank you for your patience.
The Code Factory technical team.


Re: Does NVDA have this feature that Window-eyes has?

Brian's Mail list account
 

I think the other issue is when you get a line of characters interspersed with another, like on the bottom of this list messages. I think though that to try to cope with all the eventualities could caause problems for those who want everything. Perhaps the full speech should switch any shorthand off or at least have choices within it.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Steve Nutt" <steve@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, June 16, 2022 12:49 PM
Subject: Re: [nvda] Does NVDA have this feature that Window-eyes has?


Which is quite bad, because what if you get the string 9= in a file, maybe for programming?

It should say Equals repeats nine times.

All the best

Steve

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jackie
Sent: 22 May 2022 08:51
To: nvda@nvda.groups.io
Subject: Re: [nvda] Does NVDA have this feature that Window-eyes has?

NVDA says the number then the symbol, ie, if I write 9 consecutive equal signs, NVDA says 9 equals.

On 5/22/22, Sim Kah Yong <simkahyong@...> wrote:
Hi all, I just received an email from Amazon and it contains a string
of "equal sign" (about 22) in part of the email. Window-eyes will read
"equal, equal, repeated 22 times".

NVDA and JAWS will read 22 times of the "equal sign". Obviously,
Window-eyes is is the better option here. Does anyone know if NVDA or
JAWS has such feature? Thank you.








--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com


Re: In-Process AND a beta both out today

Brian's Mail list account
 

I made Quincy, specifically for smaller speakers, since they tend to make ESpeak sound like it shrieks on the normal ones. I created the grandma one just for fun, but you can easily tweak them yourself as I did, there used to be a tutorial on the ESpeak web site telling you what the various registers do in the voice files.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Robert Mendoza" <lowvisiontek@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 17, 2022 4:36 AM
Subject: Re: [nvda] In-Process AND a beta both out today


Quentin ,

One thing I noticed when reading of my mother's tongue:
Tagalog is very clear and crisp.
I am using the default Voice: English (Great Britain) and Variant: Max
for the speach engine e-Speak ng.
I know you are not fun of the variant max though. LOL!
But, I was so impressed with the narration even a little dialects of my
language is so clear.
Just to give you overview from the time I used NVDA max and alternately
used variant quenzy as my choice.

I tested this out of curiosity as portable to my machine.
Cheers,
Robert Mendoza

On 6/16/2022 2:07 PM, Quentin Christensen wrote:
Our latest In-Process blog is now available!
Highlights from this issue:
- Spotlight on several new features and fixes you might have missed
from NVDA 2022.1
- Info on the first beta of the upcoming NVDA 2022.2
- NV Access going to RSB Tech Fest, we hope to see you there next week!
- We chat with Vision Australia Radio's Focal Point program
- We have refreshed our LinkedIn page, come follow us!
- #NVeofy and more!

Read it now at: https://www.nvaccess.org/post/in-process-16th-june-2022/

--
Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org <http://www.nvaccess.org/>
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>


Re: Recommendations for NVDA Add-Ons

Brian's Mail list account
 

I find Toolbar Explorer very useful for unknown software. I also like the sound theme manager formally 3D sound etc, as it adds audio to a stereo sound to help understand some screen layouts.

Most of the others are more specialised and not used much, but the various addons that announce cut paste, copy etc, can be handy if you are used to that. None of those I've tried is perfect, since there are so many pieces of software that expose the info in an ambiguous way.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Bob Cavanaugh" <cavbob1993@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, June 16, 2022 8:22 PM
Subject: Re: [nvda] Recommendations for NVDA Add-Ons


It all depends on what you're using NVDA for. Personally, I only run
three addons, and am probably going to remove one. They are Numpad Nav
Mode, Addon Updater, and NV Speech Player, though that's the one I'm
thinking of removing as I don't like its voice. Addon Updater is the
essential one if you're running any addons, otherwise it really
depends on how you use the program.

On 6/16/22, Mo Khan <mk3386751@...> wrote:
Which nvda addons would you recommend please? much appreciated. thank you.
Mo.








Re: a settings question

Lukasz Golonka
 

On Fri, 17 Jun 2022 01:00:47 -0700
"mcLeod stinnett" <macks75205@...> wrote:

under preferances, settings, review cursor. i have follow system focus checked, and the 2 boxes after that unchecked. for best results should all of the boxes in that category be checked?
Assuming that by "2 boxes after that" you mean "Follow System Caret" and
"Follow mouse cursor" there is no single good answer.
The best way to determine how these options should be set for your use
cases would be to read their description in the user guide. I personally
prefer to work with all options in the review settings panel except
"Simple review mode" unchecked, but that is of course pretty subjective,
and requires moving review cursor manually to the focus position rather
than this being done automatically.


--
Regards
Lukasz


a settings question

mcLeod stinnett
 

under preferances, settings, review cursor. i have follow system focus checked, and the 2 boxes after that unchecked. for best results should all of the boxes in that category be checked? thanks.
--
from mack


Re: holding off on 2022.1 due to Code Factory dragging their feet

Ron Canazzi
 

Hi Quentin,

You wrote:
...NVDA will remain free and open source.  Re the suggestion that we should charge for it so users can demand excellent, I would argue you have every right to expect excellence now....

and I would argue that even if you pay for it, in this kind of small (relatively speaking) market, even if you pay hundreds of dollars, what guarantee do you have of excellence anyway?  As a long time JAWS user, I worked for the private beta team for more than a decade and there were always problems.  I got booted from the list for making a snide remark when during the final stages of the JAWS 11 testing cycle, at the last minute, they decided to remove a popular feature without telling anyone. This feature was tested by me and several dozen others right up to the end of the cycle and then they decided to do a complete about face. 

There's no guarantee that private companies are any better than public endeavors--no matter how much we are told otherwise.
 


On 6/17/2022 2:15 AM, Quentin Christensen wrote:
Just to confirm NVDA will remain free and open source.  Re the suggestion that we should charge for it so users can demand excellent, I would argue you have every right to expect excellence now.  And I like to think we generally deliver on that ideal.  Not always, sure, but we do aim to set the bar high!

Re add-ons, which, arguably, seem to be the main complaint (well, add-ons and the breaking of them) - as Brian rightfully pointed out, almost all of them are made and maintained by people other than NV Access, so we can't make any guarantees about them.  What we can say, is that we advise the add-on community often a year in advance, of breaking changes.  Case in point, if you look at the what's new for NVDA 2022.2 Beta 1: https://www.nvaccess.org/files/nvda/releases/2022.2beta1/documentation/changes.html

Under the Changes for developers section, you will find:

"Deprecations
These are proposed API breaking changes. The deprecated part of the API will continue to be available until the specified release. If no release is specified, the plan for removal has not been determined. Note, the roadmap for removals is 'best effort' and may be subject to change. Please test the new API and provide feedback. For add-on authors, please open a GitHub issue if these changes stop the API from meeting your needs."

There are a handful of depreciated functions and their replacements listed.  So we do try to give people as much notice as possible.

Kind regards

Quentin.

On Fri, Jun 17, 2022 at 3:58 PM Monte Single <mrsingle@...> wrote:

Yes, Ron,

 

And there is also a large group of people, in any aspect of society,  who trumpet loud and wide, “you get what you pay for”.

I am glad to make a small contribution   to nvda rather than supporting jaws.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: June 16, 2022 11:50 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Hi Group,

I hope NVDA never goes commercial.  In the US now-of-days, there is a persistent and radical libertarian philosophy that has taken hold of a large minority of the people saying in essence: 'If you don't pay, you don't play.'  Without getting into a political discussion on this issue, people who advocate this don't realize just what profound changes would result if this philosophy (as it appears likely) takes over the body politic entirely.  Just think of Europe from the middle ages to the nineteenth century. 

Having said that, people should be appreciative of the great work done by the creators of NVDA and should be grateful and not complain so much.  A small donation--even from unemployed blind people to NVDA would be in order.  Since it is well known that millions (I believe over 70 million at last report) of people in the world use NVDA, just imagine if everyone gave the equivalence of five dollars US a year.  That would be 350 million dollars US yearly. 

As far s as code factory Eloquence, I am having no problem with the SAPI 5 version of the product.  What issues are there with this product?

On 6/16/2022 11:31 PM, Ravindran V.S. wrote:

Dear Mike,

If my understanding is correct of your message,

Please note, ever since NVDA released as a free screen reader millions of Blind users have got into some kind of technical or computer literacy and use of technology.

If not still a vast majority would not be able to access computers due to the high cost of the commercial products.

Also, NVDA has created many job opportunities to many Visually Impaired Persons in several countries.

So, I urge that this should continue as the current way it is as an open source product and accessible to all Blind people.

People in the poor countries, and the developing countries are mainly depending on this screen reader. Who may be heavily using the product, but may not be in a position or afford to donate towards this cause.

Therefore, I kindly request to all the developers and contributors to keep  and continue this as an open source and free product, or at least to the people in the poor countries.

We even get the computers through donations, under this circumstances how could we spend hundreds or thousands of Dollars to the commercial Screen Readers?

I live in Sri Lanka, and now even we almost starving , under this situation cannot think of purchasing any screen reader or anything other than considered to be essential items.

Which some time may cost the job of the Blind people as well, who are depending on NVDA for their work .

So, for delay of any Add-Ons should not deny access of a screen reader for many Blind people.

Thank you in advance for understanding. NVDA is a blessing to many Blind.

Ravi.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mike mcglashon
Sent: Thursday, June 16, 2022 9:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Quoting:

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

End quote:

 

Amen to this.

If NVDA were a commercial software instead of “charitable open source code”, these practices might not be tolerated as easily.

I wish sometimes that NVDA would “actually charge” for its software instead of hiding behind “donations” then we could demand excellence.

It is strictly my belief that we as a society give too much leeway to “charitable” products.

 

I say these things as a “donor” to NVDA.

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, June 16, 2022 12:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

No, you’re not alone. It makes work also for the average user, who gets their NVDA just right with add-ons, only to find them broken in the next version.

 

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

 

All the best


Steve

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Wood
Sent: 23 May 2022 20:16
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

As a random interjection I find it quite disturbing how easily add ons are losing compatibility from one minor version to the next. This is a trend I as a user am not a fan of. It means more work for developers, more issues by the end user if add ons become unsupported, or at least, unsupported according to NVDA itself, and less time to actually make improvements for the developers who are already placing their doubtlessly limited and free time into this wonderful hobby of creating resources for NVDA to take advantage of.

I am truly curious to know what I, as a user, am benefiting from with this so called fragmentation. Previously add ons would work without issue, now it’s a guessing game as to which add ons will be disabled and stop working when I’d like to update NVDA from, again, one minor version to the next.

 

As it stands right now, I’m running a portable version of the latest NVDA due to the above, with my main install remaining an older version. Am I alone in viewing this slightly worrying trend?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mattias
Sent: Monday, May 23, 2022 10:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Lol we got the same answer..

 

Skickades från E-post för Windows

 

Från: Supanut Leepaisomboon
Skickat: den 23 maj 2022 12:18
Till: nvda@nvda.groups.io
Ämne: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

So I just got a reply from Codefactory, to a ticket regarding compatibility with NVDA 2022.1 that I submitted way back in April. Below is their response:
Good morning,
We are aware that a breaking NVDA update was released today.
We've been working on the addon, but unfortunately our update will take a few more days to complete.
Thank you for your patience.
The Code Factory technical team.

 



-- 
Signature:
For a nation to admit it has done grievous wrongs and will strive to correct them for the betterment of all is no vice;
For a nation to claim it has always been great, needs no improvement  and to cling to its past achievements is no virtue!


--
Quentin Christensen
Training and Support Manager


-- 
Signature:
For a nation to admit it has done grievous wrongs and will strive to correct them for the betterment of all is no vice;
For a nation to claim it has always been great, needs no improvement  and to cling to its past achievements is no virtue!


Re: holding off on 2022.1 due to Code Factory dragging their feet

Quentin Christensen
 

Just to confirm NVDA will remain free and open source.  Re the suggestion that we should charge for it so users can demand excellent, I would argue you have every right to expect excellence now.  And I like to think we generally deliver on that ideal.  Not always, sure, but we do aim to set the bar high!

Re add-ons, which, arguably, seem to be the main complaint (well, add-ons and the breaking of them) - as Brian rightfully pointed out, almost all of them are made and maintained by people other than NV Access, so we can't make any guarantees about them.  What we can say, is that we advise the add-on community often a year in advance, of breaking changes.  Case in point, if you look at the what's new for NVDA 2022.2 Beta 1: https://www.nvaccess.org/files/nvda/releases/2022.2beta1/documentation/changes.html

Under the Changes for developers section, you will find:

"Deprecations
These are proposed API breaking changes. The deprecated part of the API will continue to be available until the specified release. If no release is specified, the plan for removal has not been determined. Note, the roadmap for removals is 'best effort' and may be subject to change. Please test the new API and provide feedback. For add-on authors, please open a GitHub issue if these changes stop the API from meeting your needs."

There are a handful of depreciated functions and their replacements listed.  So we do try to give people as much notice as possible.

Kind regards

Quentin.

On Fri, Jun 17, 2022 at 3:58 PM Monte Single <mrsingle@...> wrote:

Yes, Ron,

 

And there is also a large group of people, in any aspect of society,  who trumpet loud and wide, “you get what you pay for”.

I am glad to make a small contribution   to nvda rather than supporting jaws.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: June 16, 2022 11:50 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Hi Group,

I hope NVDA never goes commercial.  In the US now-of-days, there is a persistent and radical libertarian philosophy that has taken hold of a large minority of the people saying in essence: 'If you don't pay, you don't play.'  Without getting into a political discussion on this issue, people who advocate this don't realize just what profound changes would result if this philosophy (as it appears likely) takes over the body politic entirely.  Just think of Europe from the middle ages to the nineteenth century. 

Having said that, people should be appreciative of the great work done by the creators of NVDA and should be grateful and not complain so much.  A small donation--even from unemployed blind people to NVDA would be in order.  Since it is well known that millions (I believe over 70 million at last report) of people in the world use NVDA, just imagine if everyone gave the equivalence of five dollars US a year.  That would be 350 million dollars US yearly. 

As far s as code factory Eloquence, I am having no problem with the SAPI 5 version of the product.  What issues are there with this product?

On 6/16/2022 11:31 PM, Ravindran V.S. wrote:

Dear Mike,

If my understanding is correct of your message,

Please note, ever since NVDA released as a free screen reader millions of Blind users have got into some kind of technical or computer literacy and use of technology.

If not still a vast majority would not be able to access computers due to the high cost of the commercial products.

Also, NVDA has created many job opportunities to many Visually Impaired Persons in several countries.

So, I urge that this should continue as the current way it is as an open source product and accessible to all Blind people.

People in the poor countries, and the developing countries are mainly depending on this screen reader. Who may be heavily using the product, but may not be in a position or afford to donate towards this cause.

Therefore, I kindly request to all the developers and contributors to keep  and continue this as an open source and free product, or at least to the people in the poor countries.

We even get the computers through donations, under this circumstances how could we spend hundreds or thousands of Dollars to the commercial Screen Readers?

I live in Sri Lanka, and now even we almost starving , under this situation cannot think of purchasing any screen reader or anything other than considered to be essential items.

Which some time may cost the job of the Blind people as well, who are depending on NVDA for their work .

So, for delay of any Add-Ons should not deny access of a screen reader for many Blind people.

Thank you in advance for understanding. NVDA is a blessing to many Blind.

Ravi.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mike mcglashon
Sent: Thursday, June 16, 2022 9:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Quoting:

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

End quote:

 

Amen to this.

If NVDA were a commercial software instead of “charitable open source code”, these practices might not be tolerated as easily.

I wish sometimes that NVDA would “actually charge” for its software instead of hiding behind “donations” then we could demand excellence.

It is strictly my belief that we as a society give too much leeway to “charitable” products.

 

I say these things as a “donor” to NVDA.

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, June 16, 2022 12:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

No, you’re not alone. It makes work also for the average user, who gets their NVDA just right with add-ons, only to find them broken in the next version.

 

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

 

All the best


Steve

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Wood
Sent: 23 May 2022 20:16
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

As a random interjection I find it quite disturbing how easily add ons are losing compatibility from one minor version to the next. This is a trend I as a user am not a fan of. It means more work for developers, more issues by the end user if add ons become unsupported, or at least, unsupported according to NVDA itself, and less time to actually make improvements for the developers who are already placing their doubtlessly limited and free time into this wonderful hobby of creating resources for NVDA to take advantage of.

I am truly curious to know what I, as a user, am benefiting from with this so called fragmentation. Previously add ons would work without issue, now it’s a guessing game as to which add ons will be disabled and stop working when I’d like to update NVDA from, again, one minor version to the next.

 

As it stands right now, I’m running a portable version of the latest NVDA due to the above, with my main install remaining an older version. Am I alone in viewing this slightly worrying trend?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mattias
Sent: Monday, May 23, 2022 10:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Lol we got the same answer..

 

Skickades från E-post för Windows

 

Från: Supanut Leepaisomboon
Skickat: den 23 maj 2022 12:18
Till: nvda@nvda.groups.io
Ämne: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

So I just got a reply from Codefactory, to a ticket regarding compatibility with NVDA 2022.1 that I submitted way back in April. Below is their response:
Good morning,
We are aware that a breaking NVDA update was released today.
We've been working on the addon, but unfortunately our update will take a few more days to complete.
Thank you for your patience.
The Code Factory technical team.

 



-- 
Signature:
For a nation to admit it has done grievous wrongs and will strive to correct them for the betterment of all is no vice;
For a nation to claim it has always been great, needs no improvement  and to cling to its past achievements is no virtue!



--
Quentin Christensen
Training and Support Manager


Re: In-Process AND a beta both out today

Quentin Christensen
 

Hi Robert,

Oh I am not voicist!  (Is that a word?  I don't have a specific preference of one voice over another).  I'm glad it is working even better for you now!



On Fri, Jun 17, 2022 at 1:36 PM Robert Mendoza <lowvisiontek@...> wrote:

Quentin ,

One thing I noticed when reading of my mother's tongue:
Tagalog is very clear and crisp.
I am using the default Voice: English (Great Britain) and Variant: Max
for the speach engine e-Speak ng.
I know you are not fun of the variant max though. LOL!
But, I was so impressed with the narration even a little dialects of my language is so clear.
Just to give you overview from the time I used NVDA max and alternately used variant quenzy as my choice.

I tested this out of curiosity as portable to my machine.
Cheers,
Robert Mendoza

On 6/16/2022 2:07 PM, Quentin Christensen wrote:
Our latest In-Process blog is now available!
Highlights from this issue:
- Spotlight on several new features and fixes you might have missed from NVDA 2022.1
- Info on the first beta of the upcoming NVDA 2022.2
- NV Access going to RSB Tech Fest, we hope to see you there next week!
- We chat with Vision Australia Radio's Focal Point program
- We have refreshed our LinkedIn page, come follow us!
- #NVeofy and more!

Read it now at: https://www.nvaccess.org/post/in-process-16th-june-2022/ 

--
Quentin Christensen
Training and Support Manager



--
Quentin Christensen
Training and Support Manager


Re: holding off on 2022.1 due to Code Factory dragging their feet

Monte Single
 

Yes, Ron,

 

And there is also a large group of people, in any aspect of society,  who trumpet loud and wide, “you get what you pay for”.

I am glad to make a small contribution   to nvda rather than supporting jaws.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: June 16, 2022 11:50 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Hi Group,

I hope NVDA never goes commercial.  In the US now-of-days, there is a persistent and radical libertarian philosophy that has taken hold of a large minority of the people saying in essence: 'If you don't pay, you don't play.'  Without getting into a political discussion on this issue, people who advocate this don't realize just what profound changes would result if this philosophy (as it appears likely) takes over the body politic entirely.  Just think of Europe from the middle ages to the nineteenth century. 

Having said that, people should be appreciative of the great work done by the creators of NVDA and should be grateful and not complain so much.  A small donation--even from unemployed blind people to NVDA would be in order.  Since it is well known that millions (I believe over 70 million at last report) of people in the world use NVDA, just imagine if everyone gave the equivalence of five dollars US a year.  That would be 350 million dollars US yearly. 

As far s as code factory Eloquence, I am having no problem with the SAPI 5 version of the product.  What issues are there with this product?

On 6/16/2022 11:31 PM, Ravindran V.S. wrote:

Dear Mike,

If my understanding is correct of your message,

Please note, ever since NVDA released as a free screen reader millions of Blind users have got into some kind of technical or computer literacy and use of technology.

If not still a vast majority would not be able to access computers due to the high cost of the commercial products.

Also, NVDA has created many job opportunities to many Visually Impaired Persons in several countries.

So, I urge that this should continue as the current way it is as an open source product and accessible to all Blind people.

People in the poor countries, and the developing countries are mainly depending on this screen reader. Who may be heavily using the product, but may not be in a position or afford to donate towards this cause.

Therefore, I kindly request to all the developers and contributors to keep  and continue this as an open source and free product, or at least to the people in the poor countries.

We even get the computers through donations, under this circumstances how could we spend hundreds or thousands of Dollars to the commercial Screen Readers?

I live in Sri Lanka, and now even we almost starving , under this situation cannot think of purchasing any screen reader or anything other than considered to be essential items.

Which some time may cost the job of the Blind people as well, who are depending on NVDA for their work .

So, for delay of any Add-Ons should not deny access of a screen reader for many Blind people.

Thank you in advance for understanding. NVDA is a blessing to many Blind.

Ravi.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mike mcglashon
Sent: Thursday, June 16, 2022 9:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Quoting:

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

End quote:

 

Amen to this.

If NVDA were a commercial software instead of “charitable open source code”, these practices might not be tolerated as easily.

I wish sometimes that NVDA would “actually charge” for its software instead of hiding behind “donations” then we could demand excellence.

It is strictly my belief that we as a society give too much leeway to “charitable” products.

 

I say these things as a “donor” to NVDA.

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, June 16, 2022 12:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

No, you’re not alone. It makes work also for the average user, who gets their NVDA just right with add-ons, only to find them broken in the next version.

 

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

 

All the best


Steve

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Wood
Sent: 23 May 2022 20:16
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

As a random interjection I find it quite disturbing how easily add ons are losing compatibility from one minor version to the next. This is a trend I as a user am not a fan of. It means more work for developers, more issues by the end user if add ons become unsupported, or at least, unsupported according to NVDA itself, and less time to actually make improvements for the developers who are already placing their doubtlessly limited and free time into this wonderful hobby of creating resources for NVDA to take advantage of.

I am truly curious to know what I, as a user, am benefiting from with this so called fragmentation. Previously add ons would work without issue, now it’s a guessing game as to which add ons will be disabled and stop working when I’d like to update NVDA from, again, one minor version to the next.

 

As it stands right now, I’m running a portable version of the latest NVDA due to the above, with my main install remaining an older version. Am I alone in viewing this slightly worrying trend?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mattias
Sent: Monday, May 23, 2022 10:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Lol we got the same answer..

 

Skickades från E-post för Windows

 

Från: Supanut Leepaisomboon
Skickat: den 23 maj 2022 12:18
Till: nvda@nvda.groups.io
Ämne: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

So I just got a reply from Codefactory, to a ticket regarding compatibility with NVDA 2022.1 that I submitted way back in April. Below is their response:
Good morning,
We are aware that a breaking NVDA update was released today.
We've been working on the addon, but unfortunately our update will take a few more days to complete.
Thank you for your patience.
The Code Factory technical team.

 



-- 
Signature:
For a nation to admit it has done grievous wrongs and will strive to correct them for the betterment of all is no vice;
For a nation to claim it has always been great, needs no improvement  and to cling to its past achievements is no virtue!


Re: holding off on 2022.1 due to Code Factory dragging their feet

Ron Canazzi
 

Hi Group,

I hope NVDA never goes commercial.  In the US now-of-days, there is a persistent and radical libertarian philosophy that has taken hold of a large minority of the people saying in essence: 'If you don't pay, you don't play.'  Without getting into a political discussion on this issue, people who advocate this don't realize just what profound changes would result if this philosophy (as it appears likely) takes over the body politic entirely.  Just think of Europe from the middle ages to the nineteenth century. 

Having said that, people should be appreciative of the great work done by the creators of NVDA and should be grateful and not complain so much.  A small donation--even from unemployed blind people to NVDA would be in order.  Since it is well known that millions (I believe over 70 million at last report) of people in the world use NVDA, just imagine if everyone gave the equivalence of five dollars US a year.  That would be 350 million dollars US yearly. 

As far s as code factory Eloquence, I am having no problem with the SAPI 5 version of the product.  What issues are there with this product?

On 6/16/2022 11:31 PM, Ravindran V.S. wrote:

Dear Mike,

If my understanding is correct of your message,

Please note, ever since NVDA released as a free screen reader millions of Blind users have got into some kind of technical or computer literacy and use of technology.

If not still a vast majority would not be able to access computers due to the high cost of the commercial products.

Also, NVDA has created many job opportunities to many Visually Impaired Persons in several countries.

So, I urge that this should continue as the current way it is as an open source product and accessible to all Blind people.

People in the poor countries, and the developing countries are mainly depending on this screen reader. Who may be heavily using the product, but may not be in a position or afford to donate towards this cause.

Therefore, I kindly request to all the developers and contributors to keep  and continue this as an open source and free product, or at least to the people in the poor countries.

We even get the computers through donations, under this circumstances how could we spend hundreds or thousands of Dollars to the commercial Screen Readers?

I live in Sri Lanka, and now even we almost starving , under this situation cannot think of purchasing any screen reader or anything other than considered to be essential items.

Which some time may cost the job of the Blind people as well, who are depending on NVDA for their work .

So, for delay of any Add-Ons should not deny access of a screen reader for many Blind people.

Thank you in advance for understanding. NVDA is a blessing to many Blind.

Ravi.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mike mcglashon
Sent: Thursday, June 16, 2022 9:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Quoting:

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

End quote:

 

Amen to this.

If NVDA were a commercial software instead of “charitable open source code”, these practices might not be tolerated as easily.

I wish sometimes that NVDA would “actually charge” for its software instead of hiding behind “donations” then we could demand excellence.

It is strictly my belief that we as a society give too much leeway to “charitable” products.

 

I say these things as a “donor” to NVDA.

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, June 16, 2022 12:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

No, you’re not alone. It makes work also for the average user, who gets their NVDA just right with add-ons, only to find them broken in the next version.

 

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

 

All the best


Steve

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Wood
Sent: 23 May 2022 20:16
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

As a random interjection I find it quite disturbing how easily add ons are losing compatibility from one minor version to the next. This is a trend I as a user am not a fan of. It means more work for developers, more issues by the end user if add ons become unsupported, or at least, unsupported according to NVDA itself, and less time to actually make improvements for the developers who are already placing their doubtlessly limited and free time into this wonderful hobby of creating resources for NVDA to take advantage of.

I am truly curious to know what I, as a user, am benefiting from with this so called fragmentation. Previously add ons would work without issue, now it’s a guessing game as to which add ons will be disabled and stop working when I’d like to update NVDA from, again, one minor version to the next.

 

As it stands right now, I’m running a portable version of the latest NVDA due to the above, with my main install remaining an older version. Am I alone in viewing this slightly worrying trend?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mattias
Sent: Monday, May 23, 2022 10:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Lol we got the same answer..

 

Skickades från E-post för Windows

 

Från: Supanut Leepaisomboon
Skickat: den 23 maj 2022 12:18
Till: nvda@nvda.groups.io
Ämne: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

So I just got a reply from Codefactory, to a ticket regarding compatibility with NVDA 2022.1 that I submitted way back in April. Below is their response:
Good morning,
We are aware that a breaking NVDA update was released today.
We've been working on the addon, but unfortunately our update will take a few more days to complete.
Thank you for your patience.
The Code Factory technical team.

 


-- 
Signature:
For a nation to admit it has done grievous wrongs and will strive to correct them for the betterment of all is no vice;
For a nation to claim it has always been great, needs no improvement  and to cling to its past achievements is no virtue!


Re: Language issue with NVDA

Sean Budd (NV Access)
 

Can you please test 2022.2beta1. I believe we fixed this issue in that release: https://www.nvaccess.org/post/nvda-2022-2beta1/ 

 

Kind Regards,

Sean Budd

NV Access Software Developer


Re: In-Process AND a beta both out today

Robert Mendoza
 

Quentin ,

One thing I noticed when reading of my mother's tongue:
Tagalog is very clear and crisp.
I am using the default Voice: English (Great Britain) and Variant: Max
for the speach engine e-Speak ng.
I know you are not fun of the variant max though. LOL!
But, I was so impressed with the narration even a little dialects of my language is so clear.
Just to give you overview from the time I used NVDA max and alternately used variant quenzy as my choice.

I tested this out of curiosity as portable to my machine.
Cheers,
Robert Mendoza

On 6/16/2022 2:07 PM, Quentin Christensen wrote:

Our latest In-Process blog is now available!
Highlights from this issue:
- Spotlight on several new features and fixes you might have missed from NVDA 2022.1
- Info on the first beta of the upcoming NVDA 2022.2
- NV Access going to RSB Tech Fest, we hope to see you there next week!
- We chat with Vision Australia Radio's Focal Point program
- We have refreshed our LinkedIn page, come follow us!
- #NVeofy and more!

Read it now at: https://www.nvaccess.org/post/in-process-16th-june-2022/ 

--
Quentin Christensen
Training and Support Manager


Re: holding off on 2022.1 due to Code Factory dragging their feet

Ravindran V.S.
 

Dear Mike,

If my understanding is correct of your message,

Please note, ever since NVDA released as a free screen reader millions of Blind users have got into some kind of technical or computer literacy and use of technology.

If not still a vast majority would not be able to access computers due to the high cost of the commercial products.

Also, NVDA has created many job opportunities to many Visually Impaired Persons in several countries.

So, I urge that this should continue as the current way it is as an open source product and accessible to all Blind people.

People in the poor countries, and the developing countries are mainly depending on this screen reader. Who may be heavily using the product, but may not be in a position or afford to donate towards this cause.

Therefore, I kindly request to all the developers and contributors to keep  and continue this as an open source and free product, or at least to the people in the poor countries.

We even get the computers through donations, under this circumstances how could we spend hundreds or thousands of Dollars to the commercial Screen Readers?

I live in Sri Lanka, and now even we almost starving , under this situation cannot think of purchasing any screen reader or anything other than considered to be essential items.

Which some time may cost the job of the Blind people as well, who are depending on NVDA for their work .

So, for delay of any Add-Ons should not deny access of a screen reader for many Blind people.

Thank you in advance for understanding. NVDA is a blessing to many Blind.

Ravi.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mike mcglashon
Sent: Thursday, June 16, 2022 9:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Quoting:

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

End quote:

 

Amen to this.

If NVDA were a commercial software instead of “charitable open source code”, these practices might not be tolerated as easily.

I wish sometimes that NVDA would “actually charge” for its software instead of hiding behind “donations” then we could demand excellence.

It is strictly my belief that we as a society give too much leeway to “charitable” products.

 

I say these things as a “donor” to NVDA.

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, June 16, 2022 12:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

No, you’re not alone. It makes work also for the average user, who gets their NVDA just right with add-ons, only to find them broken in the next version.

 

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

 

All the best


Steve

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Wood
Sent: 23 May 2022 20:16
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

As a random interjection I find it quite disturbing how easily add ons are losing compatibility from one minor version to the next. This is a trend I as a user am not a fan of. It means more work for developers, more issues by the end user if add ons become unsupported, or at least, unsupported according to NVDA itself, and less time to actually make improvements for the developers who are already placing their doubtlessly limited and free time into this wonderful hobby of creating resources for NVDA to take advantage of.

I am truly curious to know what I, as a user, am benefiting from with this so called fragmentation. Previously add ons would work without issue, now it’s a guessing game as to which add ons will be disabled and stop working when I’d like to update NVDA from, again, one minor version to the next.

 

As it stands right now, I’m running a portable version of the latest NVDA due to the above, with my main install remaining an older version. Am I alone in viewing this slightly worrying trend?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mattias
Sent: Monday, May 23, 2022 10:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Lol we got the same answer..

 

Skickades från E-post för Windows

 

Från: Supanut Leepaisomboon
Skickat: den 23 maj 2022 12:18
Till: nvda@nvda.groups.io
Ämne: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

So I just got a reply from Codefactory, to a ticket regarding compatibility with NVDA 2022.1 that I submitted way back in April. Below is their response:
Good morning,
We are aware that a breaking NVDA update was released today.
We've been working on the addon, but unfortunately our update will take a few more days to complete.
Thank you for your patience.
The Code Factory technical team.

 


Re: "Recognition failed" whenever I try to use NVDA+R

Joshua Tubbs
 

Oh... yes, I am using NVDA+R, completely missed the typo in my message. As for screen curtain, yes it is off. NVDA says Recognition failed every time though, and it wouldn't say it if it was on and would instead instruct the user to turn screen curtain off.
I'm just trying to figure out what would cause it to fail like this. Maybe I'll grab a portable version and see if it works but I doubt it.


On Thu, Jun 16, 2022 at 5:59 AM Luke Davis <luke@...> wrote:
Joshua Tubbs wrote:
> It worked for the longest time.
> Would recognition failed message be because the OCR engine isn't able
> to be ran?

Maybe. Have you recently started using screen curtain? I believe it doesn't
work when the curtain is on.

Brian's Mail list account via groups.io wrote:

> I'm a bit puzzled by the actual meaning of Cloud pc in this context.

Presumably he's remoting into a virtual server somewhere.

Luke







Re: Does NVDA have this feature that Window-eyes has?

Luke Davis
 

Brian Vogel wrote:

this is the regular expression one would use:(\+|-|\*|\=){3,}--
Brian, I have not tested the above, nor what I am going to say next, but I'm curious why you are re-inventing the bracket expression?

AFAIK, the Re above could be more efficiently, and clearly, written as:

[-*\+\=]{3,}

https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_03_05

A more complete separator line catcher might be:

[-*\+\=._]{4,}

I used 4 as the minimum, so it does not catch a non-UTF-8 ellipsis (...).

Luke

4461 - 4480 of 100970