Closed vcardillo closed 9 years ago
There are two reasons why looks a little slow at displaying, first is because i download the image in the background just when the image is going to be displayed then store it locally, the second is because in the custom menu, i use lazy adapter, to display the image only at scroll, i do it for two reason, the first is because in some devices the list doesn't feel smoothly and the second is because there is some big error in android called OutOfMemoryError it causes the app crash http://stackoverflow.com/questions/477572/strange-out-of-memory-issue-while-loading-an-image-to-a-bitmap-object
What i can do is to remove the lazy adpter, but the displaying of the image is delegated to an external library to prevent OutOfMemoryError
So, do the images have to be loaded every single time? Are you saying that they can't ever be cached?
They are saved locally but could be a little slow to show, but just a little, i save them in memory and in local, i changed the list adapters to work as a normal (not lazy)
Okay. I think with a nicer more polished loading icon, this will be good enough then.
IMO everything should be loaded once, on a background thread, and then the user shouldn't see the loading symbol anymore once this initial caching is complete. Is there any reason why this can't be done?