I see that I have misunderstood the context of this 'feature' (if that's what it is). It refers to a situation where one runs a script in the IDE, finds an error, corrects it and runs it again. It's entirely an IDE thing, isn't it? Compilation can happen outside the IDE, for example where a splash stack invokes other stacks containing scripts, but the developer doesn't see this directly so can't mess with the script and go again. I was thinking in a wider context, where the stack gets removed completely from the machine and then is brought back. That isn't what it's about.
Not quite so puzzled Graham On 23 Feb 2014, at 20:09, J. Landman Gay <[email protected]> wrote: > On 2/23/14, 12:17 PM, Bob Sneidar wrote: >> Could it be that editing the script resets the script local >> variables? This is true in Applescript properties. Editing and saving >> the script resets the properties to their defaults. > > Don't think so, that was one of my first tests when I tried to reproduce the > problem. I'm going with "script error" as the culprit for now. > > -- > Jacqueline Landman Gay | [email protected] > HyperActive Software | http://www.hyperactivesw.com > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
