Skip to content

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

@nvaccessAuto

Description

@nvaccessAuto

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

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions