New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error when switching to another synthesizer when the change was previously made in a profile #14760
Comments
@fernando-jose-silva could you reproduce the issue with add-ons disabled and provide a log? Thanks. |
follows log with disabled addons. |
Note: Message edited: I was mentioning Rui instead of Fernando, sorry. Thanks @fernando-jose-silva. |
thank you very much for your attention. |
Cc @LeonarddeR: You have recently modified |
The relevant error:
It looks like the profile is corrupt, i.e. the volume is parsed as string, not as float. Is this an entirely new profile? |
I deleted the nvda.ini files, and reconfigured nvda. |
In that case @fernando-jose-silva, it would really help to know when this issue started occurring. Does it occur in 2023.1 and 2022.4? |
I have performed tests. The issue does not occur on 2022.4. It occurs on 2023.1beta1. |
I have tracked the regression to be introduced in commit 816496f (PR #14133). Previous commit 084db95 is running well. @seanbudd could you have a look to this regression since you are the author of #14133? Thanks. Note that I have used a slightly different way to reproduce the issue but it seems to me that it is the same root issue. STR:
Result: |
Also got just now another error related to value coming from the config
The code line is the following: NVDA 2023.1; Windows 10 2004 (x64) build 19041.388. |
Fixes #14760 Fixup of #14133 Summary of the issue: When saving a config spec, validation would be skipped if the string value of the data is unchanged. This caused various issues including config values not being correctly converted to numbers from strings when validating. This caused config profiles to fail to load or save correctly. Description of user facing changes Fix up of various bugs related to user config Description of development approach Perform special handling that was introduced in #14133 for feature flags only
Steps to reproduce:
First of all, apologies if I'm too imprecise, as I don't know what causes the problem, I'll try to show my whole scenario.
First create a profile for word.
In this profile I have configured nvda to read column and cell information in tables.
Now in the normal settings profile besides several settings I have configured nvda to use the rh voice synthesizer.
It is worth saying that I think that to reproduce this problem it is possible to use a profile of settings for any program, the most important thing is that in the normal profile the voice is defined for the rhvoice synthesizer and in the profile for word there is not even a defined voice, so he is using the rh voice too, derived from the normal profile.
Perhaps this is reproduced with another synthesizer besides the rh voice.
in summary:
normal perfio using rhvoice voice and not reading table info.
perfio word using rh voice inherited from normal perfio and reading table positioning information.
Now open word
press nvda + ctrl + s choose with the arrow keys the one core synthesizer and press enter.
so far everything ok.
I don't know if it matters how these screens are opened, so I'm describing how I opened and used them.
now press windows+d to go to desktop.
Now nvda should be using the rh voice synthesizer defined in the normal profile again.
reopen the synthesizer screen with nvda + ctrl + s.
from there with the arrow keys to the one core synthesizer and press enter.
Actual behavior:
nvda reports that there is an error in the one core synthesizer and does not change the normal profile synthesizer.
Expected behavior:
nvda should switch to the one core synthesizer for the normal profile as it is already in use in the word profile.
I remembered, the profile for word is configured to be activated automatically when entering word.
System configuration
NVDA installed/portable/running from source:
instaled e portable
NVDA version:
nvda.exe, NVDA alpha-27948,bc3e97dd
Windows version:
10 19045.2728
Name and version of other software in use when reproducing the issue:
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
no
If add-ons are disabled, is your problem still occurring?
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
yes
log:
voz.txt
The text was updated successfully, but these errors were encountered: