Richard:
> It's what software testers call a test. ;)
> It isolates the issue to the fewest lines of code
> needed to demonstrate the issue.
And it was a very good test! I loved it. Forewarned is forearmed, and LC
has had quite a few traps to avoid. Glad this one is fixed in latest
version.
The recipe I gave is well-tested and does work with your code, assuming
it holds true on all platforms and machines; you simply have to click as
fast as you can, constantly, while holding the Enter/Return key
constantly until you get lucky. Then the Inspector or Message box opens
free to type or click, if your luck holds, which is 3 out of 4 times for
me. Kind of a fun exercise. I've used this trick or a similar one before
to gain control in one or two real situations.
Turning Debug Mode off while not actively using it (so, using it
consciously, only when actually needed, after experiencing a bug that
you can't solve without examining variables) has been one of the easiest
ways to improve IDE stability on both Windows and Mac over the years. I
think Debug has improved quite a bit, but I would recommend it just in
case to anyone who is having trouble. When that's rock-solid, it'll be
another thing to celebrate! :)
Best wishes,
Curry Kenworthy
Custom Software Development
LiveCode Training and Consulting
http://livecodeconsulting.com/
---
This email has been checked for viruses by AVG.
http://www.avg.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
