save | |||||||||||||
Type | command | ||||||||||||
Dictionary | LCS | ||||||||||||
Library | LiveCode Script | ||||||||||||
Syntax |
| ||||||||||||
Summary | Saves a stack file on the user's system. | ||||||||||||
Introduced | 1.0 | ||||||||||||
OS | mac, windows, linux, ios, android, web | ||||||||||||
Platforms | desktop, mobile | ||||||||||||
Parameters |
| ||||||||||||
Example |
| ||||||||||||
Values |
| ||||||||||||
Related | Property: substacks, defaultFolder, stackFileVersion, minStackFileVersion Control Structure: function Keyword: as, file Object: stack Glossary: substack, stack file, command, standalone application, main stack, stack version Command: create stack Function: stacks | ||||||||||||
Security | disk | ||||||||||||
Description | Use the save command to save changes to a stack or to save a copy of a stack into another file. The save command saves all stacks stored in the same file as the specified stack. That is, if you save a main stack, all substacks of that stack are also saved in the same file, and if you save a substack, its main stack and any other substacks are also saved. If the stack has not yet been saved and doesn't have a filename, you
must use the You cannot save to a standalone application's file; standalones are read-only. The save command can save the stack in several different versions of the LiveCode stack file format.
Warning: If you save in an older stack version that doesn't
support all of the features used in the stack, then some of contents of
the stack may be lost. In general, you are recommended to use the
| ||||||||||||
Tags | file system |