How is that tracking explicitly done? You actually just track the access to the getters/setters?
What about me supplying the BI into the ImageIO.read operations (which is hell, but possible using the params parameters)? Will that defeat acceleration? I would love if you folks kept us "under the hood" interested people truly up to date on how things are done, and also interactions (e.g. my question about how ImageIO accesses the BIs). I feel that the whole concept of "managed images" are slightly too magicy, but by reading several articles and book(s) and some source code, I've come to understand pretty much of it. However, I feel that this should be clearly documented. If it were up to me, the managed aspect should be more overt. This way, there was no problem with the data access - you'd only state that changing the underlying data MIGHT not be reflected when drawing the BI, unless you had used the corresponding set method to set back the actual arrays. [Message sent by forum member 'stolsvik' (stolsvik)] http://forums.java.net/jive/thread.jspa?messageID=298058 =========================================================================== 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".
