Just catching up on my eamil after a vacation, I saw Stephen's post. A
hearty YES!
I started to try to code something up in the past, using scripting, to
manage creating
saving and starting collections of custom probes, but never finished it.
I put the
beginnings of this on LAVA, as a "Wire Table" tool. I like the triggers
Stephen
describes below much better.

Now, to expand the dream a bit, (maybe in the second version ;-) ) if we
could
set and create such triggers (semi) automatically, based on search
criteria, ie
look through a hierachy or project and tag everywhere that met criteria
X with
a trigger of type Y, and tag M's with an N, etc.

Stephen, you're on to something, sign me up for the beta! (or the alpha,
since
we are just dreaming at the moment)
Mike

InYourDreams=TRUE

***********************************
Michael C. Ashe Imaginatics
Control & Test Systems
11 Quinley Way
Waterford, CT 06385
Phone: 860-444-2141
Cell: 860-961-0876
email: michael.ashe@imaginatics.net
***********************************

> Subject: Re: How about a "Execution Highlight Point"?
> From: "Stephen Mercer" <stephen.mercer@ni.com>
>
> Execution Highlight Point... a trigger to turn on or off execution
> highlighting.
> Interesting. But... may I suggest a broader dream?
>
> How about simply an "execution point trigger." Something that can be set
> on a block diagram when it is running. Triggers that could
> a) turn on and off execution highlighting
> b) turn on and off breakpoints in your code
> c) turn on and off probes
> d) open or close front panels
>
> In short, triggers that let you debug code without having to constantly
> manage your own debugging. I've thought about such an array of triggers
> for years, but never done anything with the idea.
>