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 
Return to the default flat view Create a new topic Submit Reply
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
[Message index]
 
Read Message
Read Message
Read Message
Read Message
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: Mon Dec 01 12:12:08 PST 2025

Total time taken to generate the page: 1.12356 seconds