Closed PaulSolt closed 12 years ago
Why is this? Can you investigate more? I've also noticed slowness, but not enough to be a big issue.
As for the decompression line: sure, that results in some slowness on load, but the idea is to keep them loaded uncompressed in memory so that they don't have to be decompressed again on each view.
Hi guys, sorry for the slow reply. I'll have a play with some larger images and see what's happening.
Regarding the decompression, as Adam said, it's to keep them loaded to avoid a noticeable lag while swiping between images.
Add larger images to the sample project and test it. The images included in the sample project are small, and aren't the size you'd get if you pulled in 5 megapixel image from the camera or any other camera.
From what I've seen, the uncompressing is also causing a lot more memory to be used in the photo browser.
It's a deal breaker for me right now, and I'm not sure why it takes longer for MWPhotoBrowser to load the images.
-Paul
On Sun, Aug 7, 2011 at 7:57 AM, mwaterfall < reply@reply.github.com>wrote:
Hi guys, sorry for the slow reply. I'll have a play with some larger images and see what's happening.
Regarding the decompression, as Adam said, it's to keep them loaded to avoid a noticeable lag while swiping between images.
Reply to this email directly or view it on GitHub: https://github.com/mwaterfall/MWPhotoBrowser/issues/8#issuecomment-1748232
Paul Solt PaulSolt@gmail.com 215-341-0407 (Cell) http://www.PaulSolt.com/
Create Easy Art on your iPhone: http://www.ArtworkEvolution.com/
The PhotoBrowser has very poor performance when I'm loading images that have1-2mb in size.
Try adding some larger photos and then browsing. It will be very slow. Removing the decompression line will help some, but it's still much slower than my own implementation that just loads the files.
-Paul Solt