Hi Rick,
I think each instance is its own but I may be wrong. The only conflict is
the process ID which I am sure you are concerned with. Try and see if your
instance is different, unless you are looking at the same events then that
would create a problem.
Also Rick, the Victory Associates software you were going to attempt to
work with had a virus inside of it. It is a good thing you did not work with it.
Bruce
Sent: Thursday, April 19, 2012 5:31 AM
Subject: WE And Global Scripts And Thread Safety
Hi Scriptors:
Does a Global Script run in it's own process with independent threads?
We pass the ProcessID to WE and it can be used for filtering Windows and
Messages
so I am wondering about whether shared (static) variable or data objects in
one Global
script could step on shared (static) objects of the same name and signature
in another
script or Client Application if they are not Windows or Messages.
In other words, are Global Scripts thread safe considering shared (static)
variables
and Data items?
I hope this question makes sense.
I have an external script that worked well when associated with a particular
application but had some problems when I made it a Global Script.
I have since pulled out code that used shared items and have made everything
instance objects but haven't had time to test it yet.
My guess was that I was stepping on my own shared objects since I used the
same objects in another application I was looking at and even in other global
test scripts I still had running since they were more or less useful.
I just would like to know if this is a possibility since resolving it is my
responsibility if that is the case, and yours too as scriptors.
If each script runs in it's own process independent of each other and
independent of the targeted application this might not be a consideration but I
dont think that is how it works.
WE needs communication among all facets of a session so I am guessing this
conceptual model needs consideration but would like to know the real deal so I
am not guessing.
Rick USA
