Ineffective lazy screenRect

Bob Sneidar bobsneidar at
Fri Mar 15 10:53:58 EDT 2019

Ya know, I remember a good while back, several years, that in the process of debugging I would get into these unstable states. It was something in my code that was throwing an error, but the debugger instead of catching it and stopping at the line, basically looked like it completed. But it didn't. It was like a script was still running but I was able to interact with the UI to some extent. 

Bob S

> On Mar 14, 2019, at 12:31 , J. Landman Gay via use-livecode <use-livecode at> wrote:
> It sort of fits with what I've seen in all versions of LC 9. Things start failing inexplicably -- handlers available moments ago suddenly can't be found, keyboard shortcuts stop working, the message path gets skewed or lost, etc. A restart of LC fixes things until it happens again. In many cases, if I don't restart, I'll eventually crash.
> No recipe, no logic to it. But I think it has something to do with debugging, since I most often see things go wrong after or during a debugging session.

More information about the use-livecode mailing list