There is probably some kind of image caching system behind the scenes, but I can't find any implementation details...
Scenario 1: ImageView v1, v2; ... v1.setImageResource(R.drawable.img1); v2.setImageResource(R.drawable.img1); I guess that "img1.png" won't be loaded and decoded twice. Instead, v2 will be given the same BitmapDrawable as v1, or at least a kind of proxy that points to the same pixel-data... Makes sense? --- Scenario 2: - A lot of different bitmaps are loaded via ImageView.setImageResource (int) - At some point, some "internal capacity" is reached and the system needs to purge pixel-data (LRU like strategy) before going further with loading new data. - Later on, if a BitmapDrawable _ that has been purged _ needs to be actually drawn, it's data is reloaded on the fly... Makes sense as well?
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
