Home/ Questions/Q 6877773
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T04:38:29+00:00

In the API demo , there is an example of an effecient list adapter

  • 0

In the API demo , there is an example of an effecient list adapter in which all the bitmap are preloaded in the adapter constructor : 

// Icons bound to the rows.
mIcon1 = BitmapFactory.decodeResource(context.getResources(), R.drawable.icon48x48_1);
mIcon2 = BitmapFactory.decodeResource(context.getResources(), R.drawable.icon48x48_2);

In case the adapter have to deals with a lot of bitmap, is it still a good practice or will it be better to do something like that in the getView : 

holder.myImage.setImageDrawable(context.getResources().getDrawable(R.drawable.icon48x48_1));

Note in my case , i can have something like 10-15 possible bitmap , but only a few will be used at same time. I’m concerned by the memory used by the adapter.

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If the icons are truly 48×48 pixels, they won’t be that big, and since you have a known small set of them, preloading them is probably fine. I would not use that approach if:

    • the images are massive, or
    • the images are being loaded from places other than resources, or
    • there would be more than a few dozen icon-sized images

    You can always dump your heap from DDMS and inspect it with the Eclipse MAT plug-in to get a perspective on how much heap space is actually being used. Test it on Honeycomb or Ice Cream Sandwich, though, as you get better results for tracking bitmap heap consumption.

    • 0