United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-4363288 Swing should use VolatileImage for double-buffering to improve performance
JDK-4363288 : Swing should use VolatileImage for double-buffering to improve performance

Details
Type:
Bug
Submit Date:
2000-08-16
Status:
Resolved
Updated Date:
2000-08-30
Project Name:
JDK
Resolved Date:
2000-08-30
Component:
client-libs
OS:
solaris_10
Sub-Component:
javax.swing
CPU:
generic
Priority:
P2
Resolution:
Fixed
Affected Versions:
1.3.0
Fixed Versions:
1.4.0 (beta)

Related Reports

Sub Tasks

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
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
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
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
merlin
merlin-beta

FIXED IN:
merlin-beta

INTEGRATED IN:
merlin-beta


                                     
2004-06-14



Hardware and Software, Engineered to Work Together