Skip to content
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

Error when reading emails in windows live mail. #86

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 2 comments
Closed

Error when reading emails in windows live mail. #86

nvaccessAuto opened this issue Jan 1, 2010 · 2 comments

Comments

@nvaccessAuto
Copy link

Reported by cornelius on 2008-05-06 03:04
When reading Mails in Windows Live mail, NVDA sometimes generate errors.

ERROR - queueHandler.flushQueue:
Error in func processFocusWinEvents from eventQueue
Traceback (most recent call last):
File "queueHandler.pyc", line 52, in flushQueue
File "IAccessibleHandler.pyc", line 852, in processFocusWinEvents
File "IAccessibleHandler.pyc", line 773, in focus_winEventCallback
File "IAccessibleHandler.pyc", line 843, in focus_manageEvent
File "api.pyc", line 104, in setFocusObject
File "virtualBufferHandler.pyc", line 61, in update
File "virtualBuffers_old\MSHTML.pyc", line 76, in init
File "virtualBuffers_old\MSHTML.pyc", line 150, in loadDocument
File "virtualBuffers_old\MSHTML.pyc", line 339, in fillBuffer
File "virtualBuffers_old\MSHTML.pyc", line 222, in fillBuffer
File "virtualBuffers_old\MSHTML.pyc", line 344, in getDomNodeID
File "comtypes\client\dynamic.pyc", line 80, in getattr
File "comtypes\automation.pyc", line 550, in GetIDsOfNames
COMError: (-2147024891, 'Access is denied.', (None, None, None, 0, None))

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2008-05-30 01:10
Do these errors actually affect functionality or do they just generate annoying error sounds and log entries?

@nvaccessAuto
Copy link
Author

Comment 3 by mdcurran on 2009-04-14 00:33
The code causing this error no longer exists. If the error still occures with latest NVDA snapshots please reopen and include a new log error. From a quick test I have done, the error seems to be gone.
Changes:
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant