[APBeta] Diagnosing exceptions in my script

[Paul Rodman]

On Aug 23, 2009, at 12:23 PM, Michael Portuesi wrote:

> Thanks for the info.  I assume this limitation regarding exceptions  
> applies only to embedded scripts, otherwise the compiler vendor  
> wouldn't have customers/developers for very long.

Correct.

> I'll have a look at my script today.

I still haven't gotten around to debugging the "big star" problem/s.

Paul R.

>
> Michael P.
>
> On Aug 22, 2009, at 6:10 PM, Paul Rodman wrote:
>
>>
>> On Aug 22, 2009, at 5:56 PM, Michael Portuesi wrote:
>>
>>> I've returned to my Print Finder Charts script, and I've  
>>> discovered that AP has changed out from underneath it when I last  
>>> touched it in June.
>>>
>>> I'm getting an exception when I run my script.  Unfortunately, all  
>>> I get is a dialog box that says: "Unhandled exception occurred  
>>> during execution of the script!" which is not helpful.
>>>
>>> Is there a way I can get more detailed information about the  
>>> exception?  Class type of the exception, detailed exception  
>>> message, error code, stack trace, line number on which the  
>>> exception occurred?
>>
>> Unfortunately not. It's a compiler/framework shortcoming that the  
>> vendor hasn't resolved yet. At least it doesn't crash the entire  
>> app as with V1...
>>
>> My strategy is to dot the code with
>>
>>  debug "Point A"
>>  ...
>>  debug "Point B"
>>
>> etc. and narrow down the line of code that's causing the problem  
>> (i.e. if the Debug window has "Point A" but not "Point B" then you  
>> know the exception lies somewhere between).
>>
>> Paul R.