True, but what would anyone go out of their way to write an error
handler that provides less useful information than what LC provides if
left alone?
And some of the error info I see shared in the forums is from newer
users, who seem unlikely to have ventured into the relatively arcane
world of custom error processing.
I hope I simply misunderstand what I've been seeing, that perhaps there
isn't something broken in recent versions of the IDE's error handling.
In Dan's message from yesterday he wrote:
1. Why didn't the debugger throw an error? Instead, it put this error
chunk in the message box?
@Dan: Do you have a custom errorDialog handler in your message path?
--
Richard Gaskin
Fourth World Systems
J. Landman Gay wrote:
If there's an errorDialog handler, errors bypass the IDE. That's one way it
could happen.
--
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On October 17, 2020 4:06:03 PM Richard Gaskin via use-livecode
<use-livecode at lists.runrev.com> wrote:
J. Landman Gay wrote:
On 10/17/20 12:13 PM, Dan Friedman via use-livecode wrote:
Where did Jacque get that list of codes?
From a plugin Richard and I wrote some years ago. It dynamically loads the
error list based on
the version of LC you're using. You can look up individual codes, or paste
in a list of errors
which is what I did with your report.
Tools like that can be useful at runtime to help fill out logs and such.
But I've been seeing a surprising number of conversations here and in
the forums suggesting that people are seeing raw error info in the IDE.
If that's true, what broke with the IDE's more guided error handling?
--
Richard Gaskin
_______________________________________________
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
