When is a stack "dirty"?

[Peter Haworth]

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 saving or not.  I guess I'll have to change my scripts to set it.

Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>

On Wed, Apr 8, 2015 at 10:40 AM, J. Landman Gay <jacque at hyperactivesw.com>
wrote:

> 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 property by script then quit, the
>> stack isn't saved.  Same thing happens if I add a new substack by script.
>> And if I change the value of a custom property by script.
>>
>> Surely the IDE should be aware that a save is needed in those
>> circumstances?
>>
>
> Basically it knows you made a change when you do something manually.
> Changing anything by script is sent directly to the engine and the IDE
> doesn't know about it.
>
> --
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>