IDE Save

Peter Haworth pete at
Tue Dec 7 20:52:17 EST 2010

I'm not totally sure about this now but I think the circumstances  
involved using the "Save as Standalone" option.  I did that to create  
a new standalone and got the usual prompt about saving everything so  
assumed everything had been saved.  Only after I ran the standalone  
and found that the bug I had bee working on was still there did I  
realise that my changes hadn't been saved.

I don't think I've ever come across the lack of save problem when  
building a standalone before..

Pete Haworth

On Dec 7, 2010, at 5:32 PM, Björnke von Gierke wrote:

> Yes that is annoying.
> The problem here is that there's no assured way for the LC engine to  
> know wether a stack has been changed. Sure, the IDE tracks mouse  
> clicks, changed scripts and a few other things. But if for example,  
> you lock messages at the wrong point, then the IDE is unaware, and  
> thinks there's been no change.
> As a workaround there are auto save plugins that save for you every  
> 5 minute (or so). Even then, you will probably be forced to change  
> your workflow. I for example have just reviewed my behaviour, and it  
> seems i've gotten used to never quit the app, and never just close  
> stacks. Instead I save a stack, then close it, and only after each  
> stack is closed that way, I quit. By now, I even do this in the web  
> browser and text editor!
> On 8 Dec 2010, at 02:17, Peter Haworth wrote:
>> I just came across another instance of a pet peeve of mine.  I lost  
>> a couple of hours of scripting work because for some reason that  
>> isn't clear to me the IDE doesn't always save everything when you  
>> exit.  It asked me if I wanted to save and I confirmed that I did,  
>> yet a bunch of coding changes didn't make it.  The changes weren't  
>> in my application main stack but in another main stack containing  
>> scripts that I insert as front scripts.  Both stacks were loaded  
>> into memory at the time I exited.
>> I've been aware of save problems like this for a while and try to  
>> save things manually at regular intervals but didn't do so on this  
>> occasion.  But really, should a modern day development environment  
>> allow you to exit without saving your work unless you specifically  
>> tell it not to?  That seems like a huge bug to me.
>> Pete Haworth
> -- 
> official ChatRev page:
> Chat with other RunRev developers:
> go stack URL ""
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:

More information about the Use-livecode mailing list