Martin,
I tested both the C++ examples (late binding and early binding) on a
Windows XP and a Windows 7 64-bit. You didn't mention which operating
system you were using, how you associated the script or how you "exited"
the script. So it is hard to try and duplicate your steps but here is
what I did. I'm also assuming you are using Window-Eyes 7.11.
1) Under Windows XP SP3 with Window-Eyes 7.11
I unzipped both examples and manually copied in the two .exe files to my
%appdata%\gw micro\window-eyes\users\default directory. I manually
associated one of them globally and it immediately ran and the hotkey
control-alt-windows-h hotkey toggled as it should and when toggled on
the word "hello" was replaced with "howdy". I then stopped the script
and Window-Eyes continued to work fine as expected. I started the
script again and unloaded it and again it worked fine. I then
associated the second example and did the same and again it all worked
fine. So I'm not seeing your experience at all.
2) Under Windows 7 64-bit with Window-Eyes 711.
Here I did find a bug but nothing that would cause the experience you
had. We forgot to update the scripts so they were not able to connect
to the Window-Eyes application object. Because of this as soon as I
associated the scripts globally they immediately showed a state of
stopped. This is because our examples simply terminate if they are not
able to get the Window-Eyes application object. But again, the worst
thing that happened to me was the scripts didn't run but Window-Eyes had
no stability problems at all.
We have updated our scripts to work with Vista and above. You'll find
the updated .zip files in the same location as before. But these
updates were only to get them running on Vista and above but since you
said the script did run I'm guessing you had to be using Windows XP or
2000. In which case the updated scripts won't change your experience.
So I'm not sure where to go with your issue other then the original plan
of you calling support to give us exact information of what operating
system and the exact steps you took to get the script running and
stopped. Because at this point I'm not able to duplicate anything
instability issue.
Regards,
Doug
martin webster wrote:
Hi Doug,
Sorry for miss quoting you with regards to external scripts running slowly, all
so I don't think that the c++ examples are purposely bad I just feel the
VBScript is being pushed hard as the scripting language of choice and that
something may have been over looked here. I don't have to tell you that one of
window-eyes strongest scripting qualities is that any language that suports com
automation can be used and I just want to explore that a little. I will called
tech support about this issue, and I appologize if I sounded unnecessarily
turse and to the point.
Warm regards.
Martin Webster.
--- On Mon, 3/15/10, Doug Geoffray <geoff...@gwmicro.com> wrote:
From: Doug Geoffray <geoff...@gwmicro.com>
Subject: Re: my finding on the c++ examples.
To: gw-scripting@gwmicro.com
Date: Monday, March 15, 2010, 12:15 AM
Martin,
I'm surprised that you would think we would purposefully or
even unintentionally put up examples that would have such a
bad experience. Obviously (at least to me), this is
not normal behavior. Those examples have been up there
shortly after 7.0 was released. I'm not saying you are
lying but I am saying this is not normal behavior and you
would be best to call support so we can find out exactly
what is going on. I suggest you give us a little
benefit of the doubt before you assume the worst. Lets
work through this together.
Also, I never said the scripts would operate slowly.
I said out of process scripts would technically run slower
but because they are compiled languages it most likely
compensates. Either way, you most likely wouldn't
notice any difference. Please refer me to what exactly
I said as I would never say external script would run
slowly.
Regards,
Doug
martin webster wrote:
Hi all,
I just have to comment that after trying the c plus
plus examples provided by GWMicro I am disapointed.
They are awful. I heard doug jefriys say on various
audio tutorials that they would operate slowly, but that
wasn't the case. Whilst the script was actually
running things seemed just as you would expect - I mean by
this the instructions the readme file gave. When I
closed the example script with the script manager then there
was problems. It was like swimming through treackle,
it was not good and certainly not professional. It
left window-eyes in a bad state. It was like my early
attempts at playing with the connectEvent of the script
object. C plus plus is the programming language of choice
for professional programmers and this was not good, the
OnShutdown event seemed to be completely being ignored by
both parties - and by this I mean windows XP and
window-eyes, which left window-eyes in a slow a slugish
state. This was most noticable when
alt tabbing or tabbing. The only way I
could deal with this successfully was to shut window-eyes
down and restart with "control-alt-w) absolute rubbish.
regards.
martin Webster.
