Thankyou so much! I hope this will help solve my problem!
I'll let you know
Cheers,
A.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group,
Am 15.09.11 06:47, schrieb Sorab Pithawala:
I have made a ZIP file containing the code, XML and a small readme.
Why do you do it that way:
h1 = BitmapFactory.decodeResource(res, R.drawable.help1_l);
ImageView im = (ImageView) findViewById(R.id.helpImage);
im.setImageBitmap(h1);
and not like
Presumably because he needs to recycle the switched out bitmap
immediately, rather than wait for Android to decide that it has time
to clean out the old bitmaps.
I've run into this issue a lot myself when working with largish
bitmaps. The GC for bitmaps is pretty rubbish - especially if your app
Hi there,
@Ralph - I do it my way because it seems to me that multiple calls to
getResources() is generally considered to be a bad thing (read it online),
and like Michael said I want to make sure my next Image loads without fail.
That and the fact that in an actual app, you would indeed have
Hi Sorab,
I have a similar issue: please could you provide
more code to better undestand the solution that you found?
Thanks,
A.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
Hi there,
I have made a ZIP file containing the code, XML and a small readme. Download
from BitmapTest.zip http://db.tt/hXH0d00.
Regards,
Sorab
On 14 September 2011 18:56, A. andreabl...@gmail.com wrote:
Hi Sorab,
I have a similar issue: please could you provide
more code to better
Solved the issue by having a separate Bitmap object for each Image and then
when the user navigates to the next page, decode the next bitmap, show it on
the ImageView and then recycle the previous one. For eg. in my gotoNext()
switch(index)
{
case 1:
7 matches
Mail list logo
