Page 1 of 1
LiveCode file edit issue
Posted: Tue Jul 19, 2016 5:06 pm
by Armenhui
Hi all,
I can not edit my stack, can not write code on my stack. Anyone knows why it can be happen? And what I can do?
Re: LiveCode file edit issue
Posted: Tue Jul 19, 2016 5:27 pm
by LiveCode_Panos
Hi Armenhui,
I would suggest deleting your Prefs. On OS X they are located in /Users/your_user_name/Library/Preferences/RunRev/ folder.
You should see one or two files there:
livecode.rev --> Prefs for LiveCode versions < 7
livecode7.rev --> Prefs for LiveCode 7 and 8
1. Quit LC
2. Remove those 2 files from this folder. Those files will be re-generated once you start LiveCode again.
3. Start LC
4. Try to edit your stack now
Re: LiveCode file edit issue
Posted: Tue Jul 19, 2016 5:28 pm
by Klaus
Hi Armenuhi,
did someone, not you, eventually check "cantmodify" in the inspector for that stack?
Or is it "protected" on a system level?
e.g. I can check "Protected" on my Mac for a file in the INFO for that file.
best
Klaus
Re: LiveCode file edit issue
Posted: Tue Jul 19, 2016 5:43 pm
by Armenhui
Thanks, I try two options which you said but the result was same, I can not edit the stack.

Re: LiveCode file edit issue
Posted: Tue Jul 19, 2016 7:03 pm
by FourthWorld
Perhaps the style property of the stack has been changed from topLevel to modeless?
Re: LiveCode file edit issue
Posted: Wed Jul 20, 2016 5:43 pm
by jacque
I've seen something similar when LC gets stuck in an infinite loop in one of its IDE handlers. There may be something in your script that causes that. If none of the other suggestions work, try launching LC and clicking the Messages icon in the toolbar, which turns off your scripts. Then use the File menu to open the stack.
If the stack is editable now, something in your script is causing the IDE to think it's in debug mode when it isn't.
Another thing to try is to hold down cmd-period (ctrl-period on Windows) when the stack stops working. If that clears the problem there may be a bug in the IDE. I've only seen this twice and I don't have a recipe for it yet, but if it's reproducible for you the team would probably want to see your stack.