Re: stackfileversion and locking 6.5.2
Probably unrelated, but I have noticed that text that has been produced in a PDF via their OCR tool will have hidden characters in it that will prevent me from inserting or updating records in my SQL database with that data. The SQL generates an error as though there were nothing beyond the first hidden character in the SQL statement. I just run my text through a cleaner function now to get around it, but if you are in the habit of drag/dropping text in your LC apps, it isn’t a bad idea to run all that through your own text cleaning function beforehand. I do this in the closeField handler, and have my dragDrop handler call closeField when done. That way, whether or not you copy/pasted, or dragDropped, the text will be cleaned. Bob S On Jan 30, 2015, at 14:05 , Geoff Canyon gcan...@gmail.commailto:gcan...@gmail.com wrote: well that didn't take long :-P It turns out that there is one field in the stack -- delete the contents of that field, and the stack opens fine in 6.5.2. I copied the contents of the field and pasted into Pages, then deleted the contents of the field, and the file opened fine in 6.5.2. I then pasted the contents back in, and the stack survived. Bug 14476 http://quality.runrev.com/show_bug.cgi?id=14476 ___ 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
Re: stackfileversion and locking 6.5.2
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
Re: stackfileversion and locking 6.5.2
Even setting the filename to empty might be enough. (this way, any references in the stack that use the stackname won't be broken). When this is done, when you save it, rather than just saving it brings up the filename dialog as if it were a new stack, and if you try to save it in the same place with the same name, you receive the usual warning about overwriting the stack. On Fri, Jan 30, 2015 at 9:36 AM, tbodine bod...@bodinetraininggames.com wrote: Is it feasible to make a handler for stacks being opened that would detect old version stacks and open them copies of them as untitled in the new stack format while leaving the legacy stack as is? -- Tom Bodine -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/stackfileversion-and-locking-6-5-2-tp4688290p4688300.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ 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
Re: stackfileversion and locking 6.5.2
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
Re: stackfileversion and locking 6.5.2
Is it feasible to make a handler for stacks being opened that would detect old version stacks and open them copies of them as untitled in the new stack format while leaving the legacy stack as is? -- Tom Bodine -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/stackfileversion-and-locking-6-5-2-tp4688290p4688300.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ 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
Re: stackfileversion and locking 6.5.2
well that didn't take long :-P It turns out that there is one field in the stack -- delete the contents of that field, and the stack opens fine in 6.5.2. I copied the contents of the field and pasted into Pages, then deleted the contents of the field, and the file opened fine in 6.5.2. I then pasted the contents back in, and the stack survived. Bug 14476 http://quality.runrev.com/show_bug.cgi?id=14476 On Fri, Jan 30, 2015 at 11:00 AM, Mike Bonner bonnm...@gmail.com wrote: Even setting the filename to empty might be enough. (this way, any references in the stack that use the stackname won't be broken). When this is done, when you save it, rather than just saving it brings up the filename dialog as if it were a new stack, and if you try to save it in the same place with the same name, you receive the usual warning about overwriting the stack. On Fri, Jan 30, 2015 at 9:36 AM, tbodine bod...@bodinetraininggames.com wrote: Is it feasible to make a handler for stacks being opened that would detect old version stacks and open them copies of them as untitled in the new stack format while leaving the legacy stack as is? -- Tom Bodine -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/stackfileversion-and-locking-6-5-2-tp4688290p4688300.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ 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
