Line Hint

Calvin Waterbury cjw at
Sat Jan 15 21:49:29 EST 2011

Hi Jim,

I did this somewhat, but the idea of matching errors with error messages is certainly wise.  

Thank you,
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Jim Ault <jimaultwins at>
Sender: use-livecode-bounces at
Date: Sat, 15 Jan 2011 18:38:19 
To: How to use LiveCode<use-livecode at>
Reply-To: How to use LiveCode <use-livecode at>
Subject: Re: Line Hint

Try creating know errors, then observe the error reporting.
Start with small scripts, misspell, mis-reference, etc to get a feel  
for this.

On Jan 15, 2011, at 5:17 PM, Calvin Waterbury wrote:

> We have a winner!
> Boy! do I feel like a schmolez!
> Thanks for the clarification, Jeff.
> Calvin
>> 	Jeffrey Massung <mailto:massung at>
>> Saturday, January 15, 2011 7:12 PM
>> Well, "line hint" isn't really accurate, because aren't they two  
>> separate items? So "line" would be the line # the error occurred on  
>> and "hint" would be something like "Field 'hoohaw' doesn't exist,"  
>> right?
>> I haven't done hardly anything with error decoding in LC, but that  
>> would make sense to me.
>> Jeff M.
>> 	Calvin Waterbury <mailto:cjw at>
>> Saturday, January 15, 2011 6:41 PM
>> Hi David C.,
>> Nope.  I'm referring to the "Errors" window when something flubs.   
>> It says on the left side of that dialog...
>> Type
>> Object
>> Line
>> Hint
>> I know this is an error message, but does "line hint" mean anything  
>> else?

Jim Ault
Las Vegas

use-livecode mailing list
use-livecode at
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list