errorDialog message

[J. Landman Gay]

On 11/3/04 3:39 PM, Chris Sheffield wrote:

> I'm wondering if anyone here has ever used errorDialog to trap and log
> errors within a standalone.  I'm trying to do this in order to figure out
> why a certain customer is having certain problems with my application.  This
> is working and I'm able to log the error details to a file, but the error
> details are somewhat cryptic.  The docs seem to indicate that these details
> will be similar to what is seen in the error dialog in the Rev IDE, but this
> is not the case.
> 
> This is the content of one of my log files containing information for three
> different errors:
> 
> 10/27/04 9:31:10 AM
> 87,1308,18
> 77,1308,18
> 449,1308,3,false
> 535,1308,1,false
> 241,1308,1,UpdateChecks
> 353,0,0,stack "/Applications/Read Naturally SE
> 2/rnse.app/Contents/MacOS/rnstories.rev"
> 573,17,1,UpdateChecks
> 241,17,1,preOpenCard
> 353,0,0,card id 1820 of stack "/Applications/Read Naturally SE
> 2/rnse.app/Contents/MacOS/rnstories.rev"
> 
> 10/27/04 9:31:10 AM
> 253,7,1
> 241,7,1,mouseUp
> 353,0,0,button id 5558 of card id 1085 of stack "/Applications/Read
> Naturally SE 2/rnse.app/Contents/MacOS/rnstories.rev"
> 
> 10/28/04 10:05:01 AM
> 76,321,9
> 144,321,1
> 253,315,1
> 253,314,1
> 490,313,1
> 241,313,1,CloseAllStacks
> 353,0,0,stack "/Applications/Read Naturally SE
> 2/rnse.app/Contents/MacOS/rnse"
> 
> 
> I put the date/time stamp in just to help me keep track of things.  Now, the
> first set of info tells me that the error occurred in the UpdateChecks
> handler, which was called by preOpenCard of card id 1820 of stack
> "rnstories.rev".  That much I understand.  But how can I tell what the
> actual error was?  Anyone know?  Do the lists of numbers mean anything?  The
> docs refer to the cErrorsList property of card 1 of stack "revErrorDisplay".
> I can display that list just fine, but that's all it is, a list of
> *possible* errors.  I'm hoping that one of the numbers in the error details
> will point me to the line of cErrorsList that contains the error that
> occurred.  Does anyone know if this is the case?

Yes, that's what happens. If I remember right, the first number is the 
line number of the cErrorsList that describes the error. The second item 
is the line number in the executing script where the error occured, and 
the third number is the token that caused the error. So:

87,1308,18

would have line 87 of cErrorList as its textual error message; the 
problem happened on line 1308 of the currently executing script, and 
occured because of a problem with the 18th token in that line. I'm not 
clear on the fourth item in those lines that have it, but it appears to 
be the value of the token at the time that it errored.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com