Date   

Re: Code Factory Vocalizer and Eloquence addon

Don H
 

Thanks for your response. I already tried that. Did not change
anything after I unchecked the beep and say cap options.

On 1/17/2022 6:30 PM, Gene wrote:
Try changing the settings to what you don’t want, then change them back
again.  Sometimes, settings in a program become incorrect and they may
be corrected if you ;put them as you don’t want them, then back the way
you do.
I doubt this is a general problem because if it were, I expect we would
have seen many comments before now.
Gene
-----Original Message-----
*From:* Rosemarie Chavarria <mailto:knitqueen2007@...>
*Sent:* Monday, January 17, 2022 6:20 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] Code Factory Vocalizer and Eloquence addon

Hi, Don,

It could be a code factory issue and not NVDA. I don’t know what to
suggest as I’m using the Nathan voice right now and it’s working fine
for me.

Rosemarie

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

*From: *Don H <mailto:lmddh50@...>
*Sent: *Monday, January 17, 2022 4:10 PM
*To: *nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject: *[nvda] Code Factory Vocalizer and Eloquence addon

Running the latest version of NVDA, Latest Win 10 and latest version of

the code Factory Vocalizer /Eloquence  addon.

I am using the Vocalizer Nathan voice and under speech settings I have

beep on Caps and Say Cap on Capitals unchecked.  This should mean I only

get a raise in pitch on Capital letters.  However what is happening is I

still hear Capital before each capital letter along with a pitch raise.

Is this a NVDA or Code Factory issue and is there a solution to stop

having NVDA say capital before each capital letter?

Thanks


Re: Finnish RHVoice for NVDA

Quentin Christensen
 

Good morning,

I can't comment on the need for Finnish voices (though you're unlikely to get too many people who say "No thank, we're not interested"!), but looking at our resources page: https://github.com/nvaccess/nvda-community/wiki/Connect

There is a Finnish language NVDA mailing list it might be worth asking on as well:


Kind regards

Quentin.

On Tue, Jan 18, 2022 at 11:25 AM Louder Pages <lp@...> wrote:
Hi,  

We build voices for RHVoice, the Open Source TTS with its own NVDA Add-On.

We have been doing some research into the Finnish language, but we want to understand the true need for another Finnish voice for NVDA.

Any comments from Finnish speakers would be greatly appreciated. Please contact us at inq at louderpager.org.

Kiitos kaikille.
  - Louder Pages



--
Quentin Christensen
Training and Support Manager


Re: Code Factory Vocalizer and Eloquence addon

Gene
 

Try changing the settings to what you don’t want, then change them back again.  Sometimes, settings in a program become incorrect and they may be corrected if you ;put them as you don’t want them, then back the way you do.
 
I doubt this is a general problem because if it were, I expect we would have seen many comments before now. 
 
Gene

-----Original Message-----
Sent: Monday, January 17, 2022 6:20 PM
Subject: Re: [nvda] Code Factory Vocalizer and Eloquence addon
 

Hi, Don,

 

It could be a code factory issue and not NVDA. I don’t know what to suggest as I’m using the Nathan voice right now and it’s working fine for me.

 

Rosemarie

 

 

 

Sent from Mail for Windows

 

From: Don H
Sent: Monday, January 17, 2022 4:10 PM
To: nvda@nvda.groups.io
Subject: [nvda] Code Factory Vocalizer and Eloquence addon

 

Running the latest version of NVDA, Latest Win 10 and latest version of

the code Factory Vocalizer /Eloquence  addon.

I am using the Vocalizer Nathan voice and under speech settings I have

beep on Caps and Say Cap on Capitals unchecked.  This should mean I only

get a raise in pitch on Capital letters.  However what is happening is I

still hear Capital before each capital letter along with a pitch raise.

Is this a NVDA or Code Factory issue and is there a solution to stop

having NVDA say capital before each capital letter?

Thanks

 

 

 

 

 


Finnish RHVoice for NVDA

Louder Pages
 

Hi,  

We build voices for RHVoice, the Open Source TTS with its own NVDA Add-On.

We have been doing some research into the Finnish language, but we want to understand the true need for another Finnish voice for NVDA.

Any comments from Finnish speakers would be greatly appreciated. Please contact us at inq at louderpager.org.

Kiitos kaikille.
  - Louder Pages


Re: Code Factory Vocalizer and Eloquence addon

Rosemarie Chavarria
 

Hi, Don,

 

It could be a code factory issue and not NVDA. I don’t know what to suggest as I’m using the Nathan voice right now and it’s working fine for me.

 

Rosemarie

 

 

 

Sent from Mail for Windows

 

From: Don H
Sent: Monday, January 17, 2022 4:10 PM
To: nvda@nvda.groups.io
Subject: [nvda] Code Factory Vocalizer and Eloquence addon

 

Running the latest version of NVDA, Latest Win 10 and latest version of

the code Factory Vocalizer /Eloquence  addon.

I am using the Vocalizer Nathan voice and under speech settings I have

beep on Caps and Say Cap on Capitals unchecked.  This should mean I only

get a raise in pitch on Capital letters.  However what is happening is I

still hear Capital before each capital letter along with a pitch raise.

Is this a NVDA or Code Factory issue and is there a solution to stop

having NVDA say capital before each capital letter?

Thanks

 

 

 

 

 


Code Factory Vocalizer and Eloquence addon

Don H
 

Running the latest version of NVDA, Latest Win 10 and latest version of the code Factory Vocalizer /Eloquence addon.
I am using the Vocalizer Nathan voice and under speech settings I have beep on Caps and Say Cap on Capitals unchecked. This should mean I only get a raise in pitch on Capital letters. However what is happening is I still hear Capital before each capital letter along with a pitch raise. Is this a NVDA or Code Factory issue and is there a solution to stop having NVDA say capital before each capital letter?
Thanks


Re: backing up NVDA settings

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

Yes, the NVDA settings are concentrated in very few files, and these files are very short (a few kilobytes). So one possibility for NVDA would be to automatically save backups of these files when setting changes are made, and keep these backups around for a while. If anybody "lost their settings", they could then get them back from these backup files.

Regards, Martin.

On 2022-01-18 04:35, Don H via groups.io wrote:
When you change the NVDA settings there are two files only within the
appdata/roaming/nvda folder being changed.  So only backing up those two
files would work rather than backing up the whole nvda folder at that
location.


Re: Proposal: a series of posts/articles on NVDA internals

David Csercsics
 

On a related note, if someone can speak Python, but is unfamiliar with Windows programming, how would they go about getting up to speed such that helping with NVDA development would be possible. I'd like to get back into programming seriously again, as I've got a lot of time and I might enjoy the project, but all of my programming experience is Linux or UNIX console. Definitely explaining how the screen reader works internally should be better documented for the curious, or for people doing accessibility testing.


Proposal: a series of posts/articles on NVDA internals

 

Hi all,

After looking at recent messages on this forum, I thought about proposing the following:

Most of you may know me as a code contributor to NVDA screen reader and author of several add-ons. But I don’t think many of you may know me as the producer of several NVDA tutorials, notably Welcome To NVDA series (2013, 2015, 2018); and no, I don’t think there will be a fourth edition of that tutorial series as NV Access sells Basic Training module and several community members are producing excellent tutorials. What I propose is something a bit different, something that was only seen on NVDA add-ons and development lists:

As I reflect on NVDA development and user interaction for the last ten years, I realize that the biggest missing piece of information is a document or two that explains NVDA internals to users so folks can appreciate how a screen reader works. Although we do have documents explaining NVDA internals from developers’ perspective, I understand that there is no such document from users’ perspective. Although I understand that folks can glimpse the screen reader from afar, I realize that some folks would like to know more about the actual internals of NvDA features, and in some cases, bugs.

The recent discussion on configuration profiles and backing up settings made it clear that the users community may benefit from a screen reader internals document. While anyone can see NVDA source code and figure out how things work, without context, folks won’t know how a feature fits into the overall picture.

Therefore I propose a series of articles/posts on NVDA feature internals at the user level. That is, upon request from the community, a series of posts will be written that explains how a feature works internally. The overall purpose of this proposal is to let users see what’s going on behind the scenes and appreciate the complexities (and not so complex parts) of screen reading technology. Obviously this will involve explaining NVDA source code, but just copying and pasting source code would not help many. Therefore I propose posts that use techniques such as storytelling to explain how NVDA features work behind the scenes. And no, I intend these series to not replace In-Process blog posts on feature overviews – I would imagine the posts I’m proposing are a bit geekier than blog posts. As for authorship, I hope I won’t be the only one writing these – I hope these exercises would serve as a way for would-be developers on this list to learn about talking to multiple audiences and discuss technical material.

To get started, tell us what is one feature in NVDA that you are really curious about how it works behind the scenes. To avoid this becoming a really lengthy thread that can go elsewhere, please do your best to write to me directly, or if you want, tell folks about the feature and talk to me directly with details. I will accept suggestions until January 23, 2022, at which point I will choose the top three requests and post internals about them, hopefully in February and March.

For a sample of the kind of writing I will post, take a look at add-on internals document for Control Usage Assistant:

cuaaddoninternals · nvdaaddons/DevGuide Wiki (github.com)

 

A bit geeky, but I hope you learn something useful. I expect the proposed articles/posts won’t be that geeky since the upcoming documents will be written with users in mind.

Also, if you are interested in learning more about the writing process for articles/posts like these, do ask me directly so I can look into leading a workshop on documentation writing, or perhaps something for a future NVDACon.

 

Cheers,

Joseph


Re: backing up NVDA settings

Gene
 

I believe I addressed your questions in my previous message.  I sent it before I saw yours.  I wouldn't inform the user of anything about what or where changes have been made.  I would display the same dialog any time any settings have  been changed.  Its up to the user to remember what changes were made and determine if he/she wants to save them. 


If you are saying there are technical problems with the program knowing when to display the dialog, that's a question I don't have the knowledge to address.


Gene

On 1/17/2022 3:28 PM, Joseph Lee wrote:

Hi,

Saving configuration is done in five steps:

  1. NVDA will see if it should save settings when exiting.
  2. If told to save settings, NVDA will first notify add-ons and other components that settings are about to be saved. This allows add-ons and other components to perform actions such as evaluating their own settings.
  3. Normal configuration is saved. This is mandatory.
  4. Modified configuration profiles are saved, if any.
  5. NVDA informs add-ons and other components that NVDA settings were saved. Add-ons will then perform actions such as saving their own settings.

A potential confusion can arise if NVDA is told to show config save prompt and:

  1. Multiple profiles other than normal configuration were edited.
  2. At least one of the modified profiles have multiple settings not saved yet.

Adding to the confusion is that:

  1. Internally, settings are stored as Python dictionaries, and settings (keys) are defined with text that are not easily translated for users. For example, show exit options is internally known as "askToExit", but in general settings it is labeled "Show exit options when exiting NVDA". Not all options are like this - in object presentation settings, "report notifications" is internally called "reportHelpBalloons". This is why the wording between nvda.ini is not the same as the ones shown in Settings screen.
  2. A setting may rely on more than one underlying configuration representation. For example, report indentation setting from document formatting panel relies on two flags: the actual line indentation reporting flag, and a flag indicating indentation announcement with tones. A bitwise operation is used to configure these flags for a total of four options: indentation off, indentation speech, indentation tone, indentation speech and tone.

Imagine a user is told about profile name and the exact setting that's different, and suppose the internal option names are used. Moreover, imagine the primary language of this user is not English. I hope you understand what I'm talking about.

Hope this helps.

Cheers,

Joseph


NVDA remote

Robert Doc Wright godfearer
 

Here is a thumbs up for remote. it allowed me to upgrade a pc in alabama while being in Colorado.
******
My drinking team has a bowling problem.
_______________
family times theatre
http://stream.wrighthere.net
 
ask your smart speaker to play family times on tuneIn
 
You can also find it on Ootunes


Re: backing up NVDA settings

Gene
 

I've read something about profiles and I've played a bit with a test profile.  If there is something I don't understand or am not taking into account, please let me know.


I think that any time any change is made anywhere, the dialog would come up.  Its up to the user to remember what changes he/she made and where.  As far as I can see, my proposal changes only one thing, that the user is asked so as not to accidentally or unintentionally have settings saved.  Whether the changes are made in a profile, the main program, or more than one profiles, I don't see how my proposal changes any behavior other than that the user approves or doesn't approve the saving.


It would be the same dialog.  It wouldn't specify whether the savings are in a profile or the main program nor in how many areas changes have been made.  The intent is to do nothing but prevent accidental or unintended saving of settings.


Gene

On 1/17/2022 1:43 PM, Gene wrote:

I'm not sure I understand your comments about profiles.  Are you saying that someone might change something in a profile, then go to another profile or back to the main program but they would be prompted when the program closes? 


Gene

On 1/17/2022 1:33 PM, Joseph Lee wrote:

Hi all,

A few things:

  1. Backing up settings somewhere: there is a facility in NVDA that will let add-ons react to settings save action. Using this facility, it is possible to create an add-on that will save settings to somewhere else so you can restore it later. However, this isn't effective when NVDA is exiting as add-ons will be gone by the time NVDA closes.
  2. Configuration profiles: one issue I have (as I also noted in a subsequent GitHub issue) is configuration profiles. Suppose a setting is introcued to alert users of settings changes when NVDA exits. What if the user exits NVDA while a profile other than normal configuration is active, and what if multiple profiles were edited? You might end up with a situation where you would save the wrong profile and discard the correct profile in regards to saving settings.
  3. Unexpected NVDA restart: suppose you change an important setting needed to resolve an issue you are having, and told NVDA to not save settings automatically. But suppose somehow NVDA restarts unexpectedly - perhaps an add-on has crashed NVDA (it is possible to crash NVDA with add-ons if they override functions provided by NVDA somehow or a DLL file performs unexpected things).

To focus on the original question at hand: a while ago it was proposed on GitHub and elsewhere to create a cloud backup feature to NVDA - that is, back up settings to the cloud and restore it later. The responses to this centers on possibility and logistics: it is possible to exchange data over the Internet, but how will NV Access keep track of which settings belongs to whom.

As for a related discussion on saving settings by default, if you think about it carefully, modern apps (Windows Settings, for example) will apply changes immediately. Even when we think about classic apps, save dialog applies to main content, not settings (tell us if changing view settings in Notepad without writing anything prompts a dialog to save settings). Even in Windows, unless you edit startup options or run Windows Preinstallation Environment (WinPE), settings are saved to Windows Registry even after you click OK to change settings. I won't go furtyher into this as the original question deals with backing up things, but I hope you get the idea.

Cheers,

Joseph


Re: backing up NVDA settings

 

Hi,

Saving configuration is done in five steps:

  1. NVDA will see if it should save settings when exiting.
  2. If told to save settings, NVDA will first notify add-ons and other components that settings are about to be saved. This allows add-ons and other components to perform actions such as evaluating their own settings.
  3. Normal configuration is saved. This is mandatory.
  4. Modified configuration profiles are saved, if any.
  5. NVDA informs add-ons and other components that NVDA settings were saved. Add-ons will then perform actions such as saving their own settings.

A potential confusion can arise if NVDA is told to show config save prompt and:

  1. Multiple profiles other than normal configuration were edited.
  2. At least one of the modified profiles have multiple settings not saved yet.

Adding to the confusion is that:

  1. Internally, settings are stored as Python dictionaries, and settings (keys) are defined with text that are not easily translated for users. For example, show exit options is internally known as "askToExit", but in general settings it is labeled "Show exit options when exiting NVDA". Not all options are like this - in object presentation settings, "report notifications" is internally called "reportHelpBalloons". This is why the wording between nvda.ini is not the same as the ones shown in Settings screen.
  2. A setting may rely on more than one underlying configuration representation. For example, report indentation setting from document formatting panel relies on two flags: the actual line indentation reporting flag, and a flag indicating indentation announcement with tones. A bitwise operation is used to configure these flags for a total of four options: indentation off, indentation speech, indentation tone, indentation speech and tone.

Imagine a user is told about profile name and the exact setting that's different, and suppose the internal option names are used. Moreover, imagine the primary language of this user is not English. I hope you understand what I'm talking about.

Hope this helps.

Cheers,

Joseph


Re: Microsoft Edge Suddenly Less Accessible with NVDA

Shawn
 

Search boxes like google have been becoming unreadable lately with Brave as well at times. The trick is to resize the window maximize or restore and it comes back until next time.

Shawn Klein

Sent from Mail for Windows

 

From: tim
Sent: Sunday, January 16, 2022 2:12 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Microsoft Edge Suddenly Less Accessible with NVDA

 

Try going through the settings and make sure they are what you want.

 

Because they have made updates to edge.

 

On 1/15/2022 12:12 PM, Rich DeSteno wrote:

> I have been using the current version of NVDA with the current version

> of Microsoft Edge on both Windows 10 and 11 with great success until

> recently.  Within the last few days, NVDA will no longer read the

> search term that I type in the search edit field. Also, when I press

> the Space Bar on a compressed listing of what other people ask, the

> contents open in a new window, so I must alt-tab to the other window

> to read the contents.  I assume these changes are either related to

> changes in Edge or NVDA.  Is anyone else aware of this or whether

> these problems will be corrected, or should I just give up and switch

> to Google Chrome?

 

 

 

 

 


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

Louise Pfau
 

Hi.  I just tried typing into a Google product search edit field with add-ons disabled, and I was able to replicate the issue.  I should note that the password edit fields appear to behave correctly.

Louise


Re: backing up NVDA settings

Gene
 

I've done almost nothing with profiles and I don't remember the little I did years ago.  I might have to read about profiles again to properly understand what you are saying.


As things are now, when you change a setting in a profile, then close NVDA whether you are in that profile or not, is the setting saved?  Are all changes everywhere automatically saved when using the default?  If so, how does the dialog change anything?  The user would answer yes or no and savings anywhere would be saved.  But if that isn't how profiles work, then the dialog might present problems and confusions I don't know about.


If the question is too involved to answer and I need to read about profiles to properly understand it, please let me know.


Gene

On 1/17/2022 2:08 PM, Joseph Lee wrote:

Hi,

As for profiles comment, consider the following scenario:

Imagine a user creates two configuration profiles: a manual profile, and an app-specific profile. With this set up, three profiles will be used: normal configuration, manual profile, and app-specific profile. Now suppose a feature to notify users about unsaved settings is implemented.

Now suppose this user activates the manual profile, called "profile 1". Then the user switches to the app-specific profile for an app, say Windows Terminal because the user needs to read terminal output, which takes place as soon as system focus moves to Windows Terminal window. now suppose the user opens object presentation settings panel from Windows Terminal window and tells NVDA to not announce object descriptions (by default, this setting is on).

Scenario 1: after changing settings, user exits NVDA while focused on Windows Terminal. NVDA says the current profile is not saved and offers to save changes.

Scenario 2: after changing settings, user moves to a different app and exits NVDA. NVDA will prompt to save settings.

Scenario 3: after changing settings, not only the user moves to a different app, but deactivates profile 1, the manual configuration profile, and then exits NVDA.

Scenario 4: after changing settings, not only the user moves to a different app and deactivates manual profile, the user creates a new profile and activates it. Then the user changes Windows OCR language and does not save settings, then exits NVDA.

Think carefully:

  • Scenario 1 is straightforward - at least the user thinks NVDA is presenting config save dialog while "focused" on Windows Terminal when in fact Windows Terminal profile is deactivated. Why? Because exit dialog is part of NVDA itself, not Windows Terminal, therefore the app is different and the Windows Terminal profile is deactivated.
  • Scenario 2 is a bit easier to understand on the surface but may confuse users without specifying exactly which profile is not saved.
  • Scenario 3 is similar to scenario 2 but with an important caveat: what if the user changes something from manual profile without saving it? If the setting is not changed, NVDA would have an easier time because only one profile needs to be saved. But if you do not save settings in more than one profile, then NVDA must present settings for multiple profiles.
  • Scenario 4 is perhaps the most complicated set up and demonstrates the question raised from scenario 3.

These complications arise due to how configuration profiles are organized and handled from NVDA, something I hope to write about when given a chance to do so. But suffice to say that configuration profiles handling uses at least three components: configuration maps, settings scope, and profile switch detection.

Cheers,

Joseph


Re: backing up NVDA settings

 

Well maybe for profiles, each profile could be its own ini file with all the settings for that app in it would that work?



On 18/01/2022 8:33 am, Joseph Lee wrote:

Hi all,

A few things:

  1. Backing up settings somewhere: there is a facility in NVDA that will let add-ons react to settings save action. Using this facility, it is possible to create an add-on that will save settings to somewhere else so you can restore it later. However, this isn't effective when NVDA is exiting as add-ons will be gone by the time NVDA closes.
  2. Configuration profiles: one issue I have (as I also noted in a subsequent GitHub issue) is configuration profiles. Suppose a setting is introcued to alert users of settings changes when NVDA exits. What if the user exits NVDA while a profile other than normal configuration is active, and what if multiple profiles were edited? You might end up with a situation where you would save the wrong profile and discard the correct profile in regards to saving settings.
  3. Unexpected NVDA restart: suppose you change an important setting needed to resolve an issue you are having, and told NVDA to not save settings automatically. But suppose somehow NVDA restarts unexpectedly - perhaps an add-on has crashed NVDA (it is possible to crash NVDA with add-ons if they override functions provided by NVDA somehow or a DLL file performs unexpected things).

To focus on the original question at hand: a while ago it was proposed on GitHub and elsewhere to create a cloud backup feature to NVDA - that is, back up settings to the cloud and restore it later. The responses to this centers on possibility and logistics: it is possible to exchange data over the Internet, but how will NV Access keep track of which settings belongs to whom.

As for a related discussion on saving settings by default, if you think about it carefully, modern apps (Windows Settings, for example) will apply changes immediately. Even when we think about classic apps, save dialog applies to main content, not settings (tell us if changing view settings in Notepad without writing anything prompts a dialog to save settings). Even in Windows, unless you edit startup options or run Windows Preinstallation Environment (WinPE), settings are saved to Windows Registry even after you click OK to change settings. I won't go furtyher into this as the original question deals with backing up things, but I hope you get the idea.

Cheers,

Joseph


Re: Apology to list members

Louise Pfau
 

Hi.  I hope you feel better soon.

Louise


Re: backing up NVDA settings

 

On Mon, Jan 17, 2022 at 02:33 PM, Joseph Lee wrote:
Configuration profiles: one issue I have (as I also noted in a subsequent GitHub issue) is configuration profiles. Suppose a setting is introcued to alert users of settings changes when NVDA exits. What if the user exits NVDA while a profile other than normal configuration is active, and what if multiple profiles were edited? You might end up with a situation where you would save the wrong profile and discard the correct profile in regards to saving settings.
-
All of your points are excellent, but when it comes down to it something this complicated is unlikely to be solved programattically.

This is one reason I believe that when one is tweaking settings, it is best done "a few at a time" and an assessment done after each of those few to see if they work.  If so, a manual save should be done.

There are just some things that require thought on the part of the user, and in a situation as complicated as the one you outline, that's the case.  No matter what would end up being done by NVDA in a situation like that, someone's not going to be happy.  But those someone's do have the ability to ensure that what they want is saved as soon as they know it is what they want, and that's what they should be doing.

There would be no way for NVDA to guess "what's most important" to someone in a scenario like that one, and even trying to do so is contraindicated.

(As a not entirely humorous aside, this is why I think the predictions of AI taking over the world are overhyped.  There are just too many things that require "shades of gray" that I have yet to see any AI come close to emulating.  But what it can do already is plenty scary enough in a number of contexts.  It is "better than a human" in some of those contexts where there's less preference and way more analysis of available information to take "the optimal path with the information available" while taking emotion out of it.)
--

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: backing up NVDA settings

 

Hi,

As for profiles comment, consider the following scenario:

Imagine a user creates two configuration profiles: a manual profile, and an app-specific profile. With this set up, three profiles will be used: normal configuration, manual profile, and app-specific profile. Now suppose a feature to notify users about unsaved settings is implemented.

Now suppose this user activates the manual profile, called "profile 1". Then the user switches to the app-specific profile for an app, say Windows Terminal because the user needs to read terminal output, which takes place as soon as system focus moves to Windows Terminal window. now suppose the user opens object presentation settings panel from Windows Terminal window and tells NVDA to not announce object descriptions (by default, this setting is on).

Scenario 1: after changing settings, user exits NVDA while focused on Windows Terminal. NVDA says the current profile is not saved and offers to save changes.

Scenario 2: after changing settings, user moves to a different app and exits NVDA. NVDA will prompt to save settings.

Scenario 3: after changing settings, not only the user moves to a different app, but deactivates profile 1, the manual configuration profile, and then exits NVDA.

Scenario 4: after changing settings, not only the user moves to a different app and deactivates manual profile, the user creates a new profile and activates it. Then the user changes Windows OCR language and does not save settings, then exits NVDA.

Think carefully:

  • Scenario 1 is straightforward - at least the user thinks NVDA is presenting config save dialog while "focused" on Windows Terminal when in fact Windows Terminal profile is deactivated. Why? Because exit dialog is part of NVDA itself, not Windows Terminal, therefore the app is different and the Windows Terminal profile is deactivated.
  • Scenario 2 is a bit easier to understand on the surface but may confuse users without specifying exactly which profile is not saved.
  • Scenario 3 is similar to scenario 2 but with an important caveat: what if the user changes something from manual profile without saving it? If the setting is not changed, NVDA would have an easier time because only one profile needs to be saved. But if you do not save settings in more than one profile, then NVDA must present settings for multiple profiles.
  • Scenario 4 is perhaps the most complicated set up and demonstrates the question raised from scenario 3.

These complications arise due to how configuration profiles are organized and handled from NVDA, something I hope to write about when given a chance to do so. But suffice to say that configuration profiles handling uses at least three components: configuration maps, settings scope, and profile switch detection.

Cheers,

Joseph

9301 - 9320 of 101047