JDK-4363288 : Swing should use VolatileImage for double-buffering to improve performance
  • Type: Bug
  • Status: Resolved
  • Resolution: Fixed
  • Component: client-libs
  • Sub-Component: javax.swing
  • Priority: P2
  • Affected Version: 1.3.0
  • OS: solaris_10
  • CPU: generic
  • Submit Date: 2000-08-16
  • Updated Date: 2000-08-30
  • Resolved Date: 2000-08-30
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 Availabitlity Release.

To download the current JDK release, click here.
Other
1.4.0 betaResolved
Description
Now that Java2D provides VolatileImage support to speed up rendering /blitting
images, Swing should be modified to use this for it's double-buffering support.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin merlin-beta FIXED IN: merlin-beta INTEGRATED IN: merlin-beta
2004-06-14

PUBLIC COMMENTS Now that Java2D provides VolatileImage support to speed up rendering /blitting images, Swing should be modified to use this for it's double-buffering support.
2004-06-10

EVALUATION We will modify the RepaintManager to include a method to return a volatile image and change JComponent and JViewport to "get" a volatile image to use for double-buffering. Since it's (remotely) possible for the rendering to the VolatileImage to fail, we will provide a fallback mechanism to use a standard image buffer in that case. amy.fowler@Eng 2000-08-16
2000-08-16