@aamf - It was a while ago, but from some notes I made at the time:
I was able to prove this by putting this code in ComponentPeer::handlePaint(), in the JUCE_ENABLE_REPAINT_DEBUGGING section right after the g.FillAll(), to show the bounds of the clipRectangle. (JUCE_ENABLE_REPAINT_DEBUGGING must be enabled, but you can comment out the g.FillAll())
// TEMPORARY_EDIT
auto r = g.getClipBounds();
std::cerr << String::formatted("bounds x %03d, y %03d, w %03d, h %03d",
r.getX(), r.getY(), r.getWidth(), r. getHeight()) << "\n";
This lets us see the actual regions that are called to repaint, which JUCE_ENABLE_REPAINT_DEBUGGING does not display correctly.
See also:
