I do something similar but it's a lot less trouble.

 Save the stack.
 Go to Finder /Explorer and duplicate it. Rename the copy.
Go back to LC and carry on with the original. You can update the name or any properties there.

Occasionally as I work I realize that I've implemented a lot of changes that I may not want to keep. So before I save the stack, I duplicate it in Finder so I have a copy of the one I'm working on as it was before I wrote myself into a corner. That's come in handy.

I don't have much trouble with the duplicate stack dialog because I always hit the Purge button which removes the first one from memory and opens the second one. I don't remember ever actually seeing a loop. If I want to work with two same-named stacks together I have two methods.

1. Open one of them in another copy of LC. I always have at least 3 different versions running at the same time, and yes, you have to be careful when you do that. I usually choose this method because most often I just want to copy a handler or a control.

2. Temporarily rename the first one slightly, open the second, do what you want, then close and remove the second one from memory and set the name of the first one back to normal.

None of this has ever required me to quit LC. I suppose now that I've mentioned it, something will happen...

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On October 6, 2021 7:04:07 PM "Brian K. Duck via use-livecode" <use-livecode@lists.runrev.com> wrote:

My process has become:
Save the file in LiveCode.
Close the file from LiveCode, purge from memory.
Switch to Finder (Mac) or Windows Explorer, or QUIT LiveCode,
Duplicate and rename the file,
Open the new file,
Return to LiveCode,
Rename the file in stack properties, if there isa version number in the stack name.

It may be needless to say, this is usually a 1x or 2x a day process.

TL;DR: don’t ’save as,’ save, close, quit LC, duplicate in finder / windows explorer, open new file, rename stack in stack properties - if there is a version no in the stack name.

Even then, I occasionally see the message. Then i repeat and QUIT LiveCode.

Sent from my iPad,
Brian Duck



Sent from my iPad
On Oct 6, 2021, at 12:57 PM, Sean Cole (Pi) via use-livecode <use-livecode@lists.runrev.com> wrote:

Hi all,
Can someone give the definitive answer as to what to choose when I save my
stack with a save as to create a new iterative version and it comes up with
the prompt :
     A stack with the same name as the one you are trying to load is
already open.
           Save    Purge    Cancel

Option 4: avoid the hassle.
_______________________________________________
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

Reply via email to