Debugging LiveCode Builder scripts (widgets)

[Ralph DiMola]

Ben,

You could try to dispatch messages to LCS. They may be buffered also, it's
worth a shot.

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at evergreeninfo.net

-----Original Message-----
From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf
Of Ben Rubinstein via use-livecode
Sent: Thursday, March 30, 2023 12:33 PM
To: Use LiveCode
Cc: Ben Rubinstein
Subject: Debugging LiveCode Builder scripts (widgets)

I'm trying to track down an obscure crashing bug in a widget.

With thanks to Mikey for
https://github.com/macMikey/LCB-missing-manual/wiki/debugging, I've mostly
been able to get by using 'log' as my primary debugging method, for all my
simple scripting errors.

However in this case the problem is that under certain circumstances
LiveCode/the widget hangs when new data is set. In this case (I'm reasonably
certain) the log messages that are issued are never reported. The standard
things seems to be that messages sent by 'log' are buffered, and reported
when idle.

Are there any tips for putting out debugging info from a widget that can
either be displayed/reported _immediately_ in LiveCode, or to some other app
so that I can get them up to the point that it hangs?

TIA, Ben

_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode