stackfileversion and locking 6.5.2

[Mike Bonner]

Even setting the filename to empty might be enough. (this way, any
references in the stack that use the stackname won't be broken).  When this
is done, when you save it, rather than just saving it brings up the
filename dialog as if it were a new stack, and if you try to save it in the
same place with the same name, you receive the usual warning about
overwriting the stack.

On Fri, Jan 30, 2015 at 9:36 AM, tbodine <bodine at bodinetraininggames.com>
wrote:

> Is it feasible to make a handler for stacks being opened that would detect
> old version stacks and open them copies of them as "untitled" in the new
> stack format while leaving the legacy stack as is?
> -- Tom Bodine
>
>
>
> --
> View this message in context:
> http://runtime-revolution.278305.n4.nabble.com/stackfileversion-and-locking-6-5-2-tp4688290p4688300.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>