Date   

Re: Vocalizer expressive that compatible with NVDA 2022.1

Rui Fontes
 

Hello!


No, it is not backward compatible.

That was the reason to not be published before the NVDA 2022.1 release...


You must update first NVDA and then Vocalizer-Expressive.


Best regards,

Rui Fontes
Tiflotecnia, Lda.



Às 16:14 de 24/05/2022, Mike Sedmak escreveu:

Rui, is the new 3.17 driver backwards compatible with nvda 2021.*? I'm
wondering if I can update the vocalizer driver first, or if I need to
update nvda to 2022 first.

Thanks,
Mike


On 5/24/22, Rui Fontes <rui.fontes@...> wrote:
Hello!


It is not yet published, but it is here:

https://www.tiflotecnia.net/ftp/vocalizer_expressive_driver-3.1.7.nvda-addon




Best regards,

Rui Fontes
Tiflotecnia, Lda.



Às 11:53 de 24/05/2022, Socheat escreveu:
Hi listers

So I just updated to NVDA 2022.1 today, and Tiflotecnia’s Vocalizer
expressive driver no longer compatible. I saw on this list some days
that Rui mentioned the latest driver is going to be updated, but as of
now, only the 3.1.6 was present on the website.

Thanks.






Re: Vocalizer expressive that compatible with NVDA 2022.1

Mike Sedmak
 

Rui, is the new 3.17 driver backwards compatible with nvda 2021.*? I'm
wondering if I can update the vocalizer driver first, or if I need to
update nvda to 2022 first.

Thanks,
Mike

On 5/24/22, Rui Fontes <rui.fontes@...> wrote:
Hello!


It is not yet published, but it is here:

https://www.tiflotecnia.net/ftp/vocalizer_expressive_driver-3.1.7.nvda-addon




Best regards,

Rui Fontes
Tiflotecnia, Lda.



Às 11:53 de 24/05/2022, Socheat escreveu:

Hi listers

So I just updated to NVDA 2022.1 today, and Tiflotecnia’s Vocalizer
expressive driver no longer compatible. I saw on this list some days
that Rui mentioned the latest driver is going to be updated, but as of
now, only the 3.1.6 was present on the website.

Thanks.






Re: Accessible Youtube video downloader?

 

hey did you try videoder? it is working vith nvda allso.


CodeFactory updated their download of the Eloquence/Vocalizer driver

Joseph Norton
 

Hi listers:

 

Code Factory has updated their own link for the Eloquence/Vocalizer driver.  They just updated the file, but, left the filename the same.  However, it is definitely changed, since I’m using it right now. They haven’t yet done the one branded for ATGuys, but, it doesn’t matter—their download also works with the licensing system.  Here’s the link:

 

https://www.codefactoryglobal.com/downloads/installers/codefactory-py3-1.0.nvda-addon

 

Hope this helps.

 

Sent from Mail for Windows

 


Question on up dates on Add On's

Dave Grossoehme
 

I am questioning if anyone has run into the Cloud Vision Add on being a problem.  I don't see it named in the out of compatible list.  Has there been any news on this add on?

DaveG


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

anthony borg
 

Hi Joseph

 

Many thanks for your great work you have done for us which I really appreciated.

 

Best regards

 

Anthony

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: 24 May 2022 08:09
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Hi,

Add-on Updater will offer latest VLC add-on automatically (version 2.14). This also answers the questions raised on a different thread about Emoticons but note that Emoticons and some other add-ons require NVDA 2022.1 to work (at least latest versions of those add-ons do). I advise checking the version of Add-on Updater you have and make sure it is 22.06 or later before checking for other add-on updates.

Cheers,

Joseph


Re: Addons for Nvda

Rui Fontes
 

Nop, I don't know the add-on and I don't use VLC...


There is nothing in the help file?


Best regards,

Rui Fontes
Tiflotecnia, Lda.


Às 07:58 de 24/05/2022, Jarek.Krcmar escreveu:

Hi Rui,


thank you for the link to download Vlc. But I have a problem: I can't select a volume, the keyboard doesn't work.

 I can't press even the key Pause.

Could you give me a claryfication, please?

Jarek

Dne 23.05.2022 v 21:47 Rui Fontes napsal(a):
Hello!


ClipSpeak is already updated on the add-ons page.. and in the spanish page of add-ons.

Esperanto symbols I don't know...


For VLC the spanish repository already have one add-on 2022.1 compatible, made by Paul Ber, and it is abailable at:

https://nvda.es/files/get.php?file=vlcaccessenhancement


Best regards,

Rui Fontes
NVDA portuguese team



Rui Fontes


Às 20:39 de 23/05/2022, Jarek.Krcmar escreveu:
Hello group,


I have today downloaded and installed the version of Nvda 2022.1, and I need some addons.

I have in Nvda these addons, uncompatible: Clipspeak, Esperanto symbols, Vlc media player.

I would like to know, whether they will be available.

Sincerely:





Re: Forgive this q. about end-block-quote and paragraph Editable

Steve Nutt
 

I agree with you Pen, it doesn’t matter what a default is, provided you can set it to your taste.

 

All the best


Steve

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Penny Golden
Sent: 14 May 2022 11:43
To: nvda@nvda.groups.io
Subject: Re: [nvda] Forgive this q. about end-block-quote and paragraph Editable

 

Thanks so much.  I don't care what default is, if only I can change it. 

Thanks so much for the info.

Pen

 

 

On 5/14/2022 5:36 AM, Gene wrote:

NVDA announces block quotes by default, a setting I have objected to in the past.

You can eliminate this announcement in the following way:
Open the document formatting dialog using the command control NVDA d.  That is, hold control and the NVDA key and type d while doing so.
Tab through the items and you will eventually get to block quotes.  It is a check box.  Uncheck it with the space bar, then press enter. 

You won't hear block quotes identified in places like e-mails or web pages. 

Gene

On 5/14/2022 5:29 AM, Penny Golden wrote:


Can I write emails without having these words come up?  I know it must be possible; and I know that I should be able to figure out what it is that I need to turn off.

Is there a way to get this extraneous wording out of the reading and writing process?

Sorry if this should be obvious.

Thanks.






 

 


Re: Vocalizer expressive that compatible with NVDA 2022.1

Rui Fontes
 

Hello!


It is not yet published, but it is here:

https://www.tiflotecnia.net/ftp/vocalizer_expressive_driver-3.1.7.nvda-addon


Best regards,

Rui Fontes
Tiflotecnia, Lda.
 


Às 11:53 de 24/05/2022, Socheat escreveu:

Hi listers

So I just updated to NVDA 2022.1 today, and Tiflotecnia’s Vocalizer expressive driver no longer compatible. I saw on this list some days that Rui mentioned the latest driver is going to be updated, but as of now, only the 3.1.6 was present on the website.

Thanks.


Vocalizer expressive that compatible with NVDA 2022.1

Socheat
 

Hi listers

So I just updated to NVDA 2022.1 today, and Tiflotecnia’s Vocalizer expressive driver no longer compatible. I saw on this list some days that Rui mentioned the latest driver is going to be updated, but as of now, only the 3.1.6 was present on the website.

Thanks.


Re: IMPORTANT: Clock and Calendar add-on is abandoned and end of support, no plans for future releases, use alternatives

Luke Davis
 

Hold your horses a bit on this. After Joseph's announcement, someone offered to get Clock and Calendar updated. It may take a bit to get worked out, but I suspect an update for the add-on will be along.

Luke


Re: when the speech history add-on will be available for NVDA 2022.1

 

This is the add-on I've been using:
https://github.com/davidacm/nvda-speech-history/
Jason Bratcher


Welcome to the NVDA Community Add-ons website - Speech Logger #nvdaaddonsfeed

Group Integration <nvda@...>
 

Speech Logger

  • Author: Luke Davis, with contributions by James Scholes
  • Download stable version
  • NVDA compatibility: 2019.3.1 and later

An NVDA add-on to log speech to a file or files. It can log speech generated on the local machine into a text file. It can also log speech from a remote machine received through the NVDA Remote add-on, either to the same or a different file.

Configuration

To configure this add-on, open the NVDA menu, go to Preferences, then Settings, then Speech Logger (NVDA+N, P, S, then press S until you get there, on a default U.S. English keyboard).

Note: the add-on can only be configured while in the Normal Configuration profile of NVDA. The add-on is not profile-aware. If you can think of some use case that requires it to operate differently in different profiles, please contact the author or file an issue on the GitHub repo.

The following settings are available: * The log directory. You can enter or browse for your desired destination directory, which must already exist. System variables such as %temp%, %userprofile%, etc., can be used in this field. * Local log filename. The created file will be placed in the above directory. This will contain speech logged while the local log mode is engaged. This can be the same as the remote log file. Leave blank to disable this kind of logging completely. * Remote log filename. The created file will be placed in the above directory. This will contain speech logged while the remote log mode is engaged. It can be the same as the local log file. Leave blank to disable this kind of logging completely. * Separator. This combobox lets you choose one of the available utterance separators. See below for more information. * Custom separator. This field lets you enter a custom utterance separator (see below), which is used if "custom" is chosen in the combobox.

Utterance separator

When NVDA speaks something such as "recycle bin 1 of 55" while it's reading your desktop, this is considered two separate utterances. The first one is the item name ("Recycle bin", in this example), and the second is the object position information ("1 of 55", in this example).

Depending on what you are reading, and how you have NVDA configured, there can be several separate utterances that happen during a single speech sequence.

In the normal NVDA log at debug level, each individual utterance is separated with two spaces, as it is written in the example above.

Speech Logger allows you to separate utterances in the same way NVDA does (with two spaces), or by one of a few reasonable alternatives (a newline, a comma and a space, two underscores), or by a custom sequence of your own devising.

If, for example, you wanted your utterance separator to be two dollar signs ($$), you would set the combobox to "custom", and enter "$$" (without the quotes), in the custom separator field. If you wanted it to be a tab, you could enter "\t".

Starting and stopping logging

This add-on has two gestures set by default. You can change them in the NVDA Input Gestures Tools category. Look for "Toggles logging of local speech" and "Toggles logging of remote speech". * NVDA+Alt+L: start/stop logging of local speech. * NVDA+Shift+Alt+L: start/stop logging of remote speech.

A note on remote speech logging

This add-on is intended to work with the NVDA Remote add-on, for logging of remote speech.

It is important to know, that it is not possible to start logging for remote sessions until you actually start one. There is no way to, for example, start logging, and have it wait, on stand-by, until a remote session starts, and begin logging at that time.

However, once started, logging will continue across remote sessions.

Feedback and feature requests

If you would like to suggest a feature or report a bug, please reach out by email, or file an issue.

As always, I appreciate hearing that my add-ons are useful, and what people are using them for.


Re: IMPORTANT: Clock and Calendar add-on is abandoned and end of support, no plans for future releases, use alternatives

Robert Doc Wright godfearer
 

I am running windows 11. The screen reader cannot manipulate any of the clock settings.



On May 23, 2022, at 7:04 PM, Eduardo Fermiano Luccas <25102008luccas@...> wrote:

what version of windows are you using? I've always used windows 10, and he's never had problems like this but, I don't know how it would be on windows 11

Em seg., 23 de mai. de 2022 às 17:38, Robert Doc Wright godfearer <godfearer@...> escreveu:

I found it but it is not accessible.

On 5/23/2022 8:00 AM, Ron Canazzi wrote:
Hi Group,

When Joseph refers to other apps such as Windows 10/11 Alarms and Clock app, is this an NVDA app or is it something built into Windows itself?

On 5/23/2022 4:33 AM, Joseph Lee wrote:

Hi everyone,

I see that Clock and Calendar add-on is not showing as compatible with just released NVDA 2022.1. There is a story to that:

A few months ago, folks from NVDA add-ons community reached out to the original author of Clock add-on about add-on maintenance, and the author noted that he will not be able to maintain it. I, the last known maintainer of this add-on, have long ago abandoned maintenance of this add-on (back in December 2021) with no plans for NVDA 2022.1 compatibility then. The add-ons community was and still is looking for maintainers of this add-on. But for now:

I hereby announce that Clock and Calendar add-on is abandoned and end of support. There are no plans for future releases, and compatibility with future NVDA releases cannot be guaranteed. Please use alternatives such as Windows 10 and 11 Alarms and Clock app or other apps and services offering time keeping/calendar/stopwatch/timer features. The add-on may become supported again if new maintainers step forward to maintain this add-on.

Thank you.

Cheers,

Joseph


-- 
Signature:
For a nation to admit it has done grevous 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!
-- 
******
Sometimes I think I understand everything,  and then I regain consciousness. 
---------
Family Times theatre
http://familytimes.wrighthere.net:9244/stream 
or ask your smart speaker to play family times on tune-in




--
eduardo fermiano luccas
joinville, brasil
músico e editor de áldio iniciante


Public service announcement before going off the air: please install Add-on Updater 22.06 BEFORE checking for add-on updates

 
Edited

Hello all,

This is the (final) public service announcement before going off the air:

In the midst of messages about NVDA 2022.1 and add-ons, someone reported that they are not getting recent add-on updates. After some discussion, it was determined that Ad-on Updater was not updated to the latest version available (22.06), with the person reporting that add-on updates were offered after installing Add-on Updater 22.06.

For folks wondering why you are not receiving add-on update notices after installing NVDA 2022.1, part of it may have to do with the version of Add-on Updater you have. As I explained countless times (sometimes with joy, sometimes with tears, most of the time with calm), Add-on Updater is one of the first add-ons made compatible with upcoming NVDA releases; in fact, Add-on Updater declares compatibility with a year.1 release as soon as beta 1 is released. This is so that by the time the stable version is released, Add-on Updater can start offering compatible add-on releases to you.

Short of making Add-on Updater a mandatory add-on, as I sign out for the time being, I seriously and sincerely recommend everyone to install Add-on Updater 22.06 (compatible with NVDA 2021.3 and 2022.1). Restart NVDA, and you may get add-on update notices. Plus, Add-on Updater will check for updated versions of itself. I leave you the direct download link for Add-on Updater 22.06 on your screens:

https://github.com/josephsl/addonUpdater/releases/download/22.06/addonUpdater-22.06.nvda-addon

 

See you in July. Thank you for all your encouragements and support (beep, beep, beep, static).

Cheers,

Joseph


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

 

Hi,

Add-on Updater will offer latest VLC add-on automatically (version 2.14). This also answers the questions raised on a different thread about Emoticons but note that Emoticons and some other add-ons require NVDA 2022.1 to work (at least latest versions of those add-ons do). I advise checking the version of Add-on Updater you have and make sure it is 22.06 or later before checking for other add-on updates.

Cheers,

Joseph


Re: Editing an NVDA Add-On Manifest file as a Temporary Workaround #adminnotice

Héctor Javier Benítez Corredera
 

Good morning, last year I created a small add-on to modify the manifests in a simple way.

This add-on has english translation and below I leave the translated manual.

This is the repository:

https://github.com/hxebolax/cricricri-para-NVDA

And from here you can download the latest version:

https://nvda.es/files/get.php?file=cricricri

As colleagues say changing the manifest is something that does not ensure its operation if the add-on requires internal changes in the code but in most cases if it will work to continue using the add-ons.

If I recommend to be attentive to the updates and to update the add-on even if it works with the changed manifest because the updates can bring changes in the code for a better performance.

Next I leave the manual of the add-on that is very simple and we will be able to change in a single blow all the manifests of our installed add-ons that we have chosen and in a simple way.

Manual of cricricri for NVDA
Small add-on that will help us to change the date of the manifests.
Now according to the latest NVDA policy and until further changes, every year in the first version of NVDA programmers will have to change the version to match their manifest to the NVDA version.
There will be programmers who will do it immediately, others who will take some time and others who simply won't do it due to add-on abandonment or any other reason.
In this last case we will have to make the change of the lastTestedNVDAVersion property by hand and if we have many plugins we will have to waste time, besides it is not a task for all users since there are many levels of users.
Also if we want to test the betas and RCs we will have to change this parameter in the manifests otherwise we will not be able to have the add-on installed.
Well cricricri helps us in this task doing the process for us and quickly.
Using cricricri
Cricricri can be launched from the menu Tools / Date changer for manifests or add a shortcut in Preferences / Input gestures and look for the category cricricri.
Once opened the window is simple we will have a list with our plugins and their version in the manifest.
We will be able to choose the ones we want.
If we tab we have two buttons, select all or deselect all, little to say this will act on the list of plugins.
If we tab we will fall in three combo boxes:
-
Select major version: This combo box has to match the date of the version that NVDA is going to have.
-
Select Minor version: Here it is enough to leave it in 1, however I have put the four annual versions in case there are changes (anything can happen).
-
Select a revision: In this combo box leaving it at 0 is enough, however I have put up to 5 also just in case.
If we tab we will fall in the button Apply changes to the manifests which will begin the process of modifying the manifests to those complements that we have selected in the list.
If we tab again we will click on the Close button which will close the window without doing any action.
Shortcut keys
- Alt+L: It takes us quickly to the add-ins list.
- Alt+S: Selects all the add-ons.
- Alt+D: It deselects all the plug-ins that are marked.
- Alt+A: It will start the modification of the manifests of those plug-ins that we have selected.
- Alt+C or Escape: It will close the window without making any action.
Author's comments
Well NVDA is a reader in constant evolution for what many times there are complements that remain in the way for lack of development and for lack of adapting them to the changes that NVDA in its evolution brings.
This means that changing the date in the manifests solves a momentary problem to be able to continue using those add-ons that are not updated or that the developer is slow to update them. But there will be add-ons that not only serves to change the manifest and need internal changes to adapt to new versions, in that case the add-on will break and only remains to contact the author of the add-on.
I advise you to update the plugins that come out with the changes in the manifests even if we have changed the date with cricricri because it is possible that these plugins bring apart from the adaptation of the manifest other modifications that the developer has made.
I am not responsible if something is broken by changing the manifests because there are hundreds of plugins and there may be some exceptions not contemplated by me.
The use of this add-on and its results is solely under the responsibility of the end user.
Translators and contributors:
- French: Rémy Ruiz
- English: Alberto Buffolino
- Turkish: : umut korkmaz
Change log.
Version 0.2.1.
-
Fixed a security bug in secure screens.
-
Fixed a problem with reloading add-ons in NVDA.
-
Added English language.

Regards
Translated with www.DeepL.com/Translator (free version)

El 23/05/2022 a las 22:46, Brian Vogel escribió:

Editing an NVDA Add-On Manifest file as a Temporary Workaround

Moderator's Note:
  This post is about exactly what it says, a temporary workaround.  This is NOT the way to truly fix add-on compatibility issues in many cases, but it will work as a temporary workaround for some in a pinch. You use these instructions completely at your own risk.

Note Well:  This will NOT always work when there is a backward compatibility breaking release of NVDA because, sometimes, add-on code must be changed.  But it sometimes works if nothing more than testing and certification is needed for a given add-on, and that’s a bit behind the actual NVDA release.  Also, the %APPDATA% folder is normally hidden, so if your machine objects to your trying to navigate there, you will have to take the steps to show hidden files and folders on your machine.

Your NVDA Add-Ons are found in the following folder:

%APPDATA%\nvda\addons

and you can type (or cut and paste) the exact path shown above into the Address combo box in File Explorer, and after hitting Enter that’s where you’ll be.  A list of folders corresponding to each of the add-ons you have installed will be in the file list.  Locate the add-on for which you wish to edit the manifest file and open its folder.

In the folder you will find a file with the name manifest.ini.  It is a plain text file, so can be opened for editing with any plain text editor of your choosing.  I use Notepad, but any text editor will do.

Once you have the file open for editing, search for the line that starts with:  lastTestedNVDAVersion =

You will be substituting the current NVDA version number for whatever is currently shown after the equal sign.  It is critical that there be a space after the ‘n’ in “version” as well as after the equal sign itself.  The NVDA version goes after that space after the equal sign.  If you check out the line character by character after the ‘n’ in “version” as you found it, you’ll encounter those spaces.  Just make sure that the equal sign has a space before it, and after it.

This will trick NVDA into believing that the add-on has been tested up to and including the current NVDA version number.

If an add-on crashes or otherwise misbehaves after using this workaround, then work on its code will be required.

If you use this workaround, and become aware that a version of your add-on that has actually been tested with the latest version of NVDA has become available, definitely take the time to install the real version.  Your doctored manifest.ini file will end up being overwritten as part of installing “the real thing.”

--

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

You can't crush ideas by suppressing them. You can only crush them by ignoring them.
     ~ Ursula LeGuin, The Dispossessed


Re: Addons for Nvda

Jarek.Krcmar
 

Hi Rui,


thank you for the link to download Vlc. But I have a problem: I can't select a volume, the keyboard doesn't work.

 I can't press even the key Pause.

Could you give me a claryfication, please?

Jarek

Dne 23.05.2022 v 21:47 Rui Fontes napsal(a):

Hello!


ClipSpeak is already updated on the add-ons page.. and in the spanish page of add-ons.

Esperanto symbols I don't know...


For VLC the spanish repository already have one add-on 2022.1 compatible, made by Paul Ber, and it is abailable at:

https://nvda.es/files/get.php?file=vlcaccessenhancement


Best regards,

Rui Fontes
NVDA portuguese team



Rui Fontes


Às 20:39 de 23/05/2022, Jarek.Krcmar escreveu:
Hello group,


I have today downloaded and installed the version of Nvda 2022.1, and I need some addons.

I have in Nvda these addons, uncompatible: Clipspeak, Esperanto symbols, Vlc media player.

I would like to know, whether they will be available.

Sincerely:



--
Jarek


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

Lenron
 

No you are not alone. Anyone have a link for the latest VLC addon. I
am so over having to lose addons every time I need to update

On 5/23/22, Shaun Oliver <blindman75@...> wrote:
why do people insist on posting stuff that is questionable if not
outright illegal on this list?


We've all been asked time and time again to refrain from doing so.



On 24/05/2022 9:50 am, Curtis Delzer wrote:

I have the IBM update for NVDA, and it is working with this version of
NVDA 2022.1 just fine.

It is as good as any eloquence, in fact the creator of the same
algorithm made this one.

https://od.lk/d/NjRfMjg2MzEwMDlf/IBMTTS-V21.03-Alpha1%28By-BHP%29.NVDA-addon

so, check it out.

On 5/23/2022 2:31 PM, Joseph Lee wrote:

Hi everyone,

A few clarifications before I crash with another headache:

Code Factory add-ons: while I cannot go into specifics, there was a
last minute change made in NVDA 2022.1 to keep many add-ons
compatible (specifically, control types refactor). I'm not sure if
Code Factory is referring to this issue (a while ago someone posted
that CF told folks that they are awaiting word from NV Access about
code change in 2022.1), but I imagine that folks over there are
working on compatibility updates.

Add-on update delays: it is normal to receive compatibility updates
with a delay when stable NVDA versions are released, more so when we
have a year.1 version (compatibility breaking release) in front of
us. Without going into details, around the time NVDA 2022.1 beta 1
was around the corner, add-on authors wrote to NV Access about
control types refactor (see the list archive from last year for an
overview from me about this) and that can break more add-ons than
anticipated. Therefore, NV Access decided to include a compatibility
layer for old and new add-on releases, which is why add-ons may
appear to work when you edit the manifest (addressed below). But for
all practical purposes, NV Access recommends using the new control
types code introduced in NVDA 2021.2.

As for manifests, as you read from Brian V a few minutes ago, working
with manifests is a temporary workaround until the actual update
declaring compatibility with the just released NVDA version becomes
available. Why is this method a temporary workaround?

1. 32-bit versus 64-bit Python: the reason why NVDA is a 32-bit
application (for the most part) is because it is running on top
of a 32-bit Python interpreter. There has been talks about moving
to 64-bit Python (and consequently making NVDA a 64-bit screen
reader), which requires a huge coordination between NV Access,
add-ons community, users, and other stakeholders - similar to, or
more than the work required to move from Python 2 to Python 3 (by
the way, as of May 2022, building add-ons with Python 2 is no
longer supported). Moving from 32-bit to 64-bit is not a simple
matter of instaling a 64-bit Python interpreter and get it to run
NVDA - it requires working with dependencies, including
third-party libraries which can come in either 32-bit or 64-bit
flavors, or in some cases, libraries needed to let 64-bit NVDA
talk to 32-bit components and programs. Add-ons are not free from
this - I would say add-ons require more work than the screen
reader itself as they can come with components that are purely
32-bit (most notable being 32-bit speech synthesizer DLL's); on
64-bit Windows, you CANNOT let a 64-bit executable (.exe) talk to
32-bit DLL and vice versa without asking someone (another
executable) to serve as a bridge and translate things on the fly
(won't go into details as it is quite technical (low-level,
literally) and don't want to go to the hospital right now). This
becomes more important if your favorite add-on(s) use Python
libraries with the extension of .pyd (Python extension DLL), and
recent Python releases will load compatible DLL's (32-bit pyd for
32-bit Python and vice versa). So imagine a scenario where a
64-bit NVDA is released and you edit the add-on manifest,
thinking that your favorite add-on(s) will work beautifully on
both 32-bit and 64-bit NVDA. I'll leave it up to you to imagine
what would happen when you restart NVDA.
2. NVDA code can come and go: while the biggest under the hood
change in NVDA 2022.1 (among other things) is control types
refactor, there are things that can be introduced in future NVDA
(and Python) releases that can make add-ons inoperable without
editing the add-on source code. Imagine a new version of NVDA is
released which is powered by a newer Python release (say, 3.10).
Even if the add-on manifest edits appear to work and the add-on
source code looks fine, it may not work correctly if it turns out
it is using parts of Python that is no longer present or changed
in some way. This becomes complicated if the add-on uses pyd
files - Python will load pyd files that are compatible with: the
version of Python you have and bit compatibility (32-bit Python
3.7 will load pyd files specifically designed for 32-vbit Python
3.7).

The biggest takeaway: EDIT MANIFESTS AS A LAST RESORT OPTION! Or, for
that matter, DO NOT EDIT MANIFESTS, or if you must do it, first
contact the add-on author BEFORE following what Brian wrote to you
several minutes ago.

P.S. I once thought about instructing Add-on Updater (in the future)
to present a message to anyone using add-ons with modified manifests
but decided against as it is draconian and requires Internet access.
But my sentiment remains: unless you know what you are doing, editing
manifests should not be attempted prior to doing everything you can
to contact the add-on author about updates. After all, it is not NV
Access who has final authority on add-ons - the ultimate authority
with add-ons rest with authors (including NV Access if they wrote
add-ons you are using); my statement on who has final (and ultimate)
authority on add-ons should also answer a question posed earlier: who
to call when add-ons become unmaintained (contact the last known
maintainer and/or the original add-on author (contact info can be
found in Add-ons Manager) and then let the community know).

Thank you.

P.S. This might be the last time I will address this subject (for
now; NVDA 2022.1 development and coordinating add-on compatibility
while studying for grad seminars (which I passed, by the way) was
rewarding and stressful; I didn't feel this tired and out of energy
since 2016 while organizing NVDACon that year, ended up lying on my
bed for a few days then).

Cheers,

Joseph
--
Curtis Delzer
H.S.
K6VFO
Rialto, CA
curtis@...




--
Lenron Brown
Main cell 985-714-8446
Cell: 985-271-2832
Skype: ron.brown762


Re: Whether or not recommending new NVDA user to set Capslock as NVDA key

William
 

I do programming as well, many variables and function names include both upper case and lower case.

and many of my passwords used in login in include upper and lower case.

So personally I do not use Capslock as NVDA key.

But for new NVDA users, I will try to explain to them the possible benefits and problems of setting Capslock as NVDA key and let them choose.

But many of them are newly blind people, and they do not have the knowledge to decide on themselves on whether they should set Capslock as NVDA key or not.




Carlos Medrano 於 24/5/2022 01:55 寫道:

Hmm. I usually tell people to try it both ways. Keep in mind that I'm considering this from the perspective of having key echo turned off and being really aggravated to find out that I've been coding for the last 5 to 10 minutes in upper case. Most programming languages are case sensitive, and depending on the programming style used, it's rare for me to write anything in upper case.


Having Capslock used as a modifier by NVDA makes it much harder for me to accidentally enable it in this particular case.


Hope this is helpful.


On 5/23/2022 12:38 PM, Bob Cavanaugh wrote:
Does JAWS have this option? The only reason I ask is because JAWS was
the first screen reader I used, and this was not the modifier.
Therefore, I've found it quite strange to use that key, even though
NVDA has had it as an option ever since I've been using it. It's also
why I wasn't a fan of the revamped Narrator when it came out, because
that was its only modifier. That being said, it's really user
preference as has been stated before.

On 5/23/22, Chris Mullins <cjmullins29@...> wrote:
Hi

I always set Caps Lock as an NVDA modifier Because as a touch typist, it is
more convenient to have a modifier key on each side of the keyboard to
facilitate command entry.   For the same reason, I always get an external
keyboard with 2 Windows keys.



I rarely type in all capitals so the double press of the Caps Lock to engage
capital input is not an issue as using the shift key is not difficult.



Cheers

                 Chris

Sent from Mail for Windows



From: William
Sent: 23 May 2022 04:14
To: nvda@nvda.groups.io
Subject: [nvda] Whether or not recommending new NVDA user to set Capslock as
NVDA key



Hi all,



I would like to ask for your opinion.



Some new NVDA users, including desktop and laptop owners, will ask for

my opinion on whether they should set the Capslock as the NVDA key.



With regard to desktop and laptop environment, the logic that I have

provided them are as follows:



1. setting Capslock key as NVDA key, you have to press the key two times

in order to input capital letters. But if you have to frequently press

the Capslock key to type capital letters, then setting Capslock key as

NVDA key will not be a good option.



2. setting Capslock key as NVDA key, you have one more option of NVDA

key, which you can choose from using the Capslock key or Insert key as

the NVDA key. But if you do not set Capslock as NVDA key, you will most

probably have to limit to pressing Insert key (laptop) or Insert key or

Numpad 0 (desktop).





How would you advice new NVDA users if they own a desktop or laptop

regarding this issue? thanks.

































5441 - 5460 of 101054