ok, thanks Ron. _____
From: Ron Parker [mailto:r...@gwmicro.com] Sent: Tuesday, April 05, 2011 8:58 AM To: gw-scripting@gwmicro.com Subject: Re: External Script, ProcessID and Second Test Output Results On 4/2/2011 1:36 PM, Chip Orange wrote: * what you pass into clientIdentify can be anything; they just want it to be unique, so they (gw) suggest it be the process id of your process. That's not actually true. It has to match the process that we launched in some way, so that we know which process to kill if your script doesn't terminate on receipt of the OnShutdown event. The process ID is the most reliable way to do that matching, but the name of the executable is often sufficient. The purpose of ClientIdentify is for your script to be able to say "Hi, I'm that process you just launched as a (possibly application-specific) script, not some non-script client that just happened to connect at the right time. Please give me access to my ClientInformation object."
