Quit on Close -- booby trap

[Mark Schonewille]

Hi Sivakatirswami,

Here you'll find a script, which makes sure that your application  
doesn't keep running as a ghost process in Windows:

<http://runrev.info/Quit%20your%20standalone.htm>

You might need to make a few adjustments, to stop and unload externals.

Best,

Mark

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Color Converter does what it says. Download it at http://economy-x-talk.com/cc.html

On 23 mei 2008, at 05:30, Sivakatirswami wrote:

> 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 the IDE  
> to suddenly watch his work disappear as Rev quits. Unsaved changes  
> would be lost as apparently the quit command over-rides Rev's built  
> in dialog to save stacks before quitting. My apologies to anyone who  
> had this happen to them.
>
> 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 sages say that *is* best  
> practice? and I will fix it.
>
> Thanks
> Sivakatirswami
>