JUCE development futures

[sudara]

I put in a feature request about improved component debugging, please upvote:

FR: Callback or other mechanism for exposing Component debugging/timing

Probably a long shot, but it keeps bubbling to the surface so I’ll throw it out there. It would be amazing if the framework helped us access paint call frequency / times. For example the ability to supply a callback function to be run “beforePaint” and “afterPaint”. Or a macro that when enabled dumps some internal timing information from paintComponentAndChildren into the component’s properties. Just ideas! It came up again because I’m working on the next version of my component inspector and…

I also published a component inspector as a module — @jimc your component inspector was the inspiration, maybe it fits your needs, you can check out the features so far here (handling focus is planned).

The tool is definitely limited by JUCE not exposing things like paint timing (see Roland’s amazing work here that relies on a fork).

My feature request asks for more API abilities (like timing) as they would enable the community to build more cool things. However, if the JUCE team did want to add and maintain tooling like this, I’d offer myself as tribute be available for hire and would be happy to work on it.