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 <p...@lcsql.com> To: How to use LiveCode <use-livecode@lists.runrev.com> Sent: Wed, Apr 8, 2015 12:35 pm Subject: When is a stack "dirty"? 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? Pete lcSQL Software <http://www.lcsql.com> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
