It usually works for me to click the Messages button in the toolbar (to turn off messages) before opening the stack. That prevents a crash if the problem is script related. You can still use the editor and other IDE stacks, and you may also be able to turn messages back on after the stack has opened.
On May 23, 2015 10:32:48 AM CDT, Mike Kerner <mikeker...@roadrunner.com> wrote: >For me the next time I have to be able to do this... > >I had a stack that was causing LC to hard-crash at startup. THAT is >really >inconvenient when you're trying to recover your stack and when you're >trying to fix it, since you can't actually get the stack to the script >editor, so > >1) Create another stack >2) put a button in that stack >3) script of the button: > >*on* mouseUp > *answer* file "Please select a stack" with *type* "LiveCode >Stacks|rev|RSTK" > *if* it is empty *then* *exit* mouseUp > *edit* the script of stack it >*end* mouseUp > >DON'T FORGET, YOU HAVE TO SAVE THE STACK WHILE YOU'RE STILL IN THE >SCRIPT >EDITOR (COMMAND/CTRL-S) -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.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
