thanks much Aaron for keeping me from banging my head against that wall! What exactly does the "stop script" or "disable script" cause to happen for the script? I mean, is onShutdown triggered? I should be able to use a timer to keep trying, and that should allow onShutdown to fire.
Chip -----Original Message----- From: Aaron Smith [mailto:[email protected]] Sent: Monday, May 25, 2009 8:55 PM To: [email protected] Subject: Re: trouble stopping a script Chip, The next version of Window-Eyes post 7.1 will be much more forceful about shutting down scripts that are stuck. In the meantime, you need some sort of condition that will cause your loop to return after a specific time has passed. Right now, If a script is stuck in a loop, Window-Eyes will not be able to shut it down without restarting scripting (maybe even restarting Window-Eyes). Aaron On 5/25/2009 12:39 PM, Chip Orange wrote: > Hi all, > > I have a script, which has a handler for onQuit and onShutdown. in > these handlers, at the very end, is even a stopScript command. > > in my script initialization I have a loop waiting on the application > to reach a specific operating state where the script is designed to function. > this happens after onQuit and onShutdown are setup. > > In these loops I have sleep commands and doEvents commands. > > even with all this, the script cannot be disabled or stopped, via the > script manager, if it's locked in the initialization loop because the > application it's associated with is having some unusual difficulty. > > so, what else can I possibly do to allow the script manager to stop > the script? > > thanks. > > Chip > -- To insure that you receive proper support, please include all past correspondence (where applicable), and any relevant information pertinent to your situation when submitting a problem report to the GW Micro Technical Support Team. Aaron Smith GW Micro Phone: 260/489-3671 Fax: 260/489-2608 WWW: http://www.gwmicro.com FTP: ftp://ftp.gwmicro.com Technical Support & Web Development
