LiveCode Forums

I am using latest 9.0.2 Community edition of LC on Mac. I had some kind of crash, and now the text is running off the bottom of the script editor and much of the text is not accessible.

In addition the Variables and other info at the bottom are not visible either.

I have tried deleting the obvious preferences files and reinstalled LC, but still same problem.

Any ideas?

Please see image of the bottom of the script editor:

https://drive.google.com/file/d/1StJ9va ... sp=sharing

Gee, couldn't you put a bit more of the picture than that?

I have installed 9.0.1, but same problem, so some preference file somewhere...

Sorry Bogs. Here is another shot. You can see the text cursor at the bottom. I can push it down with the arrow key, but I don't see any more text and you can see there is no scrollbar showing

https://drive.google.com/open?id=1SuOPR ... logies.com

Here is a screen recording of the bottom of script being inaccessible.

https://drive.google.com/file/d/1SymB8W ... sp=sharing

Hi Kaveh,

did you delete the preference files from folder

/Users/userName/Library/Preferences/RunRev
?
The files "livecode7.rev" and "livecode.rev" ?

When you delete those files (assuming both are there. "livecode7.rev" is for LC 7 and up) Livecode should not be running because otherwise it will recreate the faulty file on close.

I would try that again.
Kind regards
Bernd

Thank you so much Bernd. Worked.

I had deleted but must have been while LC was running...

Kaveh

Evening All

I have had a similar problem.

My script editor view no longer shows the variables pane at the bottom. I have uninstalled and reinstalled Livecode indy 9.05 on Mac and it still isn't showing.


Am I unaware of a setting?


Many Thanks

Hi.

This does sometimes go away. Do a "Find and replace..." from the "Edit" menu, and all the nice bottom stuff should reappear.

Craig

Try deleting your LC preferences.

Deleting the LC preferences was the solution.

Thank you very much.

Deleting prefs is a good way to restore the tool to a usable state, but does not address the underlying problem.

I hope anyone who has a recipe for this will please consider submitting a bug report so no one has to deal with it in the future.