I've popped the three debug classes I use on github.
They do:
ValueTree inspection (and a bit of editing).
Component tree inspection (and a bit of cock-up detection).
float * buffer inspection for debugging errant DSP code
They are all ugly but functional (and trivial to use).
Here's a screenshot from the component debugger - showing the class name, component name, ID and bounds. One with zero size is marked in red, and ones not marked as visible are in grey.
It'd be great to have some hooks in Component to report things like number of paint calls and profiling information, like time taken inside paint(...).
And being able to move components in it .... I might have to add that ;-) Just added
Hey I'm getting a "missing dependencies" problem in IntroJucer. It says it needs juce_gui, but there is no juce_gui. Is it juce_gui_basics, juce_gui_extras, or both?
By the way, I'm loving the component debugger. I think I'll be using this a lot. I'm suprised how easy it is to set up too. I'll have to give the other debugger tools a spin too. :)
Sweet! I was thinking about making something like the Component Tree to help parse/understand Component layout for large foreign projects . Very very nice to see it's already made! :D