Fix logged error when locking up the computer #95
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Woody
Here is a PR fixing a a little issue; there is no functional issue though.
Issue
When locking the computer (
Windows+l
)or switching to a secure screen, an error message is logged:The error is due to the fact that not all
NVDAObject
's areWindow
objects and thus, not all have awindowClassName
attribute. More specifically, the secure screen object is not an object corresponding to a real window.This error does not cause functional issue but having error that should be ignored in the log is disturbing when performing other debug tasks.
Solution
Try to get the
windowClassName
attribute and returnNone
if it is missing.