Q: debuggging widget applications in IDL 5 [message #10960] |
Fri, 30 January 1998 00:00 |
Jack Saba
Messages: 30 Registered: January 1996
|
Member |
|
|
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. Right now it looks like
we're going to have to keep IDL 4 around just for this.
If you send email, reply to the address below.
--
Jack Saba <jack@magus.stx.com>
|
|
|