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

nvdaHelperRemote: Handle cases where CoInitialize is called later than nvdaHelper is first injected #641

nvaccessAuto opened this Issue May 8, 2010 · 2 comments


None yet
2 participants

nvaccessAuto commented May 8, 2010

Reported by jteh on 2010-05-08 23:39
In most applications, CoInitialize is called before we are injected, so registering the IA2 proxy in that process works. However, in some applications such as Eclipse, this is not the case. For example, Eclipse brings up a splash screen when it is first loaded, which is where we get injected, but CoInitialize hasn't been called yet, so registering the IA2 proxy fails. As a result, all use of IA2 from NVDA fails until NVDA is restarted.
Blocking #256


This comment has been minimized.

nvaccessAuto commented May 8, 2010

Comment by jteh on 2010-05-08 23:42
(In #256) #641 is needed to fix the restart requirement.

Mick, it's possible that we could get Eclipse to call !CoInitialize earlier, which would avoid the need for #641. However, if it's likely to happen again in future, we may as well try to fix it properly on our side. Thoughts?


This comment has been minimized.

nvaccessAuto commented May 10, 2010

Comment 3 by jteh on 2010-05-10 22:04
Fixed in e652b05.
State: closed

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015

@nvaccessAuto nvaccessAuto added this to the 2010.2 milestone Nov 10, 2015

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