comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: Q: debuggging widget applications in IDL 5
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Q: debuggging widget applications in IDL 5 [message #10956 is a reply to message #10947] Fri, 30 January 1998 00:00 Go to previous message
davidf is currently offline  davidf
Messages: 2866
Registered: September 1996
Senior Member
Jack Saba (jackxxx@magusxxx.stx.com) writes:

> In IDL 4, when an error occurs in a widget application that uses
> XMANAGER, the program stops in the module that caused the error.
> IDL tells you what line the error occurred on and you can look at the
> variables to get a handle on the problem. With IDL 5, XMANAGER catches
> the error and returns a message that starts something like
>
> XMANAGER: Caught unexpected error from client application.
>
> You are not thrown out to the IDL prompt, and you are not told what
> module the error occurred in.
>
> Is there any way to get IDL to behave the way it did in IDL 4, or at
> least to tell you where the error occurred? I tried using the new
> CATCH=0 option on the XMANAGER statement, but either I haven't figured
> out how to use it, or this isn't the solution.

I can't figure it out, either. When I set Catch=0 on my
Windows NT machine (IDL 5.0.3) my widgets programs don't
run at all. Ever. I don't *think* this is how it is suppose
to work, but nothing I've tried works except just removing
the CATCH=0 keyword.

I deal with the problem of where an error occurs by writing
small, very modular event handlers and by having my own CATCH
error handling in these modules. In this way, I always know
in which module the error occurs. And because the module is
small, a few minutes of detective work can usually isolate
the problem.

But I do wish there was a better solution. What would be
ideal is for there to be a !Line_Number_Error system variable that
gets set whenever an error occurs in a program module.

Cheers,

David
-----------------------------------------------------------
David Fanning, Ph.D.
Fanning Software Consulting
E-Mail: davidf@dfanning.com
Phone: 970-221-0438
Coyote's Guide to IDL Programming: http://www.dfanning.com/
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Beginner fails miserabley at first hurdle 0.05 0.05
Next Topic: Re: command line args for pvwave ?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 19:25:31 PDT 2025

Total time taken to generate the page: 0.63853 seconds