Honor useSpellingFunctionality parameter when reporting shortcuts#15572
Conversation
See test results for failed build of commit 2daba6eda6 |
|
@seanbudd or any other reviewer: |
| class Test_getKeyboardShortcutSpeech(unittest.TestCase): | ||
|
|
||
| @classmethod | ||
| def setUpClass(cls): |
There was a problem hiding this comment.
Have you considered using unittest.mock.patch for replacing the function during the tests? When used as a decorator on these test classes you'll have much less of boilerplate code.
There was a problem hiding this comment.
It would be nice to have additional unit test confirming that when shouldUseSpellingFunctionality returns False, character mode commands are not used.
…r when Use spelling functionality is disabled.
|
@lukaszgo1, many thanks for the review! I am not used to |
See test results for failed build of commit 19e37f8b1f |
|
@lukaszgo1, I think you are a user of MathPlayer. |
See test results for failed build of commit eb162c0024 |
See test results for failed build of commit 8f1fa7a337 |
Link to issue number:
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.
Testing strategy:
Manual check:
CharacterModeCommandis used only when the "Use spelling functionality" option is enabled.Known issues with pull request:
None
Change log
None: unreleased issue.
Code Review Checklist: