stack version | |
Type | glossary |
Dictionary | LCS |
Library | LiveCode Script |
Synonyms | stack format,stack file format,stack file version |
Related | Property: blendLevel, ink, textFont, textStyle, textSize, unicodeToolTip, antialiased, opaque, minStackFileVersion Command: save Function: version Glossary: stack file, stack, Unicode, field, button, script, custom property, card, command Object: widget |
Description | When saving a binary stack using the save command, it is possible to save with a specific version of LiveCode's stack file format. This is useful when saving a binary stack so that it can be saved in an older version of LiveCode, but it should be used with caution. Warning: Using a non-default stack version could result in data being lost when stacks are saved. In particular, any features that are not present in the target version may be lost. For example, using a stack version of "2.4" will cause any blendLevel or ink properties to be lost. These are the stack file format versions that can be used with the save command, and the versions of LiveCode that they are compatible with:
When saving in the 8.0 format paragraphs will be truncated where length exceeds 32767 characters. When saving in the 7.0 format, all widgets will be lost. When saving in the 5.5 format, all Unicode text will be lost unless it is stored in a container that has a Unicode variant. For example, this means that Unicode text in fields and button labels will be saved, but any Unicode text in scripts or custom properties will be lost. When saving in the 2.7 format, the following properties or property aspects will also be lost:
When saving in the 2.4 format, the following properties will also be lost or altered:
|