You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using a ListView and ParseQueryAdapter with custom rows, and each of this rows includes an image. The problem when using ParseImageView was that each time I pressed "Load more" (because I'm using pagination) every ParseImageView in the ListView will show the placeholder again.
Now that I'm using Picasso it doesn't happen, the placeholder is only shown for images that were not loaded already.
So, my suggestion is that you can use the Picasso library for loading ParseImageView.
Thanks.
The text was updated successfully, but these errors were encountered:
I would also agree with this, and Picasso is not the only library out there with advanced cached strategies, which are clearly not implemented in (and out of scope for) Parse UI. As always, no need to reinvent the wheel. All adapter-based views look just bad with ParseImageView. Please consider this.
Hi, it's just a suggestion.
I am using a ListView and ParseQueryAdapter with custom rows, and each of this rows includes an image. The problem when using ParseImageView was that each time I pressed "Load more" (because I'm using pagination) every ParseImageView in the ListView will show the placeholder again.
Now that I'm using Picasso it doesn't happen, the placeholder is only shown for images that were not loaded already.
So, my suggestion is that you can use the Picasso library for loading ParseImageView.
Thanks.
The text was updated successfully, but these errors were encountered: