Torben et al.,

This would be a super tool and Mike's speed control and persistence
and Stephen's expansion would make it even better. Gavin and Jim
might have the start of the simple way to implement it. Albert's
concern for the color blind would also be important. John's related
tree debugging aids would also be great.

But I was wondering if it might be simpler to implement a slightly
more restricted tool that might solve most of the needs of all these
people, needs highlighted by Bruce's response. Consider your original
description but in the reversed order: a new "Execution Highlight
Point" that can turn highlighting OFF or ON. It might be easier to
implement the tool if it were allowed to require that execution
highlighting be turned on already, to avoid the problem Jim
highlighted. In that environment, it could turn off highlighting of a
branch of code and then turn it back on later. That would address
Bruce's need to skip the uninteresting parallel while loops. It might
help Mike by allowing him to concentrate all his processing bandwidth
on narrower areas of interest, the complement to slowing down the
whole world.

I'm not sure if it would be easier to implement (Stephen?) but, if it
were, would it answer the bulk of the need?

--
EnWirementally,
Paul F. Sullivan

----------------------------------------------------

SULLutions (781)769-6869
"when a single discipline is not enough"

visit http://www.SULLutions.com

----------------------------------------------------