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

**URL:** <https://forum.juce.com/t/fr-callback-or-other-mechanism-for-exposing-component-debugging-timing/54481>\
**Category:** Feature Requests\
**Created:** [January 11, 2023, 7:06pm UTC](https://forum.juce.com/t/fr-callback-or-other-mechanism-for-exposing-component-debugging-timing/54481 "2023-01-11T19:06:37Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![sudara](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/sudara/32/8071_2.png) [@sudara](https://forum.juce.com/u/sudara)\
**Post date:** [January 11, 2023, 7:06pm UTC](https://forum.juce.com/t/fr-callback-or-other-mechanism-for-exposing-component-debugging-timing/54481/1 "2023-01-11T19:06:37Z")

</div>

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 would love to display the last paint timings of the selected component in the inspector to aid with debugging.

 ![Figma - 2023-01-11.58@2x](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/a/a48cc9b35f8e297955e070063b9737b0e4d485fb.jpeg)

For now, I’ll give this a go by inheriting from a custom component — I just wanted to share a concrete example of what could be built if debugging/timing abilities were exposed.

---

_[View the full topic](https://forum.juce.com/t/fr-callback-or-other-mechanism-for-exposing-component-debugging-timing/54481)._