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 #10949 is a reply to message #10947] Fri, 30 January 1998 00:00 Go to previous messageGo to previous message
Liam Gumley is currently offline  Liam Gumley
Messages: 473
Registered: November 1994
Senior Member
Jack Saba wrote:
>
> 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.

Just type

XMANAGER,CATCH=0

at the command line *before* you run your widget app, or put it in your
IDL startup file. It works just fine for me (IDL 5.0.3, SGI Irix 6.2).

Cheers,
Liam.
[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:32 PDT 2025

Total time taken to generate the page: 0.79828 seconds