It would be nice to get a method in Image that allows me to 'make this Image
object managed if possible' without this workaround.
If you want more explicit control over acceleration then the best route
would be to create your own VolatileImage objects and manage them
yourself. That is essentially what we are doing with the managed
images, except for two differences:
- you are subject to our acceleration heuristics (which we can probably
make more convenient with a well-considered RFE)
- the original image object remains in the heap wasting memory if you
only ever want the accelerated versions
In particular, if you are managing a bunch of sprites, then having a
load routine which gets the image from ImageIO, immediately creates,
validates, and copies the loaded image into a VolatileImage, and then
drops the reference to the original loaded sprite - that will save a lot
of Java heap memory by not having duplicate copies laying around. The
price for that efficiency and control, though, is that you will need to
track when the images get unloaded...
...jim
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
