Yes, that was my thought too. Unfortunately, I can't consistantly reproduce the duplicate stack part of the problem. Pete lcSQL Software <http://www.lcsql.com>
On Sat, Sep 15, 2012 at 11:24 AM, J. Landman Gay <[email protected]>wrote: > What it sounds like is that LiveCode is opening the new copy as a second > stack instead of replacing the original. Then it sees there are two stacks > with the same name and fails. It sounds like a bug to me. _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
