Skip to content

Reintroduce Improve shortcut key reporting (#14900)#15373

Merged
seanbudd merged 3 commits into
nvaccess:masterfrom
CyrilleB79:revert-15237-i15233
Sep 6, 2023
Merged

Reintroduce Improve shortcut key reporting (#14900)#15373
seanbudd merged 3 commits into
nvaccess:masterfrom
CyrilleB79:revert-15237-i15233

Conversation

@CyrilleB79

Copy link
Copy Markdown
Contributor

Link to issue number:

Fixes #10807
Reintroduce the changes of PR #14900 that were reverted in #15237.

Summary of the issue:

See #14900 for the initial issue.

#14900 had to be reverted since it caused any speech sequence containing a character mode command to spell the whole speech sequence with Code Factory driver. Although the issue is in the driver and not NVDA, it has been decided to wait for an API-breaking release to issue this fix so that Code Factory synth users be not impacted by this bug.

Description of user facing changes

Same as #14900, that is:

Shortcut key reporting will be improved in some cases. This applies to on-demand reporting (shift+numpad2) as well as when "Report Object Shortcut Keys" option is checked in Object presentation settings.
The cases where it should be improved are:

  • punctuation key, e.g. "." (dot)
  • letter keys when the name of the letter is not spoken the same way as the equivalent one-letter word, e.g. "à" or "y" in French.
    Braille reporting should remain unchanged.

Description of development approach

Revert #15237 to reintroduce the changes in #14900 and remove change log modifications.

Testing strategy:

Re-execute the tests in #14900.

Known issues with pull request:

In addition to limitations listed in #14900:
This PR will trigger again Code Factory synthesizer's bug. The bug has already been reported to Code Factory; so they will have the opportunity to fix it for 2024.1 release.

Change log entries:

Bug fixes
Reporting of object shortcut keys has been improved. (#10807)

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 changed the base branch from beta to master September 5, 2023 09:31
@CyrilleB79 CyrilleB79 marked this pull request as ready for review September 5, 2023 11:12
@CyrilleB79 CyrilleB79 requested a review from a team as a code owner September 5, 2023 11:12
@CyrilleB79 CyrilleB79 requested a review from seanbudd September 5, 2023 11:13

@seanbudd seanbudd left a comment

Copy link
Copy Markdown
Member

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 535ae76 into nvaccess:master Sep 6, 2023
@nvaccessAuto nvaccessAuto added this to the 2024.1 milestone Sep 6, 2023
@CyrilleB79 CyrilleB79 deleted the revert-15237-i15233 branch September 6, 2023 06:59
seanbudd pushed a commit that referenced this pull request Oct 9, 2023
…5572)

Closes #15566
Fix-up of #14900 / #15373.

Summary of the issue:
In #14900 / #15373., spelling mode was used (CharacterModeCommand) no matter the state of the "Use spelling functionality" option.

The use spelling functionality exists because some old SAPI synth do not support spelling mode correctly. For them, this option needs to be honored.

Description of user facing changes
Use spelling functionality option will now be honored when reporting shortcuts.

Description of development approach
See logic in the code.
If use spelling functionality option is disabled, the key is just reported as is.
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.

Outlook 2010: No Shortcut Key Given for the To Button in the New Message Window

3 participants