nvda

afa2f067 - Changes to make nvdaController local to the desktop NVDA is running on. This fixes a bug where nvdaControllerClient didn't work if NVDA had already been started on another desktop or another session, before the current copy of NVDA had been started.

Changes to make nvdaController local to the desktop NVDA is running on. This fixes a bug where nvdaControllerClient didn't work if NVDA had already been started on another desktop or another session, before the current copy of NVDA had been started. Also some other code cleanup. Specifically: *Add winIPCUtils, which contains a function: getNVDAControllerNcalrpcEndpointString, which can calculate an appropriate ncalrpc port name, that has the current session Id and desktop name encoded in the string. *Make sure all nvdaHelper code that creates an rpc client binding, or sets the nvdaController server protocol, uses getNVDAControllerNcalrpcEndpointString, so that nvdaControllerClient and nvdaHelperRemote can speak to a running NVDA on the same desktop. *nvdaControllerInternal interface: the implicit binding handle must be called nvdaControllerInternalBindingHandle, not nvdaControllerBindingHandle. *Initialize the nvdaController and nvdaControllerInternal binding handles in nvdaHelperRemote's dllMain. Previously nvdaHelperRemote's ia2LiveRegions initialization / termination code was initializing the nvdaControllerBindingHandle, and the nvdaControllerInternalBinding handle wasn't being initialized at all.