<doc>
	<legacy_id>3502</legacy_id>
	<name>stackFileVersion</name>
	<type>property</type>

	<syntax>
		<example>set the stackFileVersion to <i>version</i></example>
		<example>the stackFileVersion</example>
	</syntax>

	<synonyms>
	</synonyms>

	<summary>Reports the version of the stack file format to use.</summary>

	<examples>
<example><p>command legacySave pStack</p><p>  local
tOldStackFileVersion</p><p>  put the stackFileVersion into
tOldStackFileVersion</p><p>  set the stackFileVersion to 2.4</p><p>  save
stack pStack</p><p>  set the stackFileVersion to
OldStackFileVersion</p><p>end legacySave</p></example>
	</examples>

	<history>
		<introduced version="2.7">Added.</introduced>
		<deprecated version=""></deprecated>
		<removed version=""></removed>
		<changed version="5.5.0">Added version 5.5</changed>
		<experimental version=""></experimental>
		<nonexperimental version=""></nonexperimental>
	</history>

	<objects>
		<global/>
	</objects>

	<platforms>
		<mac/>
		<windows/>
		<linux/>
		<ios/>
		<android/>
	</platforms>

	<classes>
		<desktop/>
		<server/>
		<web/>
		<mobile/>
	</classes>

	<security>
	</security>


	<classification>
	</classification>

	<references>
		<command tag="save">save command</command>
	</references>

	<description>
	<overview>Use the <b>stackFileVersion</b> to obtain or change which version
of the stack file format LiveCode will use when saving stacks.</overview>

		<parameters>
		</parameters>

	<value>The <b>stackFileVersion</b> currently has two possible values:<p>  -
"2.4" - This stack file version is used by LiveCode 2.6.1 and
arlier</p><p>  - "2.7" - This stack file version is used by versions of
LiveCode after 2.6.1 and before 5.5.0.</p><p>  - "5.5" - This stack file
version is used by versions of LiveCode after 5.5.0 and before
.0.</p><p>  - "7.0" - This stack file version is used by versions of
LiveCode 7.0. and after.</p></value>
	<comments>The <b>stackFileVersion</b> is useful when stacks need to be
saved in legacy formats for backwards compatibility but it should be used
with caution.<p></p><p>Setting the <b>stackFileVersion</b> to something less
than the current version could result in data being lost when stacks are
saved, in particular any features that are not present in the target
version. For example setting the <b>stackFileVersion</b> to 2.4 will cause
any blendLevel or ink properties to be lost.</p><p></p><p>Remember to set
the <b>stackFileVersion</b> back to its previous value after changing it,
otherwise LiveCode may save your stacks in unexpected
formats.</p><p></p><p>There is no need to use the <b>stackFileVersion</b> to
save a stack compatible with version 2.6.1 and earlier in the IDE. Instead,
open the stack in the current version of LiveCode and select "Save As" from
the "File" menu, then choose "Legacy LiveCode Stack" from the drop down box
for the file type. If you do not wish to do this every time, there is a
setting in the "Files  Memory" section of the preferences that causes
LiveCode to preserve the stack file version of legacy
stacks.</p><p></p><p>The following properties are not supported in the 2.4
stack file format and will be lost or altered when saving in 2.4
format:</p><p></p><p>antialiased property - lost</p><p>ink property - lost
for cards, reverted to GXcopy for controls if not supported</p><p>opaque
property - lost for cards</p><p>blendLevel property - lost</p><p></p><p>The
following properties are not supported in the 2.7 stack file format and will
be lost or altered when saving in 2.7 format:</p><p></p><p>textFont
property - separation lost</p><p>textStyle property - separation
lost</p><p>textSize property - separation lost</p><p>textFont property -
separation lost</p><p>unicodeToolTip property - lost</p><p>all paragraph
level properties - lost</p><p>separation of Unicode attribute of chars -
lost</p><p>character level metadata property - lost</p><p></p><p>The
following properties are not supported in the 2.7 stack file format and will
be lost or altered when saving in 2.7 format:</p><p></p><p>textFont
property - separation lost</p><p>textStyle property - separation
lost</p><p>textSize property - separation lost</p><p>textFont property -
separation lost</p><p>unicodeToolTip property - lost</p><p>all paragraph
level properties - lost</p><p>separation of Unicode attribute of chars -
lost</p><p>character level metadata property - lost</p><p></p><p>When saving
in the 5.5 format all Unicode text that does not have a Unicode variant in
5.5 will be lost, so field text and button labels etc will be saved but any
Unicode text in scripts or custom properties will be lost.</p></comments>
	</description>
</doc>
