JDK-4390163 : Custom Composite implementations don't work on the screen
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2000-11-16
  • Updated: 2021-07-13
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-6525932 - java.lang.InternalError: not implemented yet at sun.awt.X11SurfaceData.getRaster()
Relates :  
JDK-5106309 - OGL: xor mode broken
Description
Using a custom implementation of the Composite interface in 1.4 generates
exceptions when trying to render to the screen.  The same code will render
successfully to a BufferedImage.
Comments
EVALUATION The Composite objects need a Raster to work on, but the screen data is not normally stored in a Raster. We need to implement a pipeline to read the screen data into a Raster so that the custom Composite objects can modify the pixels. jim.graham@Eng 2000-11-21
21-11-2000