force quit question

Jim McNeely jmcneely at
Fri Oct 3 14:30:19 EDT 2008

Thanks, guys, great info. Not that I would ever need to know any of  
this :^)


On Oct 3, 2008, at 11:11 AM, Eric Chatonet wrote:

> Bonsoir Jim,
> As usual, Jacque's reply is perfect.
> I'll just add that command/dot (may need shift to be correct:  
> depends on the platform and your system language) allows you to  
> stop any running script in the IDE unless you have specified 'set  
> the can't abort to true' at the beginning of your handler.
> Le 3 oct. 08 à 19:31, Jim McNeely a écrit :
>> Here is a (probably embarrassing) newbie question for you.
>> Suppose you put some ill-advised code in a file that results in an  
>> endless loop, and you have to force quit revolution. If you go  
>> back to that file and resume work, should you suppose that it is  
>> damaged, or should you assume that all is well except unsaved  
>> changes were lost?
>> In other words, what is the conventional wisdom in this  
>> circumstance, besides avoiding putting dumb endless looping code  
>> into your app?
> Best regards from Paris,
> Eric Chatonet.
> ----------------------------------------------------------------
> Plugins and tutorials for Revolution:
> Email: eric.chatonet at
> ----------------------------------------------------------------
> _______________________________________________
> use-revolution mailing list
> use-revolution at
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:

More information about the Use-livecode mailing list