This fixes two issues with the Swing painting:
1. As reported in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27185, an
optimization in JComponent.paintChildrenOptimized() didn't work quite
right. Looking at it, it seems that this optimization doesn't gain much
anyway, possibly the overhead of calcu
Hi,
I fixed the Swing painting a little more. This finally removes the
flickers that have been visible from time to time (to be more precise:
when the AWT triggers repainting, which is entirely different from when
Swing triggers repainting).
Effectively, this adds a check in the paint() method if
> - in Sun's JDK, _all_ Swing components are doublebuffered-enabled by
> default
Not with Apple's JDK on Mac OS X where the window server handles the
double buffer.
-- Pinski
___
Classpath-patches mailing list
Classpath-patches@gnu.org
http://lists.gn
On Sep 24, 2005, at 5:08 PM, Andrew Pinski wrote:
- in Sun's JDK, _all_ Swing components are doublebuffered-enabled by
default
Not with Apple's JDK on Mac OS X where the window server handles the
double buffer.
I take this back.
Thanks,
Andrew
___