So when you selected “Save As…” did you choose “Legacy LiveCode Stack (5.5)” from the Format pulldown at the bottom of the dialog?
I just created a basic stack in 7.0.1, saved it in 5.5 format, and it opened correctly in both 5.5 and 6.7, so I have to imagine 6.5.2 should be fine. You should try the same with a test stack and see if you get the same results. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On Jan 9, 2015, at 1:47 PM, Ray <r...@linkit.com> wrote: > Scott - thanks again. I just tried that and unfortunately it doesn't work. > > I forgot to mention that I've also tried 'exit to top' on the first card's > preOpenStack handler. I believe this would also stop any scripts from > running. Nonetheless, even choosing Open Stack... from Livecode 6.5.2's File > menu produces the same error displaying "There was a problem opening that > stack: file is not a stack" and does not open the stack file in any way. > > On 1/9/2015 5:20 PM, Scott Rossi wrote: >> I believe what Mike was suggesting was to turn on lock messages, then use >> “Open Stack…" in the File menu to launch the stack. This should prevent any >> startup scripts from firing, and you should then be able to choose "Save >> As…" and resave the stack. >> >> I haven’t done this with 7.0.1 but have done this often with 6.x and >> previous stacks. >> >> Regards, >> >> Scott Rossi >> Creative Director >> Tactile Media, UX/UI Design >> >> On Jan 9, 2015, at 12:08 PM, Ray <r...@linkit.com> wrote: >> >>> Mike - thanks for the idea but even a script like this fails >>> on mouseUp >>> lock messages >>> go stack [legacyStackPath] >>> end mouseUp >>> >>> The result is the file I chose is not a stack file. >>> >>> So currently I can't open a stack which is a nearly two years of work in an >>> older version of Livecode. Meanwhile, 7.0.1 is so full of bugs (even >>> playing a sound after 'waiting till sound is done' crashes) I can barely >>> use the stack. I failed to maintain piles of old versions of my project >>> trusting Livecode's claim that a release is stable and relying on the >>> legacy saving ability. Both of these have failed leaving me pleading for >>> suggestions. >>> >>> Anybody? >>> >>> -------- Original message -------- >>> From: Mike Bonner <bonnm...@gmail.com> >>> Date:01/09/2015 12:38 PM (GMT-04:00) >>> To: How to use LiveCode <use-livecode@lists.runrev.com> >>> Cc: >>> Subject: Re: Can't Move Backward >>> >>> You might turn off messages before opening the stack to see if it loads. >>> Also, if you're double clicking to open the stack, try using the file menu >>> instead. >>> >>> On Fri, Jan 9, 2015 at 7:19 AM, Ray <r...@linkit.com> wrote: >>> >>>> I'm trying a "Save As" on a stack file last saved in 7.0.1 so I can open >>>> it in 6.5.2, the last stable version of Livecode that I know of. >>>> >>>> The choices are: >>>> Legacy Livecode Stack (5.5) >>>> Legacy Livecode Stack (2.7) >>>> Legacy Livecode Stack (2.4) >>>> >>>> I would imagine my copy of Livecode 6.5.2 would open a stack file saved as >>>> Legacy 5.5, but it doesn't. I can't remember back as far as 2.7 and 2.4. >>>> >>>> I am able to create a new, empty stack file in 7.0.1, save it in legacy >>>> 5.5 and then open it in 6.5.2 so there's apparently something going on with >>>> the first stack file. However, Livecode should open it and produce script >>>> errors which I can then find and fix. If Livecode 6.5.2 doesn't even open >>>> it then I'm stuck. >>>> >>>> Does anybody know how to move backward away from the many problems 7.0.1 >>>> has without having to re-write years of work? >>>> >>>> _______________________________________________ >>>> 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 >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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
