Fix say all error when on Desktop#10723
Conversation
|
CC @LeonarddeR |
fa424c9 to
c8bf59c
Compare
|
Can you please resolve conflicts, and then request a review from me. |
|
Can you mention why you chose not to re-raise the exception? With this current approach there is still |
|
For you, what is the exception which should be raise? |
|
I think it should raise |
|
I don't understand what I supose to do. |
|
I'm suggesting that you raise the exception in the init method, and where is used you catch that exception and return early. The class is used in only one place (inside method The benefit of this is that a half made instance isn't created. Then in |
See test results for failed build of commit 978b2da2da |
|
@clementb49 Are you planning to work further on this? It looks like only remaining think to be done is addressing a Linter error. |
feerrenrut
left a comment
There was a problem hiding this comment.
I don't think this needs a change log entry, I don't believe this is a user visible error in a release, though certainly annoying for alpha users.
|
There is still an error when pressing nvda+a on desktop (keyboard is laptop layout): This causes following user impact:
|
|
The only way to turn back to the settings before pressing nvda+a on desktop is to restart NVDA. Even activating and deactivating profiles does not work. The settings are not applied unless you restart NVDA. |
Link to issue number:
fixes #9947
Summary of the issue:
If say all was invoked in non-text, NVDA raise an error.
Description of how this pull request fixes the issue:
This PR check that the _TextReader object has an attribute reader
Testing performed:
Check that produce no error.
Known issues with pull request:
None
Change log entry:
None