Veteran
Joined: 26 Dec 2006 |
Posts: 253 |
Location: Phoenix, AZ |
|
 |
Posted: Mon Sep 03, 2007 12:40 pm |
|
 |
 |
 |
 |
That's a usable work-around for now, but it's not the same and not nearly as good. For one, it requires that I enter the value of the variable, which may not be fun - perhaps a big array or even some binary data. Also, as soon as you hit the next break, you must update the breakpoint's condition; you can't just do a quick observation of the variable and hit Run again. If you're trying, for example, to identify the particular loop iteration that's sending a variable's value into never-never-land, this would get very tedious very quickly.
However, I can see how such a flag in the Watch tab would be implemented under the hood using conditional breakpoints that are automatically set and updated... perhaps a path to quick implementation?
|
|