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

Home » Public Forums » archive » Re: Hate to Bring Up Another Debug "Feature"
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Re: Hate to Bring Up Another Debug "Feature" [message #57880] Tue, 08 January 2008 13:01 Go to next message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
Doug Edmundson wites:

> I just played around with things a bit and had some success in
> preventing the debug dialog from popping up. Go to preferences >
> Run/Debug > Perspectives and change the IDL Application perspective from
> "Debug" to "None". When IDL hits a breakpoint the editor should update
> to show the instruction pointer, but the debug view shouldn't pop up.
> The keyboard accelerators for stepping and whatnot should work. Now for
> the bad news... the change from "Debug" to "None" doesn't stick between
> workbench sessions. I don't know why. I'll update the associated CR
> with this potential workaround and its glitch.

Yes, this works. But for some reason, I can't step through my code
now. I keep getting the same error message in BOTH perspectives,
at the same line. Can't step over, etc. This didn't used to be a
problem, so maybe I'm just in a funny mode or something. Don't have
time to play with it right now.

> Funny, but after I
> logged the CR about the debug view popping up, someone ran into my
> office saying how much they love the debug view and that it pops up.
> ;-)

Well, I'm sure they are probably better programmers than I am.
When they make a mistake its a surprise. When I get it right,
it's a miracle. :-)

Cheers,

David

P.S. By the way, Mike's suggestion to keep the Debug View
around in the IDL Perspective, too, also works, but I've
been trying all day to eliminate views not stuff my display
with them. Adding yet more views is just defeating my whole
purpose. Still, it might be workable if I could just get
the cursor to step over the breakpoint and carry on. I'm
*sure* I've done this part before...


--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
Re: Hate to Bring Up Another Debug "Feature" [message #57882 is a reply to message #57880] Tue, 08 January 2008 12:02 Go to previous messageGo to next message
Michael Galloy is currently offline  Michael Galloy
Messages: 1114
Registered: April 2006
Senior Member
On Jan 8, 12:00 pm, David Fanning <n...@dfanning.com> wrote:
> Is there a way to stop that window from popping up? I
> don't really see the point of that window, and I *certainly*
> don't need to see it 100 times during the course of a day
> of work. :-(

How about dragging the view into another tab of something else? For
example, you could have an "area" (not sure of the Eclipse term for
it) with the Variables, Breakpoints, and Debug views as individual
tabs in it (or whatever combination you want). Then the Debug view
would be present, but not taking up any space. (Of course, the
Workbench would probably select that tab when you hit a breakpoint.)

Mike
--
www.michaelgalloy.com
Tech-X Corporation
Software Developer II
Re: Hate to Bring Up Another Debug "Feature" [message #57883 is a reply to message #57882] Tue, 08 January 2008 12:00 Go to previous messageGo to next message
Doug Edmundson is currently offline  Doug Edmundson
Messages: 58
Registered: November 2005
Member
David Fanning wrote:
> Doug Edmundson writes:
>
>> If you hit a breakpoint, the "switch perspective" functionality should
>> work.
>
> OK, yes it does. But as it happens (you had to see this
> coming, I'm sure) I don't *want* to switch now. No reason
> for me to, really. I hit a breakpoint and I just want to
> step though my code. So I get the prompt, and I answer "no".
> But that darn (to me, useless) Debug View gets thrown up
> on top of my editor window anyway in the IDL Perspective.
> I could live with it if it would just say in the Debug Perspective
> where I wouldn't have to look at it. I have to take my hands
> off the keyboard, grab my mouse, and kill it before I can
> go on.
>
> Is there a way to stop that window from popping up? I
> don't really see the point of that window, and I *certainly*
> don't need to see it 100 times during the course of a day
> of work. :-(
>
> Cheers,
>
> David

The normal behavior of the Eclipse debug model is to show the
instruction pointer and stack when IDL suspends. I think the main value
of the debug view is that one gets toolbar buttons for the stepping and
running commands. Some would like to see some of those commands on the
command line view's toolbar...

I just played around with things a bit and had some success in
preventing the debug dialog from popping up. Go to preferences >
Run/Debug > Perspectives and change the IDL Application perspective from
"Debug" to "None". When IDL hits a breakpoint the editor should update
to show the instruction pointer, but the debug view shouldn't pop up.
The keyboard accelerators for stepping and whatnot should work. Now for
the bad news... the change from "Debug" to "None" doesn't stick between
workbench sessions. I don't know why. I'll update the associated CR
with this potential workaround and its glitch.

I'm not sure what the ultimate resolution to this will be, but it's good
to know how people are using the IDL Workbench. Funny, but after I
logged the CR about the debug view popping up, someone ran into my
office saying how much they love the debug view and that it pops up.
;-) Hopefully there'll be a clean solution for everyone.

Cheers,
Doug
Re: Hate to Bring Up Another Debug "Feature" [message #58121 is a reply to message #57883] Mon, 14 January 2008 13:04 Go to previous message
Doug Edmundson is currently offline  Doug Edmundson
Messages: 58
Registered: November 2005
Member
Doug Edmundson wrote:
> David Fanning wrote:
>> Doug Edmundson writes:
>>
>>> If you hit a breakpoint, the "switch perspective" functionality
>>> should work.
>>
>> OK, yes it does. But as it happens (you had to see this
>> coming, I'm sure) I don't *want* to switch now. No reason
>> for me to, really. I hit a breakpoint and I just want to
>> step though my code. So I get the prompt, and I answer "no".
>> But that darn (to me, useless) Debug View gets thrown up
>> on top of my editor window anyway in the IDL Perspective.
>> I could live with it if it would just say in the Debug Perspective
>> where I wouldn't have to look at it. I have to take my hands
>> off the keyboard, grab my mouse, and kill it before I can
>> go on.
>>
>> Is there a way to stop that window from popping up? I
>> don't really see the point of that window, and I *certainly*
>> don't need to see it 100 times during the course of a day
>> of work. :-(
>>
>> Cheers,
>>
>> David
>
> The normal behavior of the Eclipse debug model is to show the
> instruction pointer and stack when IDL suspends. I think the main value
> of the debug view is that one gets toolbar buttons for the stepping and
> running commands. Some would like to see some of those commands on the
> command line view's toolbar...
>
> I just played around with things a bit and had some success in
> preventing the debug dialog from popping up. Go to preferences >
> Run/Debug > Perspectives and change the IDL Application perspective from
> "Debug" to "None". When IDL hits a breakpoint the editor should update
> to show the instruction pointer, but the debug view shouldn't pop up.
> The keyboard accelerators for stepping and whatnot should work. Now for
> the bad news... the change from "Debug" to "None" doesn't stick between
> workbench sessions. I don't know why. I'll update the associated CR
> with this potential workaround and its glitch.
>
> I'm not sure what the ultimate resolution to this will be, but it's good
> to know how people are using the IDL Workbench. Funny, but after I
> logged the CR about the debug view popping up, someone ran into my
> office saying how much they love the debug view and that it pops up.
> ;-) Hopefully there'll be a clean solution for everyone.
>
> Cheers,
> Doug

Okay, here's a simple solution to prevent the debug view from popping up
when a breakpoint is hit:

Preferences > Run/Debug > "Activate the debug view when a breakpoint
is hit"

Cheers,
Doug
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Re: how to find name of top level program
Next Topic: putting data into .kml (google earth) from IDL

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

Current Time: Sat Oct 11 07:10:17 PDT 2025

Total time taken to generate the page: 0.88228 seconds