Skip to content

Do not allow to save some settings to disk while running NVDA from the installer #18171

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

Open
CyrilleB79 opened this issue May 27, 2025 · 0 comments

Comments

@CyrilleB79
Copy link
Collaborator

Steps to reproduce:

  • Run NVDA installer and continue with a temporary copy
  • Enter new words in the dictionary or remove some of them
  • Add some gestures in the input gesture dialog
  • Change some options in NVDA settings dialog and save the config with NVDA+control+c.

Actual behavior:

One can add new word in the dictionary and add input gesture. Only the config from NVDA settings dialog cannot be saved.

Expected behavior:

No parameter should be saved to disk when using temporary mode as done for NVDA settings. Indeed:

  1. If the way gestures are saved to disk is changed in the future (e.g. implemente layered gestures) but NVDA is finally not installed, one would end up with an invalid gestures.ini file.
  2. The same way, dictionary file format can change in the future; it has already been so in the past. This would cause invalid format in case NVDA is finally not installed.

NVDA logs, crash dumps and other attachments:

N/A

System configuration

NVDA installed/portable/running from source:

Temp version

NVDA version:

2025.1beta8

Windows version:

Windows 10 22H2 (AMD64) build 19045.5854

Name and version of other software in use when reproducing the issue:

N/A

Other information about your system:

N/A

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, but should be present on all previous versions.

If NVDA add-ons are disabled, is your problem still occurring?

Yes

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant