Bob: > put this in the closeStack of the splash stack or the main stack?
As it says - the 'stack to build' - saving standalone from. > Also, isn’t the problem that when opening a stack Livecode detects > the stack being opened has the same name as one already in memory? As Jacqueline said: > The engine used to lock messages when building a standalone > but that was changed 4 years ago. Bob: > make backups of all your stacks first Of course, and don't mix/match methods, or ignore your project setup - Code in use 4 years, no issues; restores LC's own original SB technique! Best wishes, Curry Kenworthy Radically Innovative Christian LiveCode Development "PASSION for Elegant, Efficient Code!" http://livecodeconsulting.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
