That's correct - the stackfileversion is by default the most recent the engine understands.
Saving stackfiles in a legacy version is an IDE semantic in the IDE save routines - it stores a custom property on the stack. On the other hand it is the engine which identifies whether a stackfiles is too new to be opened. Since 2.7 all stackfiles start with 8 bytes - REVOxyzw - where xyzw are the digits for the version the format was introduced in: REVO2700 - 2.7 REVO5500 - 5.5 REVO7000 - 7.0 REVO8000 - 8.0 Warmest regards, Mark. Sent from my iPhone > On 5 Feb 2016, at 23:13, Peter Haworth <p...@lcsql.com> wrote: > > If I'm reading the documentation correctly, saving a stack file without > specifying the "with format" clause results in it being saved in the format > specified in the stackFileVersion. > > If I open a stack file created with 6.x or 7.x in 8.0 and save it without > changing the stackFileVersion and without specifying the format in the > "with" clause, it becomes unreadable by 6.x or 7.x, even if it uses none of > the 8.0 features. > > I'd be happy to use the" with format" clause but is there a property of a > stack that contains its stackFileVersion? The IDE obviously knows what it > is since it puts out a nice error message if you try to open a stack file > created with a later LC version. > > Would be nice if there was a "with current format" or something similar > that would save the stack with the format it already has. > _______________________________________________ > 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
