On Apr 24, 6:16=A0pm, David Fanning <n...@[EMAIL PROTECTED]
> wrote:
> peter.n.kupfer...@[EMAIL PROTECTED]
writes:
> > I have experienced the identical problem. ITTVIS tech support reported
> > it as a bug, but said it may be hard to fix.
> > Here is the test code and comments they sent me. Sometimes the
> > breakpoints do work and sometimes the code will even ignore a coded
> > stop.
>
> I guess I could understand if a widget program was involved.
> At least I can imagine the Workbench being confused about
> what event loop it was in. But I have one file open in the
> Workbench and I am running code that should result in a
> plot. I wish to stop after I open the window for the plot,
> but before I actually draw the plot. (I'm trying to examine
> the data to see why it is being plotted incorrectly.)
>
> It really is a pretty simple set-up. No widgets, nothing else
> going on. Weird.
>
> Cheers,
>
> David
>
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming (www.dfanning.com)
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
David,
Unfortunately, your situation is the same as mine. In fact, if you set
the no_block keyword in their
test code, the breakpoint does work, and I almost always set it in my
programs. At least they are aware
of some issues related to setting breakpoints, but I can't find a
repeatable pattern when I have problems.
|
