compatability of rev stacks and livecode stacks in a standalone?

[Lars Brehmer]

I have an app which is a splash screen that contains all of the real program stacks compressed as custom properties. When the standalone is launched the first time, it creates a folder, open decompressed those stacks and saves them into that folder. From that point on, launching the standalone opens those stacks and the app runs. Pretty standard stuff I assume.

>From this point on when the app is launched it looks for an update on my website before the main stack is launched. If there is an update, it is a stack that contains the new main stack again as a compressed custom property, opens it decompressed and saves it into that folder, replacing the older stack. So far so good. It has always worked.

The original app was done in runRev 2.8.

I have since upgraded to liveCode 5.2 and redone the app completely- splash screen, compressed stacks etc. 

But the updater doesn't work anymore and I think is because of the older runRev 2.8 stacks. In the rev 2.8 IDE it doesn't work. The update script errors out the moment a newer liveCode stack is referred to. This updater stack is a rev 2.8 stack, containing custom properties that are compressed liveCode stacks.

If I open a copy of the rev 2.8 splash screen stack in liveCode, the update stack works perfectly. LiveCode recognizes and opens the rev 2.8 update stack, opens it and performs the update with the newer compressed liveCode stacks.

But it doesn't work in the standalone. The updater stack crashes, presumably at the point where it should decompress and open the custom property stacks. Does this mean that the rev 2.8 standalone engine also doesn't recognize liveCode stacks? That seems logical to me, but if this is the case, is there any way around it?

This is way beyond my runRev & liveCode abilities and help would be greatly appreciated!

Cheers,

Lars