JUCE 8.0.13 released

[anthony-nicholls]

@kunitoki

I wonder if people will ship to customers with Melatonin inspector

I could be wrong, but I think there are already cases of this.

@kunitoki

(and enabling that will require a special build anyway)

I’ve seen cases of special key combinations, an option in a menu, or it could be a setting stored in a file on disk.

@kunitoki

potentially creating issues if for some reason a Melatonin release will by mistake start allocating inside the listener callback even when disabled.

If the inspector isn’t created / attached to anything then it shouldn’t be receiving callbacks so I think it’s relatively safe in that regard.

@kunitoki

There is no frame-level measurement in that, every component measurement is independent and there is no correlation to frame deadlines, making it impossible to attribute UI work to an actual presented frame budget or detect deadline misses in a meaningful way, which is rather important on high FPS realtime rendering apps. And you can’t do that in just Component listeners without ingraining the infrastructure into your renderer. Just my 2 cents.

I appreciate the feedback and I see your point, I’ll give this some thought. You could approximate total UI paint cost in a single frame by listening to the top-level component but that is only part of the story. Ultimately this wasn’t the focus of the work and I think that would be a separate chunk of work.

The work carried out here mostly came off the back of the component paint refactoring, the demo that was added to demonstrate that work (which in-itself came off the back of a talk I did in Japan last year and later a talk I did for ADC), and this FR: Callback or other mechanism for exposing Component debugging/timing

Maybe all that’s needed for now is an easy way to add some sort of global component listener?