Can't Save As, Can't Build Standalone

[meerkat]

SYSTEM: I'm using Livecode Community 6.1 on a MacBook Air running Mac OS X (10.7.5)
APPLICATION: I'm developing an interactive "game" like program for use in a behavioural science lab experiment. As I develop I've been using Save As under the File menu successively, so I have MyGame-v301, MyGame-v302, etc.

PROBLEM 1: Earlier, I was saving and building standalones just fine. However, now when I load my latest version of MyGame, and the last few versions, the standard LiveCode File menu has many options disabled, including Save As and Save As Standalone. I can't seem to find any mode where those menu items are activated (Edit, Browse, Application Browser active, Edit Script window active.....nothing). As a result, I can't move forward.

PROBLEM 2: (potentially related so I note it here) When I go back to older versions of MyGame where I can build a standalone, the standalone builds OK but will not launch. In addition, on some previous runs I've gotten a alert saying I've got two versions of "answer dialog" in memory, or something like that.

I'd be grateful for any words of wisdom or suggestions!

[jacque]

It sounds like the destroystack property of your stack is set to false. That's the default. Destroystack determines whether your stack is entirely removed from memory when it closes. If it's false, then the stack is closed but retained in memory, and you'll get warnings about duplicate stacks if you open a second one of the same name.

You can deal with this a few ways. In the Files & Memory pane in preferences, choose the option to always set destroystack to true when creating new stacks. Then you don't have to worry about it from now on. For existing stacks, use the property inspector to set it. Save the stack. Now when you close it, it will be removed from memory.

If you don't want to permanently set the property, you can choose "Close and remove from memory" from the File menu whenever you close the stack. That does the same thing, but only for that one time.

I keep the preference set to true. Originally when computers were slower, this option allowed previously-accessed stacks to open more quickly because they were still held in RAM. It isn't necessary any more and there's no harm in keeping destroystack set to true.

[meerkat]

Many thanks! That has worked just fine and my standalones are building and starting properly.