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
To whom this may concern:
I do not think this is fair to
assume on the behest of the “average computer user”
(sighted or blind);
Many people hit buttons,
checkboxes, edit boxes, etc in hopes of getting their
computer to work the way “it used too”;.
The statement above expects the
patient to remember what he told the doctor on his
previous visit to verify his symptoms are legit;
Many of us, (including me…
Often hit buttons and other
controls to attempt to get the computer we wanted to do
something like before;
I do appreciate any technician to
walk me through a process to get us where we wish to be;
I appreciate the fact that they
expect that I would not remember such settings to get us
back or to where we need to be;
Hence, a techie can get a person
such as I back on the forest trail and continue with the
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.
On 1/17/2022 3:28 PM, Joseph Lee
Saving configuration is done in five steps:
- NVDA will see if it should
save settings when exiting.
- 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.
- Normal configuration is saved.
This is mandatory.
- Modified configuration
profiles are saved, if any.
- NVDA informs add-ons and other
components that NVDA settings were saved. Add-ons will
then perform actions such as saving their own
A potential confusion can arise if NVDA is told to
show config save prompt and:
- Multiple profiles other than
normal configuration were edited.
- At least one of the modified
profiles have multiple settings not saved yet.
Adding to the confusion is that:
- 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
- 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.