JDK-6542106 : When a Swing component is painted to an image, it should not go through BufferStrategyPaintManager
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2007-04-03
  • Updated: 2011-01-19
  • Resolved: 2010-08-06
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6-poolResolved 7Resolved
Related Reports
Duplicate :  
JDK-6668436 - Painting a component to an off-screen image should not affect the double buffer
Relates :  
JDK-6542109 - Clean up Swing painting to non-screen graphics.
Description
Currently, Swing painting goes through BufferStrategyPaintManager even when painting to an image. This causes two problems:

1) Double buffering of the paint, which is not needed.
2) The BufferStrategyPaintManager is marked out of sync until the next paint of the entire root pane.
Comments
EVALUATION Fix is to avoid going to BSPM when painting to a graphics that's known not to be the screen graphics for the component.
03-04-2007