What does "stack was produced by a newer version" mean?

[Graham Samuel]

Answering my own question (to some extent), I now see that I did create the issue myself, by somehow messing up the "copy files" list in my standalone settings, so that the reference to the original template stack didn't work. In fact I tried to copy a non-existent file, and then rename it. Interestingly this did in fact produce a file - a useless one, but still a file.

Although I am entirely to blame for the error, it's interesting that using the 'put URL' form to do the copy, it is not obvious how to detect errors: in the old-fashioned way of handling files, one can hope to see an error in 'the result'. The current LC documentation doesn't suggest **any** way of detecting errors in URL-type file operations, but I guess there must be one or more.

My comment about conflicting error messages when I tried to open an inappropriate file still stands though: my guess now is that the "stack corrupted" is closest to correct, since the created file probably wasn't a stack file at all, apart from the extension.

Sorry for the waste of bandwidth.

Graham


On 18 Nov 2013, at 17:48, Graham Samuel wrote:

> I have a desktop app I've been developing on a Mac running Lion 10.7.5. I have just switched my LiveCode version to 6.1.3.
> 
> Part of my app copies a template stack into an area where it can be manipulated and saved (in fact it's in a folder in the 'Applications Support' area of the Mac library). The copy is just a statement:
> 
>   put URL ("binfile:" & tTemplatePath) into URL ("binfile:" & gdataStackPath) 
> 
> After this is executed, the Mac finder shows the file in place with the expected '.livecode' extension.
> 
> Then at some later point in the app's script, I execute:
> 
>   go stack gdataStackPath
> 
> This has been working for ages. I now have a problem that I may have created myself, but so far I can't find out what I've done wrong: the 'go' command fails to execute, and after investigation I see that 'the result' returns "stack was produced by a newer version", and if I try to open this copied stack directly in LC, by right-click and 'Open with...", I get "unable to open stack: stack is corrupted, check for ~ backup file". Which of these error messages is the right one, and if the first one, what does it mean? I can't see that my innocent 'put URL' can have corrupted the stack, which is not opened until my 'go' command, and therefore not subject to being corrupted.
> 
> Can anyone suggest what's wrong? I will continue to look for reasons of course,  but right now I'm stumped.
> 
> Graham
> _______________________________________________
> 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