One thing I want to stress:

Probes and the like are very good to use once you know where your problem
is. They are a little more complex but give more details. Custom probes
can probably do about anything you need. Unfortunately, it takes a while to
set up anything more than simple probes.

I am looking for a better way to quickly figure out where the problem is.
If I know it is in one area, I would just like to do execution highlighting
in that area to speed up overall execution. Being able to turn it off (or
greatly accelerate it) within loops would also be a godsend. I really like
the way the size of arrays are represented during highlighting, so I can see
the sizes and how the autoindexing is working. Many times I find my bug
involves autoindexing the wrong dimension, or enabling/disabling
autoindexing.

I really want a new tool (or enhancements) that I can set up and use very
quickly. I don't want to spend the time setting up probes everywhere I
think the problem may be.

Maybe the solution for me is as simple as being able to speed up
highlighting, and having the values displayed be more persistent. I hate
when the values all disappear after pausing execution.

Bruce

------------------------------------------
Bruce Ammons
Ammons Engineering
www.ammonsengineering.com
(810) 687-4288 Phone
(810) 687-6202 Fax