Skip to content

Inform the user that the configuration cannot be saved from a temporary version of NVDA (launcher) #14914

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

Merged
merged 3 commits into from
May 31, 2023

Conversation

CyrilleB79
Copy link
Collaborator

@CyrilleB79 CyrilleB79 commented May 9, 2023

Link to issue number:

None

Summary of the issue:

When running NVDA temp version (from launcher), the configuration cannot be save due to possible compatibility of version scheme. When pressing NVDA+control+C, the configuration is not saved and a message is logged in the log. However, NVDA reports "Configuration saved".

Description of user facing changes

When running the temporary version of the launcher:

  • NVDA will not report erroneously that the config was saved when trying to save it with NVDA+control+C command.
  • NVDA will also not offer anymore the possibility to save the configuration in the NVDA menu.

Description of development approach

As when running in secure mode:

  • When trying to save the config, use the decorator to block action and report that the config cannot be saved in this version of NVDA.
  • Also removed the "Save configuration" item in the NVDA menu when running the temp version (launcher)

Testing strategy:

Manual tests:
Launched NVDA with and without the --launcher parameter and checked NVDA+control+C and the NVDA menu.

Known issues with pull request:

None

Change log entries:

Bug fixes
When running a temporary version from the launcher, NVDA will not let the users think that they can save the configuration. (#14914)

Code Review Checklist:

  • Pull Request description:
    • description is up to date
    • change log entries
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • API is compatible with existing add-ons.
  • Documentation:
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English
  • Security precautions taken.

@CyrilleB79 CyrilleB79 marked this pull request as ready for review May 9, 2023 22:03
@CyrilleB79 CyrilleB79 requested a review from a team as a code owner May 9, 2023 22:03
@CyrilleB79 CyrilleB79 requested a review from seanbudd May 9, 2023 22:03
Copy link
Member

@seanbudd seanbudd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @CyrilleB79

@seanbudd seanbudd merged commit 861c690 into nvaccess:master May 31, 2023
@nvaccessAuto nvaccessAuto added this to the 2023.2 milestone May 31, 2023
josephsl pushed a commit to josephsl/nvda that referenced this pull request May 31, 2023
…ry version of NVDA (launcher) (nvaccess#14914)

Summary of the issue:
When running NVDA temp version (from launcher), the configuration cannot be save due to possible compatibility of version scheme. When pressing NVDA+control+C, the configuration is not saved and a message is logged in the log. However, NVDA reports "Configuration saved".

Description of user facing changes
When running the temporary version of the launcher:

NVDA will not report erroneously that the config was saved when trying to save it with NVDA+control+C command.
NVDA will also not offer anymore the possibility to save the configuration in the NVDA menu.
Description of development approach
As when running in secure mode:

When trying to save the config, use the decorator to block action and report that the config cannot be saved in this version of NVDA.
Also removed the "Save configuration" item in the NVDA menu when running the temp version (launcher)
@CyrilleB79 CyrilleB79 deleted the noConfigSave branch June 1, 2023 11:40
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

Successfully merging this pull request may close these issues.

3 participants