Running NVDA from launcher could invalidate user config for past installation #7688
Comments
One option to address this might be for the launcher to run NVDA with |
feerrenrut
added a commit
that referenced
this issue
Oct 25, 2017
When running from the launcher, dont upgrade NVDA config or move espeak voice dictionaries. Fixes #7688
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I haven't tested this with exact versions, so this is a bit theoretical at this point. However I'm fairly confident this could cause some hard to notice / track down issues.
Steps to reproduce:
Expected behavior:
The config file should remain as it was in the 2017.2 install, and not be affected by running from the launcher.
This goes for voice dictionary files as well.
Actual behavior:
Its likely that the config files get upgraded to the new schema. These changes are not necessarily backwards compatible, and might result in certain settings mysteriously different after running from the launcher. One example is the braille display cursor blink rate.
Moving the voice dictionary files could result in these files not being available anymore in the older install.
The text was updated successfully, but these errors were encountered: