I found the problem. The General Preference "if destroyStack is false..." was set to "Close the file". I don't recall setting it but I guess I must have. Somehow, "close the file" doesn't come across to me as removing it from memory but that is what it does. Pete lcSQL Software <http://www.lcsql.com>
On Mon, Mar 11, 2013 at 10:55 AM, Peter Haworth <p...@lcsql.com> wrote: > A stack that has been working fine has suddenly started misbehaving. > > When I close the stack by clicking the close button in the title bar, I do > not get a closeStack message. I verified this by setting a red-dot debug > break and a breakpoint command at the start of my closeStack message and > also looking at the output from the message watcher. > > Another oddity is that, although neither destroystack nor destroywindow > are set, when the stack is closed, it is removed from memory (doesn't > appear in the Application Browser), and any script editor tabs I have open > are closed. > > Any ideas what might be causing this? > > > > Pete > lcSQL Software <http://www.lcsql.com> > _______________________________________________ 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
