Check it out:
http://weblogs.java.net/pub/wlg/1739
Lots of useful info.
Excellent!
Finally an article we can link to that covers all of it…
or atleast nearly all of it.
There is no mention of Image.[get/set]AccelerationPriority(),
(or the temporary workaround of getRaster().getDataBuffer())
for those cases where a managed images is not wanted.
Yep, this wasn’t an article on managed images, but more about images in general (a larger and more wholly confusing topic…).
I was thinking of writing an article dedicated to managed images sometime soon; they’ve cropped up in the context of most of my blogs and presentations, but perhaps it’s time they had their own spotlight. Thanks for the idea about "un"managed images; I’ve been mostly focused on how to get people to use managed images so far, not how to defeat the system…
(Note that setAccelerationPriority() is just a stub in the 5.0 release; it sets a hint internally which is thus far ignored. So this won’t get you what you are seeking (image management punting), at least at this point. We had to get the API in there during this major release, but didn’t get a chance to fill in the details yet. Grabbing the data buffer is the only way to force image "un"management for now…)