I will look into that.
Thank you
On Mar 12, 2009, at 5:18 PM, Wyatt Webb wrote:
Well, then maybe UIImageViews aren't the right choice. You could
either use many CALayers or even a single large UIView(if you need
user input events) or CALayer subclass where you render the images
yourself.
Well, then maybe UIImageViews aren't the right choice. You could
either use many CALayers or even a single large UIView(if you need
user input events) or CALayer subclass where you render the images
yourself.
I presume there are only a small number of different images and you're
using the
> Is it possible to add multiple images to one UIView.
>
> I am hoping that would help my memory issue.
Checkout NSMatrix. It's designed to do exactly what you want - provide a
lightweight way of managing a large number of small objects which need to
render themselves and respond to input event
My images are very small.
I have approximately 100 lines with 24 small images per line. These
are all one one scrollable view. I am using a UIImageView to position
each one.
Just trying to get efficient as possible here.
On Mar 12, 2009, at 4:48 PM, Wyatt Webb wrote:
Do you mean in some wa
Do you mean in some way other than embedding multiple UIImageViews or
multiple CALayers? Unless your images are very small, I doubt the
overhead of the UIView objects is what's causing a memory problem.
Maybe I'm misunderstanding. Can you give us more detail about the
current arrangement yo
Is it possible to add multiple images to one UIView.
I am hoping that would help my memory issue.
Thanks
James Cicenia
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact
