Re: Quit on Close -- booby trap

Hi Sivakatirswami, Here you'll find a script, which makes sure that your application doesn't keep running as a ghost process in Windows: You might need to make a few adjustments, to stop and unload externals. Best, Mark -- Best regards, M

Re: Quit on Close -- booby trap

On Fri, May 23, 2008 at 1:30 PM, Sivakatirswami <[EMAIL PROTECTED]> wrote: > I presume that at least one "best practice" would be to *always* use the > > if the environment is "development" then > close this stack > else > quit > end if > > is that it? If not, please, what would the sa

Quit on Close -- booby trap

I've just been informed off line that I laid a booby trap into one of my example revOnLine stacks that I normally deploy as a standalone: on closestack quit # make sure we don't leave a hung process on the user's system end closestack which of course is going to cause any developer working in