memory - iOS AssetLibrary Storing Pointer -
There is a question about using AssetLibrary with iOS, instead of an actual picture, store an app in an app in its app possible? Let's say I want to make a playlist, but I do not want to store the actual image.
The reason I am asking for is that when I use the image picker, then I have an image in the directory of documents documents, but once I get 25 or more , Then it starts slowing down the device (iPad 1). I scale the images down if they are too big, I had run away through the leak tool several times, and there are no leaks. I am just in a deficit where to move forward, so I want to check the options. As I have not seen anywhere where I can free up the memory
This is the place where I am now, I am curious if property library can be an option because I have not stored physical images Will go
Any thoughts on this will be highly appreciated.
By storing 25 images in the directory of documents The device should not be slow, as long as you do not try to load all 25 very large images in the same memory.
You can not permanently store an indicator in the property library asset, but you can store the URL from the url property of the ALSET representation, and then the Elasatas Library
AssetForURL: resultBlock: failureBlock: To bring back the related ALSstation later, keep in mind that users may be able to remove assets outside your program, even if your app page The land, so if you are hanging on a Elaset you must hear Elasset library change notifications to know when to reload the properties. / P>
Comments
Post a Comment