Hi Chip,
Since you had found it out before, this works and anyone can try it,
just place your own path into it. The links are for WMI and probably could
be used for any external app as well. Since async does all the work, you
have to do your own using a timer since all of it is syncronous.
Bruce,
I remember reading now that some of the event call-backs from Excel also
don't work with WE; that is, just as you're finding WMI isn't able to call a
WE VBScript routine, I seem to recall that some of the Excell events can't
do so either. I suspect you've hit on the same interface issue th
Hi David,
It's a shame this part of WE was written with so little flexibility; as you
are finding, there is no way to install files into their own folder, and if
you do after installation, then you break the uninstall feature of WE (which
would normally remove these files from the users pc).
Al
Hi Chip, Ron, and Steve:
This here is the script that works on windows 7 as stated at the bottom
of the email. I still have to ask, why is it that this works as is, and it
is not a semi sync but an async call and does work in Windows7 but not
inside the WE ConnectEvent?
As I stated in my r
Hi Guys: Back awhile ago I was playing with using vb.net as a scripting
environment. There were problems with message processing and after some time I
gave up on the project.
Has anyone since then created a Real-World vb.net or C# script that uses some
of the WindowEyes methods related to windo
