restrictions
(primarily on image size).
On Jan 11, 2009, at 9:04 AM, Glenn Bloom wrote:
I don't think I see this issue in my own code using UIImageView with a
like number of JPEG's. How large are yours? For a variety of reasons, I
have found that optimizing mine as 150KB or less each
I don't think I see this issue in my own code using UIImageView with a like
number of JPEG's. How large are yours? For a variety of reasons, I have
found that optimizing mine as 150KB or less each is acceptable for 480 * 320
pixel images. On the other hand, while speed appears fine (and I can
So it looks like I now have a better solution for copying an image file and
reducing its size both in dimensions and in bytes, thanks to a couple of
recommendations I received. Of course, other recommendations made clear
that I need to learn more about alternative approaches:
- some
Can anyone recommend a best practice for resizing an image to reduce its
size in terms of both bytes and visible dimensions, retaining the new
smaller image and eliminating the original from memory? In how I go about
this now, I am concerned about memory and efficiency.
thanks in advance for any
, so
will get back to this in the AM maybe with more thoughts as well and will
post again. Thank you both.
On Thu, Dec 11, 2008 at 2:44 PM, Steve Christensen puns...@mac.com wrote:
On Dec 11, 2008, at 5:43 AM, Glenn Bloom wrote:
Can anyone recommend a best practice for resizing an image
In response to an excellent first reply, below is a revision to my original
post that corrects various points, and that also incorporates some changes
to better focus my remaining questions - please disregard my original post
in favor of the following:
In the course of trying to understand
In the course of trying to understand UIViewController memory warnings on
the iPhone, I've found various useful threads online, and in particular, was
very glad to follow the numerous recent posts in this forum with the subject
'Outlets / IBOutlet declarations'.
In response, I've written a test
