Björnke von Gierke
bvg at mac.com
Tue Dec 7 20:32:15 EST 2010
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 "http://bjoernke.com/chatrev/chatrev1.3b3.rev"
More information about the Use-livecode