Yes, before Debug came along, the IDE and it's messages and warning was my main go to for debugging.
Seem to me the list of unused variables and array provided by the IDE only came at a successful run through of the program. When I have a lot of lines of buggy code, and I have lost track of variables and arrays I have altered or abandoned along the way, I have been using our new Debug feature to find those variables (or Array with the first index) that have a value of zero and repurpose them. The problem that catches me is that the variable or array could be vital and just sitting at zero at the exact time I'm calling to see it's value( v's a variable or array which I have inadvertently abandoned).
The other problem with my use of Debug is the quantity of the variables and arrays. The abandonment or inadvertent loss of use generally is happening when I have lots of variables and arrays. I need to "Select ALL" in Debug but there are too many, so I'll set a break and try to break up the list into smaller groups to seek the unused out.
I was wondering if there was some method in the filter feature of debug that would do the same thing as the IDE and just list those with a zero value but just up to the point of a set break. I'd need an IF statement in the filter ... IF value = 0 then IMP "Abandoned"
