| Re: IDL 8.0 bug -- line number of errors not given [message #72862 is a reply to message #72861] |
Wed, 13 October 2010 14:08   |
penteado
Messages: 866
Registered: February 2018
|
Senior Member
Administrator |
|
|
On Oct 13, 2:47 pm, Chris Torrence <gorth...@gmail.com> wrote:
> A few answers:
>
> 1. That w.title is a bug that is fixed in the upcoming patch release.
OK. Is there an estimate of when that release will come out?
For now I will either use text(), or (more likely) resort to directly
getting the title object and changing its string. I encountered that
problem while making a setproperty method for a class to provide
multiplot-like functionality for the new graphics (http://
groups.google.com/group/comp.lang.idl-pvwave/browse_thread/t hread/
d51b661feb93451f/).
>
> 2. You might want to use the undocumented /DEBUG keyword when using
> the new graphics. This should cause execution to halt where the error
> occurs (it disables the on_error and catch behavior).
That seemed to have no effect. At least for the methods I was looking
at (setproperty in graphicswin and graphic).
> 3. Regarding the breakpoints - this sounds like a bug - you should be
> able to set breakpoints in the lib directory. You might try setting
> the breakpoint, and then hitting the compile button in the Workbench.
Interesting. That makes the breakpoint work. I always recompiled after
setting a breakpoint, as I am aware that it is sometimes (always?)
necessary. But I usually recompile in the (Workbench's) console (I am
used to frequently doing a .full_reset_session, to make sure that
everything will be recompiled).
So the breakpoint is ignored with autocompilation or compilation with
a .compile, but not with the compile button. And that behavior is
different if the routine is in IDL's library. I checked, running the
Workbench as root, if it might be due to an inability to write to the
routine's directory, and found that it made no difference.
> 4. You might find it useful to create a project in the Workbench that
> points to the lib directory. Just do "New IDL Project", then choose
> "Create the new project from an existing directory", and choose the
> Lib directory. Be sure to turn off the "Update IDL path" since you'll
> already have the Lib on your path.
>
> Once you have the Lib directory in a project, you can do things like
> Ctrl+H to search across all files, Ctrl+Shift+R to open up a
> particular file, etc.
That does not normally work, as a project requires write permission to
the directory, which I only provide temporarily, when testing things
like this.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
