Backing up a stack; problems with save as

[Klaus]

Yes, that's what I wrote here about six days ago with a script how to do so...

[dunbarx]

Klaus.

Yes, that's what I wrote here about six days ago with a script how to do so...

Calm down, mon ami.

I read your post, and understand that there is a big difference between saving a copy of a stack and saving a copy of a stack file.

The dictionary is correct when it says:

Code: Select all

"save stack [as filePath] [with {format stackFormat | newest format}]

What I was on about was with the dictionary example

Code: Select all

save this stack as "Backup"

If I make a new stack, save it with the name "XXX", then execute that line of code, nothing happens. Neither within LC nor anywhere else on my machine. So forget everything I wrote, and simply tell me what happens, anywhere, when I run that line of code.

Craig

[Klaus]

I'm the calm in person!

What I was on about was with the dictionary example
CODE: SELECT ALL
save this stack as "Backup"
If I make a new stack, save it with the name "XXX", then execute that line of code, nothing happens. Neither within LC nor anywhere else on my machine. So forget everything I wrote, and simply tell me what happens, anywhere, when I run that line of code.

As I also told you calmly before, if you don't supply a path for the stack, on a Mac you may find it in THE DEFAULTFOLDER.
I made a test, created a stack name "test1" and it was the way I had described on the previous page here:

Code: Select all

on mouseUp 
   save this stack as "test2"
end mouseUp

I did not supply a full path, so I ended with the saved stack inside of the APP package*** and without a suffix, see screenshot.
*** Which is the defaultfolder right after LC starts up.

P.S.
save this stack as "new name..."
will ONLY change the filename of the stack, not the (internal) name of the stack and will not add the suffix .livecode