A reaponse from Gordon on control serfaces.
Hi:
A while back I downloaded the newest control surface API and took a quick
look at the documentation. From what I was able to gather, it seems that
there have been changes to the protycols and of course classes that are used
as compared to the jSonar surface, which used a much older API. I;m not a C
plus programmer, so I can’t comment on what is going on with your DLL, but
I;m sure it is more difficult to receive the data coming back than it is to
send it. I hope you can get this working, it truly is the only way that true
access to Sonar X can be achieved.
Gord
From: Kevin L Gibbs
Sent: Monday, May 4, 2015 1:48 PM
To: Gordon Kent
Subject: Fwd: [sonarblindbeta] Sonar blind control surface issue
Gord,
Forgot. John’s e-mail is:
john@xxxxxxxxxxxxx.
Begin forwarded message:
From: John Martyn DoItBlind <John@xxxxxxxxxxxxx>
Subject: [sonarblindbeta] Sonar blind control surface issue
Date: May 4, 2015 at 11:32:35 AM CDT
To: sonarblindbeta@xxxxxxxxxxxxx
Reply-To: sonarblindbeta@xxxxxxxxxxxxx
OK, got the DLLs for x64 and x86. Everything is correct in the registry when
registering either DLL. Power shell sees it, jaws sees it. The object
creates successfully in jaws script. This is true for both versions of the
DLL. The jaws script knows that the object was created successfully. But
there is an issue. The calls to the DLL are not communicating with Sonar
platinum in 32 bit or 64 bit installations. I make sure to unregister the
DLLs properly and it does nothing when I issue commands to the DLL. I have
the control surface loaded in sonar as well. I am so lost as to why it is
not working. I must be missing something.
Any help or outreach is greatly appreciated. I even looked at JSonar to see
how commands were issued and no luck. I get nothing from the DLL. I have
triple checked the registry settings and everything is good. Power shell
reports the object just fine. Perhaps I should issue a command in
powershell. Please, everyone reach out to other developers in this issue
because as soon as I get the program communicating to the dll we are in good
standing.
Thanks,
John
