I had to do this as well. In the end it was a group that had two fields in it. I assumed it was a field property that I either could not find or could not change and submitted a bug report. Since my problem was present in 6.7. or 7, nothing was investigated.
e On Jan 30, 2015, at 7:27 AM, Geoff Canyon <gcan...@gmail.com> wrote: > So far I've determined that stripping out every line of code from the stack > doesn't fix the problem. > > Deleting every control does. > > Now I'm going through to figure out which control is poisonous to 6.5.2 > > On Fri, Jan 30, 2015 at 3:40 AM, Geoff Canyon <gcan...@gmail.com> wrote: > >> I have a stack that I moved to 7.0.2 for a few days without thinking, and >> I want to move it back. I tried this in the message box: >> >> >> set the stackfileversion to 5.5;lock messages;save stack >> "versionProblem";close stack "versionProblem" >> >> >> and after that if I open it in 6.5.2 or 6.7, they lock up with the >> spinning beach ball of death. I don't think I put anything into the stack >> that requires 7, and LC dies even if I lock messages before opening the >> stack. >> >> >> Any ideas? >> >> >> gc >> > _______________________________________________ > 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
