I've tidied up and updated the debugging tools here:
I was slightly embarrased by the sloppiness of the code, and as a one-time-only change I've also renamed two of the classes so it's a neater:
ComponentDebugger, ValueTreeDebugger and BufferDebugger.
I've also included:
- Natvis script for decoding JUCE objects in Visual Studio (I may have mentioned this one already).
- A new LLDB script for decoding JUCE objects in Xcode (Array, String, ValueTree etc.)
If you don't have something equivalent I think these are pretty much essential for problem solving, give them a go. And the LLDB script I think is more reliable than the current sticky suggestion on how to configure the debugger to show strings.
There's also a demo app showing the ValueTreeDebugger and ComponentDebugger in action. I don't know how best to make it build out of the box without including all the JUCE code as well. So you'll need to configure the module paths to run it. Is there a good way of handling this?
I'll add the BufferDebugger to the demo app when I get a moment or two spare.
Feedback good or bad gratefully received.