Date   

Re: NVDA Synthesizer Commands aren't working. Any suggestions?

Eduardo Fermiano Luccas
 

go to NVDA settings and go to the keyboard category, tap until you find the keyboard layout, and select desktop

Em sex., 14 de jan. de 2022 às 19:35, Nate Kile <theblindprogrammercorner@...> escreveu:

Hello all,

For some reason, the keystroke to change my NVDA synthesizer settings on the fly is not working. This is the key combination, NVDA + Control with the arrows. When I use the key combinations, it does nothing. If any of you have experienced this, or have some ideas to trouble shoot, it would be greatly appreciated.
 
Thank you,
Nate 


Re: NVDA 2021.3.1 cursor doesn't move in Google product edit fields

Nate Kile
 

I have also noticed this. It definitely impacts workflow.


On Fri, Jan 14, 2022 at 1:17 PM Gene <gsasner@...> wrote:
I haven’t tested with the browsers you have named but the Brave browser, another Chrome-based browser, displays this behavior in the Google search edit field.  I haven’t tried other edit fields. 
 
Firefox doesn’t display this behavior. 
 
Gene
-----Original Message-----
Sent: Friday, January 14, 2022 3:56 PM
Subject: [nvda] NVDA 2021.3.1 cursor doesn't move in Google product edit fields
 
Hi.  When I type into Google product edit fields like the search fields in Youtube or Google search, I can't move the cursor around the text using the ARROW KEYS unless I TAB out of and back into the edit field.  I tried both Microsoft Edge and Google Chrome with the same result, but they are both chromium-based browsers.  I only have those browsers installed on my computer, and they are both up-to-date.  This doesn't happen in other edit fields like the Windows search box.  I'm using Windows 10 Pro Version 21H2 (OS Build 19044.1466), NVDA 2021.3.1, Microsoft Edge Version 97.0.1072.62 (Official build) (64-bit), and Google Chrome Version 97.0.4692.71 (Official Build) (64-bit).  Has anyone else come across this?

Louise


NVDA Synthesizer Commands aren't working. Any suggestions?

Nate Kile
 

Hello all,

For some reason, the keystroke to change my NVDA synthesizer settings on the fly is not working. This is the key combination, NVDA + Control with the arrows. When I use the key combinations, it does nothing. If any of you have experienced this, or have some ideas to trouble shoot, it would be greatly appreciated.
 
Thank you,
Nate 


Re: NVDA 2021.3.1 cursor doesn't move in Google product edit fields

 

Well firefox 96 seems to have better processer handling and the latest 96.01 seems to handle displaying of some stuff a lot better to.

Security wize, its quite fast on release runs usually.

And after my own issue with firefox namely noscript I simply have gotten to understand that I just don't bother with that and well things run faster.

With privacy badger causing me issues and https everywhere no longer about.

The only things I use are an addon for rss feeds, I want my rss, add block+ and the extra sounds addon and thats it.

On chrome I use show you rss which does the same thing and add block +.

The addons dialogs on both thunderbird and firefox could be a little more accessible but on the other hand I don't need 1000 addons nore do I really see myself needing to add any more addons to anything.

In fact thunderbird has no addons what so ever.

The only issue that really gets me is that until there is say an file extention which is not included in default setups, I can't do anything till I try to download the thing the first time then I can adjust things.

If I say hide windows installer packages that also effects executable programs which I don't think should be correct.

It also doesn't reccognise nvda-addon files probably because its a weird format even though its just a zip file with a different name.

A while ago there used to be a custom file extention setting but that was ages ago.

These are gripes I have.

I also have the cpu and fan burn to hot when running things but its not like this amd unit has much to do otherwise and its not caused things to crash.

In fact firefox has been really constant from v90 onwards.

I have had waterfox a thing  I used till the end of 2019 get worse and worse to the point it was unusable.

Firefox had a bad patch and I was determined I'd never go back to firefox.

But since the last version that worked was  released august 2020 and I couldn't get any better releases after that that worked I decided to leave classic completely and move to g3.

G3 crashed and screwed up my system a lot and in fact waterfox is still recieving a lot of bad crap on the forums.

I decided to go back to firefox and while I had to leave noscript behind the display issues I had were gone and it worked.

It was a bit slower and crashed from time to time but at least it didn't crash all the time when I visited certain websites no one could find my issues in fact no one seemed to care that much saying nothing was wrong.

The users even told me it was in my head and or it was a problem with windows.

Nothing has changed and the bs has gotten to the point where some users have left.

Ever since waterfox switched to a new investment company it seems like this company is calling the shots rather than its original bosses.

I know firefox is not for everyone.

If you have a slow or an old system then you may not be able to handle it that well.


But it depends what you have loaded.

You really don't need a lot of stuff loaded with this.

I have checked firefox extentions and if you take out the 10-20 search extentions, the 5 or 6 decoders, my extentions which aparently seem to include a few things at least 3 or 4 things, and the mozilla updaters and such there isn't that much.

Some of these are double up so out of 42 different things its more like 20 or less and out of those well as I said its a mixed bag.

On edge most of these are edge related. and in chrome its worse.


Now mozilla has a lot of extra tracking and other stuff but compaired to chrome and or even edge mozilla has about the same components or slightly more than edge


On 15/01/2022 11:16 am, Gene wrote:

I haven’t tested with the browsers you have named but the Brave browser, another Chrome-based browser, displays this behavior in the Google search edit field.  I haven’t tried other edit fields. 
 
Firefox doesn’t display this behavior. 
 
Gene
-----Original Message-----
Sent: Friday, January 14, 2022 3:56 PM
Subject: [nvda] NVDA 2021.3.1 cursor doesn't move in Google product edit fields
 
Hi.  When I type into Google product edit fields like the search fields in Youtube or Google search, I can't move the cursor around the text using the ARROW KEYS unless I TAB out of and back into the edit field.  I tried both Microsoft Edge and Google Chrome with the same result, but they are both chromium-based browsers.  I only have those browsers installed on my computer, and they are both up-to-date.  This doesn't happen in other edit fields like the Windows search box.  I'm using Windows 10 Pro Version 21H2 (OS Build 19044.1466), NVDA 2021.3.1, Microsoft Edge Version 97.0.1072.62 (Official build) (64-bit), and Google Chrome Version 97.0.4692.71 (Official Build) (64-bit).  Has anyone else come across this?

Louise


Re: NVDA 2021.3.1 cursor doesn't move in Google product edit fields

Gene
 

I haven’t tested with the browsers you have named but the Brave browser, another Chrome-based browser, displays this behavior in the Google search edit field.  I haven’t tried other edit fields. 
 
Firefox doesn’t display this behavior. 
 
Gene

-----Original Message-----
Sent: Friday, January 14, 2022 3:56 PM
Subject: [nvda] NVDA 2021.3.1 cursor doesn't move in Google product edit fields
 
Hi.  When I type into Google product edit fields like the search fields in Youtube or Google search, I can't move the cursor around the text using the ARROW KEYS unless I TAB out of and back into the edit field.  I tried both Microsoft Edge and Google Chrome with the same result, but they are both chromium-based browsers.  I only have those browsers installed on my computer, and they are both up-to-date.  This doesn't happen in other edit fields like the Windows search box.  I'm using Windows 10 Pro Version 21H2 (OS Build 19044.1466), NVDA 2021.3.1, Microsoft Edge Version 97.0.1072.62 (Official build) (64-bit), and Google Chrome Version 97.0.4692.71 (Official Build) (64-bit).  Has anyone else come across this?

Louise


NVDA 2021.3.1 cursor doesn't move in Google product edit fields

Louise Pfau
 

Hi.  When I type into Google product edit fields like the search fields in Youtube or Google search, I can't move the cursor around the text using the ARROW KEYS unless I TAB out of and back into the edit field.  I tried both Microsoft Edge and Google Chrome with the same result, but they are both chromium-based browsers.  I only have those browsers installed on my computer, and they are both up-to-date.  This doesn't happen in other edit fields like the Windows search box.  I'm using Windows 10 Pro Version 21H2 (OS Build 19044.1466), NVDA 2021.3.1, Microsoft Edge Version 97.0.1072.62 (Official build) (64-bit), and Google Chrome Version 97.0.4692.71 (Official Build) (64-bit).  Has anyone else come across this?

Louise


Re: Tony's add-ons: updates and new features

Tony Malykh
 

Are you dealing with extremely long lines? Could you email me your file?

I just tried a file with 4000 lines and there is no perceptible delay when using WordNav 1.7 in VSCode.

On 1/13/2022 4:22 PM, Bruno Aníbal Prieto González wrote:
Hi,
Thanks for replying. Yes, I have word nav 1.7 installed. In large
files like 400 lines for example, it takes a couple of seconds to say
the word. Is there anything extra to do? I imagine it must be
something complex

2022-01-12 15:44 GMT-03:00, Tony Malykh <anton.malykh@...>:
Have you tried the latest version of WordNav? I improved its performance
in VSCode.

On 1/12/2022 4:31 AM, Bruno Aníbal Prieto González wrote:
Hi Tony!
Thank you so much for your awesome complements. Especially I am really
appreciating the noticeable improvement of indent nav speed in VS
Code. It's great!
I wonder if that improvement in the indent nav algorithm will be
transferable to Word Nav? VS Code doesn't behave as I would like when
navigating with Control and arrows, but with Word Nav it does. The
problem is that in larger files Word Nav causes NVDA to take a long
time to read the words.
Do you think there is a way to fix that related to how you did it with
Indent Nav?

Have a great year!

2022-01-11 17:19 GMT-03:00, abdul muhamin <abdulmuhamin600@...>:
Hello there, I’m facing a strange issue in  browser nav 2.2, whenever I
try
to use NVDA OCR, the up and down aero keys doesn’t work, at 1st, I
thaught
it’s the problem in the latest version of NVDA, and I downgraded to
2021.3,
but the problem was still there, then I restarted my NVDA with addons
disabled, and the keys were working properly, then, I enabled the addons
1
by 1, and I found this bug with Browser nav addon, please fix it.



Sent from Mail for Windows



From: David Ingram
Sent: Monday, January 10, 2022 8:48 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Tony's add-ons: updates and new features



I’d like to know how to get rid of ad-ons that are not compatible with
the
latest version of nvda?  thank you.



On Jan 4, 2022, at 5:39 PM, Rowen Cary <manchen_0528@...>
wrote:



Hello,

Thanks Tony, your add-on is very useful to me, thank you for your great
creation. For sound segmentation, is it possible to place the NVDA
sound
separately on the left or right channel without changing the multimedia
sound? This is useful for enjoying stereo resources.

Thanks again








Re: for people that don't like ribbon in office, new addon: ribbon explorer

Chris Smart
 

Not only that, but if you learn to use the ribbons as they are, instructions intended for sighted folks may be all you need to find things from then on, because You’ve done the work to learn to use the native interface with your screenreader.

 

 


Re: for people that don't like ribbon in office, new addon: ribbon explorer

 

On Fri, Jan 14, 2022 at 10:49 AM, Gene wrote:
When a sighted person uses an alternate interface to ribbons,
-
I will again emphasize, I have never seen a single "alternate interface" to the ribbons within programs or within things like File Explorer for the sighted.  It's virtually certain that somewhere, such exists, but these have never gained anything approaching wide acceptance if they are out there.  I've been working with Windows since the very first version, throughout the menu driven period, and now for all the years of the ribbon-driven period.  I have never seen anything that tries to make the ribbons back into menus for sighted users.  Just trying to do the visual overlay would be an absolute nightmare, I'd imagine.

The overarching philosophy in computing is that it is always best to, "Go with the flow of the native interface currently offered."  Many of us, including the sighted, have hated some of the changes as they've come along, but that's always been irrelevant.  At least the vast majority of the sighted have simply bitten the bullet and learned to use "what's happenin' now" and kept doing so as this changes in either evolutionary or revolutionary ways.  The notable exceptions to that rule being things like Classic Shell, Open Shell, Start10, and similar which attempt to make the Windows OS presentation, and specifically the start menu, look and feel like what existed under Windows 7.  But these shells do not extend much beyond that, and certainly do not have anything to do with the ribbons in Windows functions nor application programs.

It's often neither easy, nor pleasant, but it is necessary.  If someone actually knows of a "Ribbon Skinner" for the sighted, please point me to it, as I'd actually love to see what tortured method would be used to make an alternative that still allows access to the full complement of functions in a given program's ribbon.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


Re: for people that don't like ribbon in office, new addon: ribbon explorer

Steve Nutt
 

That's a bit like the virtual ribbon in JAWS.

I personally don't think it's the screen reader's job to change the interface to a program, except for example, virtual windows like web pages. I don't think there is any need to change the user experience of a program itself, it leads to possible support problems when Microsoft disability for example, try to support the user.

Good luck with the add-on, but I think a better approach is to learn the ribbon system.

All the best

Steve

--
To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

Computer Room Services
77 Exeter Close
Stevenage
Hertfordshire
SG1 4PW
T: +44(0)1438-742286
M: +44(0)7956-334938
F: +44(0)1438-759589
E: steve@...
W: https://www.comproom.co.uk

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Simone Dal Maso
Sent: 13 January 2022 14:45
To: nvda@nvda.groups.io
Subject: [nvda] for people that don't like ribbon in office, new addon: ribbon explorer

Hello,
Just a message to inform you that a new addon is born...
This is still in development stage and is for all people that don't like ribbon.
So, probably for 95% of you :-)))

Alberto Buffolino developed an addon to enhance experience with Ribbon menu. Only in Office products, for the moment.

I copy directly from the readme:

Important things to consider:
1. this add-on is in development;
2. confirmed (by users) to work on Microsoft Office 2019, 365 and 2021; 3. compatibility for old NVDA/Office versions is not guaranteed.
Usage
Simply install, open an Office application, press Alt to access Ribbon, and familiarize with new menu layout.
You can use arrows, tab, enter, esc, quite like in a normal menu.
Alt+down/upArrow are supported too, for expanding some controls.
If there are problems (please report), or you want temporarily interact without add-on assistance, press NVDA+space.

Some useful links:
download development version from
https://github.com/ABuffEr/ribbonExplorer/releases/download/dev/ribbonExplorer-20220112-dev.nvda-addon

For support please use the github page:
https://github.com/ABuffEr/ribbonExplorer/

Have fun!


Re: Tecnical question to devs.

Steve Nutt
 

I think it was the text you added to the link when inserting it.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: 12 January 2022 19:05
To: nvda@nvda.groups.io
Subject: Re: [nvda] Tecnical question to devs.

 

Devin,

Thanks.  Though I will say that the link I gave was correct, taken directly from the Freelists subscription page.

Why in heaven's name they didn't use either a capital 'L', to make that clear, or a font that differentiates lowercase 'l' from uppercase 'I' I do not know.  I thought it was someone's catchy idea for not spelling out 'eye'.

But when you are actually reading that page the 'l' after the "program-" and the "I" in "V.I." are visually indistinguishable.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


Re: Tecnical question to devs.

Steve Nutt
 

Hi Brian,

 

It’s program-l, not program-i.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: 12 January 2022 18:51
To: nvda@nvda.groups.io
Subject: Re: [nvda] Tecnical question to devs.

 

Gabe,

You are highly unlikely to get an answer to your queries (which are good ones) on this group since it is almost entirely composed of end users and is focused on end users of NVDA.

You really need to be asking this on a blind developer list, of which there are many.  One of the most recently recommended is the Program-I List for Visually Impaired Developers on freelists.org.  If Jackie and Joseph Lee both like it, that's recommendation enough for me.  I would strongly suggest you join and start asking away there, as the community is dedicated to just these sorts of questions.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


Re: for people that don't like ribbon in office, new addon: ribbon explorer

Gene
 

Brian and all


Whenever I hear about a nonstandard interface, I wonder if functionality is lost and what it is.  I'm not assuming anything about this alternate interface but I think that is something that should be asked about any alternate interface.


Also, this quoted statement is incorrect when  applied to ribbons:

"But then, like sight people can do, we can have a different type of approach and interface."


When a sighted person uses an alternate interface to ribbons, he/she can use the standard one, but doesn't like it.  In the case of blind people, a lot will use the alternate interface and not know how to use ribbons.  That is an important consideration because, as I wrote yesterday, using a nonstandard interface may limit a blind person's use of instructional material and the effectiveness of using help available on lists like this.


Gene

On 1/14/2022 9:01 AM, Brian Vogel wrote:

On Fri, Jan 14, 2022 at 03:29 AM, Simone Dal Maso wrote:
But then, like sight people can do, we can have a different type of approach and interface.
-
Which right there is the nonsense part.  I am sighted, we don't, and can't, have a different type of approach without the use of things like Classic Shell, Start10, or similar and that does NOT extend to the ribbon interface in programs.

I am universally critical of all of these "skinning" type programs (whether visible skinning or virtual skinning) because the only thing I've seen them do is create unawareness of how to use native interfaces, plain and simple.

They exist, people have the absolute right to use them, and I have the absolute right to discuss why I think they are very bad ideas and to get people to consider whether they actually want to use them or not, which is all I was trying to do.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


Re: for people that don't like ribbon in office, new addon: ribbon explorer

 

On Fri, Jan 14, 2022 at 03:29 AM, Simone Dal Maso wrote:
But then, like sight people can do, we can have a different type of approach and interface.
-
Which right there is the nonsense part.  I am sighted, we don't, and can't, have a different type of approach without the use of things like Classic Shell, Start10, or similar and that does NOT extend to the ribbon interface in programs.

I am universally critical of all of these "skinning" type programs (whether visible skinning or virtual skinning) because the only thing I've seen them do is create unawareness of how to use native interfaces, plain and simple.

They exist, people have the absolute right to use them, and I have the absolute right to discuss why I think they are very bad ideas and to get people to consider whether they actually want to use them or not, which is all I was trying to do.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


Version 22.01 of Joseph Lee's add-ons: now available via Add-on Updater and on community add-ons website

 

Hello everyone,

Version 22.01 of the following add-ons are now available via Add-on Updater and on community add-ons website:

  • Add-on Updater
  • Clock
  • Control Usage Assistant
  • Enhanced Touch Gestures
  • GoldWave
  • Resource Monitor
  • StationPlaylist
  • Windows App Essentials

 

In addition, a number of add-ons were also updated.

 

IMPORTANT NOTES:

  • The following add-ons are no longer actively maintained: Clock, Enhanced Touch Gestures, GoldWave, Resource Monitor, StationPlaylist. In case of Clock add-on, it is not my own.
  • Control Usage Assistant is now maintained by Noelia Martinez.
  • Add-on Updater: as I announced a few weeks ago, a future version of Add-on Updater will require NVDA 2021.3 or later. To prepare the community, starting from January 20, 2022, Add-on Updater will not offer updated versions of itself if you are using NVDA 2021.2 or earlier. Also, when it comes to issues when checking for NVDA updates on older releases, in addition to downloading NVDA 2021.3.1 manually, you can resolve this by installing Add-on Updater 21.10 or later (in this case, 22.01) from community add-ons website. At this point, I seriously encourage everyone to install a utility to update NVDA add-ons, including Add-on Updater.
  • Windows App Essentials: version 22.01 is the final version to support Windows 10 Version 20H2 (October 2020 Update). The next version of this add-on will require Version 21H1 (May 2021 Update) or later. At this point I urge everyone to at least upgrade to 21H1, or better yet, 21H2 (Version 20H2 will be supported for consumers until May 2022).

 

Thanks.

Cheers,

Joseph


locked Re: Update issues - NVDA 2021.1 & 2 along with Add-Ons in those two Versions #adminnotice

 

On Fri, Jan 14, 2022 at 08:54 AM, tim wrote:
Well if it solved. Then why does the same issue keep coming back, because not solved.
-
The answer is simple:  It doesn't keep coming back.

What's happening is the stragglers who are not updating on a timely basis, nor reading the forum about identified issues like this one, hit the issue much later than the majority and think it's new.  That, and only that, is the problem here.

This bug was solved, and remains solved.  I have yet to hear of a single, solitary person who's installed 2021.3 or later, even if they intentionally rolled back to an earlier version after having done so, having this update issue recur.

And with this post, the topic is locked.  This was not intended to be a discussion, but a way to let those who remained on earlier versions who are now encountering the update issue how to solve it.  And the solution is downloading the installer for the latest NVDA and running it, NOT trying to update from within NVDA itself in those earlier versions because since the problem lies with that mechanism that just doesn't work.
 
There is absolutely no reason to remove any user settings or add-ons to solve THIS particular problem, and it is a complete waste of time and effort to do so.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


Re: update error message

tim
 

Well its getting to look like so.

I haven't gotten it to work sense it started.

Always a reinstall to fix and then wonder what other add ons are broke again!

On 1/13/2022 3:30 PM, Ame wrote:

Hi all!

 

Just thought I’d see if there’s a new update so I went to the help menu and clicked check for updates.  I got an error.  All it said was “error checking for update.”  Is this a common thing lately?  Is there anything I can do?  This is the first time I’ve ever encountered this issue in my nearly 12 years using NVDA.   

 

Thanks a bunch.  I’ll appreciate any help you can give me.


locked Re: Update issues - NVDA 2021.1 & 2 along with Add-Ons in those two Versions #adminnotice

tim
 

Well if it solved. Then why does the same issue keep coming back, because not solved.

If you want to remove NVDA totally.

Just make sure the NVDA folder in program files x86\ NVDA and users\ your account\ apt data\ roaming\ NVDA are deleted.

Then when you reinstall it will find nothing left and install like new.

Without removing the apt data\ roaming\ NVDA folder. All problems with last install will still be there.

may take some time doing a clean remove, but you will waste less time and set it up better.

i never keep program settings, because that may be where the problem is.


On 1/13/2022 5:41 PM, Brian Vogel wrote:

We seem to keep having cycles of "the update issue" which is well known, and already solved, popping up again and again.  I am hoping this Admin Notice will help those who might encounter the issue to fix it just from having read this message.  Please file this if you are using NVDA 2021.1 or 2021.2 (or even some earlier version of NVDA) as you will almost assuredly need this information.

The update problem is cause by a certificate issue and a Windows-based certificate.  It is not a problem with NVDA, per se, but something that NVDA is seeking from Windows when trying to update.  This issue is fixed, permanently, with NVDA Version 2023.1.  The current version of NVDA as of this writing is 2021.3.1.

You cannot fix this problem by trying to update/upgrade from within NVDA, as that's the part that's broken.  You MUST download the latest version of NVDA from NVAccess and use that installer.   For NVDA 2021.3.1, the direct download link for the NVDA installer is:

https://www.nvaccess.org/files/nvda/releases/2021.3.1/nvda_2021.3.1.exe 

[As an aside, if you're ever looking for an older version of NVDA, just change the "2021.3.1" in both places in the URL with the version number you want.]

After you have the installer in hand, you can either uninstall the current version and then run the new installer (preferable), or do an install-over install by just running the new installer.  Both have worked in my experience, but the former is the one that ensures you are "clean as a whistle" before going forward.

If, by chance, you really need to be on a version of NVDA that is prior to 2021.3.1, then you can reinstall it afterward, and the issue that was causing the update to stall previously will still be fixed, as it is fixed by the certificate tweaking that the installer for 2021.3.1 does in folders not belonging to NVDA.  You can use the download link given above with the  release number changed to the release you want to get.

--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


Re: SentenceNav settings problem (Re: [nvda] Tony's add-ons: updates and new features)

Martin J. Dürst <duerst@...>
 

Hello Tony,

After fixing the problem myself by looking at examples from the FocusHighlight add-on and using some trial and error, I wanted to create a pull request. However, I found that the problem was already fixed, in a way very similar to mine, by CyrilleB79 in a commit 7 months ago.
Apparently, I had an old version, 2.11. I'll try to upgrade to the newest version soon.

Many thanks again for this great plugin!

Regards, Martin.

On 2022-01-13 04:18, Tony Malykh via groups.io wrote:
I can't fix this as I cannot see this myself. However, if you can fix this - pull request would be welcome.
On 1/10/2022 9:34 PM, Martin J. Dürst wrote:
Hello Tony, others,

I have another problem with the SentenceNav add-on settings panel. This seems to be a problem that only appears visually, not in speech.

What happens is that some of the settings (from "Sentence breakers" down to "Disaple SentenceNav in applications") are all shown on top of the first setting ("Volume of chime when crossing paragraph border"). Because they are on top of each other, only the last one of them is visible.

When I check the program, it seems that all the setting elements that are created via sHelper (gui.guiHelper.BoxSizerHelper) and all the settings with sliders (which use settingSizer, the second argument to the makeSettings) get some space, but all the other settings don't get space.

Because this is a problem of on-screen layout, it may be very difficult to debug. I'm ready to help as much as I can, but any advice regarding layout of settings dialogs is appreciated.

Regards,   Martin.


Re: for people that don't like ribbon in office, new addon: ribbon explorer

Simone Dal Maso
 

Hello,
just a short answer.
This addon was developed with the idea that people can choose a different type of interface.
All people should know how ribbon work and read tutorials and so on.
But then, like sight people can do, we can have a different type of approach and interface.

For example, I know very well the file explorer ribbon interface of windows10 and windows11. I teach this too, since I make lessons for visual impaired.
But on my computer, I use all utilities that remove the stupid ribbon interface and give me the classic menu bar.
This because ribbon for me is a terrible interface. So I have the opportunity to remove it, and my brain thanks me!
But it absolutely be clear that people must know them.
Anyway, I simply wrote a message to inform the list of this addon. I'm not involved on its development.

9641 - 9660 of 101195