If anyone can do this, it’s john. he’s a master.
From: John Martyn DoItBlind
Sent: Friday, May 08, 2015 1:11 AM
To: sonarblindbeta@xxxxxxxxxxxxx
Subject: [sonarblindbeta] Re: Fwd: Sonar blind control surface issue
It seems to be going faster than normal now. I turned on the pre compiled
headers after I ran into the snag and things are compiling faster without
errors except the parts I am still working on. I ran into a compatibility issue
with the ITL file for visual studio, but I’ll resolve it when I have more tim.
Going to bed now. I will have to give this SDK back to cake walk for a better
support matter. Basically I’m sharing the code back with others so that they
can use their control surface for another project. I didn’t want Sonar blind to
be the only child on the block. This is basically for NVDA and window eyes
developers. Having this will be invaluable to them since not everyone can
afford JAWS.
Good night,
John
From: sonarblindbeta-bounce@xxxxxxxxxxxxx
[mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of Kevin Gibbs
Sent: Thursday, May 07, 2015 9:50 PM
To: sonarblindbeta@xxxxxxxxxxxxx
Subject: [sonarblindbeta] Re: Fwd: Sonar blind control surface issue
You poor bastard! God bless you!
Sent from my iPhone
On May 7, 2015, at 10:18 PM, John Martyn DoItBlind <John@xxxxxxxxxxxxx> wrote:
I’m working my ass off on this. I have to recompile this whole project from
scratch. The .Net framework simply doesn’t like the old code. I found code
referencing windows NT in it. That sucks. I’m hoping that I can make this thing
work better. I’m no C++ expert… yet… But after this, I think I will be. This is
a massive project. I had hoped that it would be easy, but nothing in this world
is. I’m just messing around for the code and paying attention to the framework.
I guess the guys at cake walk never updated this framework stuff into .Net. I
spent more than 100 hours this week. Probably around 150. It doesn’t bother me
to code like this. I used to go days doing computer stuff. Of course I wasn’t
on anything, I just loved it so much.
Oh well, back to work.
John
From: sonarblindbeta-bounce@xxxxxxxxxxxxx
[mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of Kevin Gibbs
Sent: Thursday, May 07, 2015 7:41 PM
To: sonarblindbeta@xxxxxxxxxxxxx
Subject: [sonarblindbeta] Fwd: Sonar blind control surface issue
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
