Cleansing of corrupted stack

Want to talk about something that isn't covered by another category?

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
mvillion
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 107
Joined: Sun Feb 24, 2013 12:29 pm

Cleansing of corrupted stack

Post by mvillion » Sun Nov 02, 2014 1:13 am

HI

I have been working on a stack in version 6.7 and suddenly it got corrupted. I cannot explain it or how.
I have managed to open it in version 7 but it will not open in 6.7

Is there a clean up mechanism that can be performed to strip it down and rebuild it as I no longer trust the base stack.
Something like an XML export and reimport to rebuild the binary or some other trick.

Would saving it as an earlier version (5.5 format) work?

This is not the first time I have had a stack go bad on me and there is no warning. I save regularly but unless I am closing down and reopening the stack there is no indication it has gone corrupt.

I am thinking I am going to need to set a timer for 30 minutes and save and reopen just to protect myself.

On another matter. The other day a script stopped working. It was reporting something was wrong but the text was correct. What it turned out to be was a hidden character got typed. I guess I must have mistyped it. I was surprised that there is no validation scripts to look for this to ensure that only standard characters are within the script window.

Where I am at is I think I am going to have to create a new stack and cut paste items in and HOPE that there is some kind of validation mechanism to ensure that I have a stable stack again.

Regards
Matt

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10045
Joined: Sat Apr 08, 2006 7:05 am
Contact:

Re: Cleansing of corrupted stack

Post by FourthWorld » Sun Nov 02, 2014 1:24 am

Version 7 uses a different file format. Just use Save As from within 7 to save it to am older format and you should be fine.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn

dunbarx
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10317
Joined: Wed May 06, 2009 2:28 pm

Re: Cleansing of corrupted stack

Post by dunbarx » Sun Nov 02, 2014 3:29 am

Text validation is entirely up to you. This is extra work, but a good thing. There is no single "right" set of characters for every user. You can always do this once, and save the gadget that works for you in future projects.

Craig Newman

[-hh]
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 2262
Joined: Thu Feb 28, 2013 11:52 pm

Re: Cleansing of corrupted stack

Post by [-hh] » Sun Nov 02, 2014 10:27 am

What's interesting with "saving in older format" is that one can make this choice permanent (saved with stack) in <LC Preferences / Files & Memory>. This avoids a 'stack corruption' (but also new features) when working with LC 7 on a pre-LC7-stack.
prefsON.jpg
Available (at least) in LC 6.6.5 and later
prefsON.jpg (33.13 KiB) Viewed 6737 times
shiftLock happens

death386386
Posts: 1
Joined: Mon Nov 03, 2014 4:27 pm
Contact:

Re: Cleansing of corrupted stack

Post by death386386 » Mon Nov 03, 2014 8:05 pm

FourthWorld wrote:Version 7 uses a different file format. Just use Save As from within 7 to save it to am older format and you should be fine.

same issue here thanks for info

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10045
Joined: Sat Apr 08, 2006 7:05 am
Contact:

Re: Cleansing of corrupted stack

Post by FourthWorld » Mon Nov 03, 2014 9:27 pm

death386386 wrote:
FourthWorld wrote:Version 7 uses a different file format. Just use Save As from within 7 to save it to am older format and you should be fine.

same issue here thanks for info
Going forward they've made this even easier: While it's not possible for an older version of nearly any app to be able to understand formats created after it was written, there are some elements in the LC file format that make it possible for an older engine to at least guess that the file may have been made with a newer version, and to suggest trying that when opening a newer file in an older version.

Accordingly, this enhanement was introduced in v7.0, and has been backported to v6.7.1 which is now in testing as "RC1".
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn

Post Reply