Mark Schonewille wrote:
> Richard,
>
> Since you are a professional LiveCode programmer, just like me,
> I know that you know that one may see an error code of the form
> ###,###,###,xxxx once in a while, where # is a number and x is
> a letter. Seeing this error isn't necessarily a LiveCode bug.
> I have no idea why you assume it is.
True, the format you describe is what the engine outputs when errors are
encountered, sent as the argument to the errorDialog message.
But the IDE's revBackScript includes an errorDialog handler which
translates that into a conveniently readable form, also made available
for inclusion in standalones in the Standalone Builder.
Given that RunRev provides this lookup automatically, no one should ever
see the raw error data in either the IDE or a standalone.
If they do it means the errorDialog handler either wasn't triggered
properly, or is somehow failing itself.
So my interest is in identifying a recipe in which an errorDialog
message is sent but the info is being displayed in raw form rather than
the more readable format LiveCode normally provides.
> For further questions and comments on this product, you are welcome
> to contact me off-list.
My question here was about the perception that LiveCode isn't reporting
errors correctly. If I have questions about your product I'll write you
off-list.
--
Richard Gaskin
Fourth World
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode developers: http://www.LiveCodeJournal.com
LiveCode Journal blog: http://LiveCodejournal.com/blog.irv
_______________________________________________
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
