On 20 Aug 2007 at 16:49, Stephen Mercer wrote:

> Execution Highlight Point... a trigger to turn on or off execution
> highlighting.
> Interesting. But... may I suggest a broader dream?

Dreaming is free for all, isn't it. I think there once was a ini-setting
for enabling dream-related features...

> 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

Well, that's quite a dream. What more do you want for debugging ? You
would need to find a way to keep it understandable for the user, with all
these interconnected debugging features in there... But if you can make
it, that would be amazing.

I have a dream myself... I would like to be able to modify a value... I
know the code is optimized so the temporary values in CPU registers are a
problem, but sometimes it should be sooo convenient to just decrement a
value and have a loop repeat once more, like you can do on a global. If I
could only change some of them (and not the optimized ones) that would be
fantastic. And easy to understand for any user.

Joris
--
Joris Robijn <joris@robijn.net>
Mobile: +31 6 288 41 964