Debugging and the execution path

[Jim Ault]

On 12/24/05 7:30 PM, "Jerry Daniels" <jerry at daniels-mara.com> wrote:

> It seems there are two requests...
> 
> - one to make a variable whose value has just changed to be easy to
> see and
yes
> - another to stop execution, like a breakpoint.
(not for me)

I care less about auto stop, since I have rarely used this even in apps that
allow it.  I usually debug certain functions or loops, get them working,
document them in the code and move to a different problem.

Most useful is to see a subset of the variables in use in the top group, NOT
hiding the ones that I have assumed I don't have to inspect, then find out
that, yes, I did need to note the 'flag or status or array', etc.

My desired interface would be:
arrowFlag | true
backNav | cd id 1003
countOfImages | 13
lastImgID | 1244
it | daffodill
potColor | terricotta
potStyle | glazed
potColorsArr | <array>
* soilList | loam cr clay cr rubber cr sand

the * is a flag, set by my click during debug session, where this variable
would show its full contents in the "lower pane" so I could view the
building of the list, or the result of the replace series,

Does this make sense?

Jim