# Component::Paint change in 6.0.7?

**URL:** https://forum.juce.com/t/component-paint-change-in-6-0-7/44781
**Category:** General JUCE discussion
**Created:** [March 3, 2021, 9:49pm UTC](https://forum.juce.com/t/component-paint-change-in-6-0-7/44781 "2021-03-03T21:49:00Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![amusesmile](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/amusesmile/32/681_2.png) [@amusesmile](https://forum.juce.com/u/amusesmile)
#### Post date: [March 3, 2021, 9:49pm UTC](https://forum.juce.com/t/component-paint-change-in-6-0-7/44781/1 "2021-03-03T21:49:00Z")

</div>

Over on Mac OS I’ve been seeing some odd painting behavior where it seems that the Component::Paint(Graphics& g) function can be called without the resulting pixels being shown on the display. It’s as if whatever is computed in Paint is stored internally but not sent to the screen.

I’ve tried things like turning on JUCE\_ENABLE\_REPAINT\_DEBUGGING and putting a print statement inside of some questionable component- say a slider on one of our plugins. If I open the DAW in a terminal I’ll see the print statement firing constantly, telling me that the Paint function was called, however the JUCE\_ENABLE\_REPAINT\_DEBUGGING square around the component is not changing.

Has anyone else experienced this? Did something fundamentally change in a recent JUCE update regarding how paints are called or updated under the hood on Mac? Thanks.