-
Bug
-
Resolution: Fixed
-
P3
-
1.4.0
-
None
-
beta
-
x86
-
windows_nt
BufferedImage objects allow the user to request the SampleModel and
Raster from a given image. Currently, when the user creates a Volatile
image on win32, by calling Component.createVolatileImage(w,h), the returned
image happens to be a subclass of BufferedImage (which may change in the
future; the return type does not guarantee it to be a BufferedImage, but
it happens to work that way at present). The user can call all of the
normal BufferedImage methods on that object, but won't necessarily get
anything sensible. For example, the Raster returned from getRaster() will
be a valid Raster, but it won't have anything to do with the Raster being
used by the VolatileImage.
Raster from a given image. Currently, when the user creates a Volatile
image on win32, by calling Component.createVolatileImage(w,h), the returned
image happens to be a subclass of BufferedImage (which may change in the
future; the return type does not guarantee it to be a BufferedImage, but
it happens to work that way at present). The user can call all of the
normal BufferedImage methods on that object, but won't necessarily get
anything sensible. For example, the Raster returned from getRaster() will
be a valid Raster, but it won't have anything to do with the Raster being
used by the VolatileImage.