Question

I am using a Gallery with an ImageAdapter to load it with ImageViews that pull images out of my resources. My problem is that the convertView that gets passed to the getView() method in my adapter is always null. This means that a new ImageView is created each and every time getView() is called. This leads to horrible preformance because the GC is constantly running to wipe away all of these created and no longer used ImageView’s.

This is apparently a known bug: Gallery’s view cache is broken; never converts views..

My two preferred solutions are either 1. handle a cache of views in the adapter itself and take care of all the logic required to re-use them properly.
or 2. include a my own copy of the Gallery widget and try to fix it so it properly returns recycled views.

I’ve started implementing option one but am quickly realizing I don’t exactly know how to make all of the logic behind that operation. I am begining to think that option two might be easier.

I’ve found the code for the Gallery widget here: http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/2.1_r2/android/widget/Gallery.java

I don’t fully understand it, but I can see that it is calling

child = mAdapter.getView(position, null, this);

on line 745. My (shot in the dark) guess that this is the root of the problem.

Does anyone have experience with this bug. Or can anyone point me in the right direction for figuring out how the recycler situation works so that I can tweak this widget to work correctly? Or even suggest some alternate option that I may be overlooking.

EDIT: The best solution that I ever found was an implementation called EcoGallery. The only place I can find reference to it online anymore is here. To get it working you have to put each chunk from there in the correct place within your project.

Answer 1

No experience with that bug particularly, but I have done custom caching before with a 3rd party view pager (before the support lib).

It’s really not too difficult honestly. In my case, I knew there would be, at most, one item on the screen. But I also wanted the item to the left and right to be preloaded (these were webviews pulling data off the net). So I have a simple array of 3 views.

[V1, V2, V3]

Now the only thing you need to do is correlate a position in your adapter to a position in your cache. There’s a variety of ways you could tackle this. When I first spiked it out, I just made whatever my current view was to be V2 and the rotated the items of the array around when flipping the pager. So flipping to the next view would alter my array

[V2, V3, V1]

Was simple to keep up with. Or you could just do the math and calculate a position to a relative position of the cache.

Another approach is to create a last in, first out queue. Recycle views by pushing them into the queue, and when you need a view, just pop one from it.