New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DisplayImageOptions --> inPurgeable #209
Comments
No, there is no any reason. Some time ago I was thinking about it but I wasn't sure this option doesn't harm the lib. I wanted to investigate this option later but then probably forgot about it. Now I still not sure |
I will add |
inPurgeable only works with decodeByteArray. Since UIL is loading images from a stream, inPurgeable does nothing. |
Right you are. But maybe someone will override |
Dont you think it would be good to support inPurgable for 2.x devices ?
In this case adding the field in DisplayImageOptions, would use the flag to construct BitmapFactory.Options.
I have checked Stackoverflow and issues in here, couldn't find any comments of yours about it. Since my knowledge on that field is not that deep, and I find UIL very professional I want to ask if there is a reason for you not to put it there?
The text was updated successfully, but these errors were encountered: