Re: When is a stack "dirty"?

> On Apr 8, 2015, at 12:29 PM, stephen barncard > wrote: > > On Wed, Apr 8, 2015 at 9:33 AM, Peter Haworth wrote: > >> Surely the IDE should be aware that a save is needed in those >> circumstances? >> > > I never thought about it. > I save save save save all the time anyway and never trust

Re: When is a stack "dirty"?

Thanks for the info Mark. That probably explains what is happening in my case because the substack I delete is not open at the time I delete it. What I'm thinking of doing is setting the gRevStackStatus element for the main stack of the deleted substack in my script which sounds like it should re

Re: When is a stack "dirty"?

Hi Pete, The variable gRevStackStatus["Short name of a stack"] is set to true whenever a control moves or changes as the result of user input. Messages triggering an update or gRevStackStatus are openField and focusIn for example. I think that moveControl and resizeControl are monitored too.

Re: When is a stack "dirty"?

Well I think that's my problem - I should be able to trust the IDE :-) Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin On Wed, Apr 8, 2015 at 12:29 PM, stephen barncard < stephenre

Re: When is a stack "dirty"?

On Wed, Apr 8, 2015 at 9:33 AM, Peter Haworth wrote: > Surely the IDE should be aware that a save is needed in those > circumstances? > I never thought about it. I save save save save all the time anyway and never trusted the IDE to remind me. -- Stephen Barncard - Sebastopol Ca. USA - Deeds No

Re: When is a stack "dirty"?

QCC # 15184 Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin On Wed, Apr 8, 2015 at 11:38 AM, J. Landman Gay wrote: > On 4/8/2015 1:15 PM, Peter Haworth wrote: > >> Couldn't the e

Re: When is a stack "dirty"?

On 4/8/2015 1:15 PM, Peter Haworth wrote: Couldn't the engine let the IDE know that a stack needs to be saved? I'd think so. It would be a good feature request. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com _

RE: When is a stack "dirty"?

>Peter Haworth Wrote: >I can't think of any other program I use where it's my responsibility to ensure I save any changes I make. I agree. The other day I changed a custom property and exited out of LC and it did not ask to save as I expected. So I restarted LC made the change again then saved man

Re: When is a stack "dirty"?

Couldn't the engine let the IDE know that a stack needs to be saved? I can't think of any other program I use where it's my responsibility to ensure I save any changes I make. It really makes LC look outdated. I think there's a global property in the IDE that indicates whether a stack needs savi

Re: When is a stack "dirty"?

On 4/8/2015 11:33 AM, Peter Haworth wrote: After several years of using Livecode, I still don't understand how the IDE decides when a stack needs to be saved when I quit from it. As an example, if I delete a substack by script then quit, the stack isn't saved. If I change the vale of a custom

Re: When is a stack "dirty"?

I agree. Even if you put data into a field externally, say from the msg box, you are not asked to save the stack upon closing. Craig -Original Message- From: Peter Haworth To: How to use LiveCode Sent: Wed, Apr 8, 2015 12:35 pm Subject: When is a stack "dirty"? After several year