Re: On Debugger Controls
- From: "R. Haynie" <rhaynie@xxxxxxxxxxx>
- To: programmingblind@xxxxxxxxxxxxx
- Date: Thu, 05 Nov 2009 23:24:10 -0500
Hi Andreas.
Andreas Stefik wrote:
> Hi Rodney
>
> I would suggest 2 more.
> 1. Set Next Statement
> This would allow you to move the cursor down past a block of code, and
> say "this is where I am now". Effectively setting the line as the
> next
> line to be executed.
>
>
> I'm not sure I follow what you mean. Are you describing jump to
> cursor, which means execute to the current line of code?
No, I mean a way of skipping code altogether. So, for example, say
there was an IF blockk. And I did not want the IF block to execute at
all, I would move the cursor to the next line of code I would want to
execute and then press the "Set Next Statement" button. Now if I
pressed "Continue" it would continue from here.
>
>
> 2. Throttle
> This would allow you to set a delay between execution of
> statements. So
> you could really throttle down and more easily watch variables change
> values while the code is continuing. (This is a great feature on
> Visual
> FoxPro... not sure who else has it.)
>
>
> Are you suggesting an animation mode that executes the program for you?
>
> Mind clarifying, I'm curious?
>
Ok, the Throttle setting is only used during the Continue or Step Over
types of commands where multiple statements will be executed. Since we
are talking about the debugger being visible, I assume there will be
places in the debugger interface where you can watch variable values.
But at normal execution speeds, you would never be able to notice the
variable values as they change. So the Throttle setting would tell the
debugger to slow down time between executing statements. This gives you
time to review things and will also give you time to press Pause when
you notice something wrong with the variable values.
-Rodney
Other related posts:
