On Fri, Apr 4, 2008 at 9:18 PM, Adam R. Maxwell <[EMAIL PROTECTED]> wrote:
> Can you do that by creating too many images? The docs for +imageNamed:
> say "...you do not need to retain the returned image object unless its name
> could be cleared. You can clear an image object from the table by pas
On Apr 4, 2008, at 6:43 PM, stephen joseph butler wrote:
On Fri, Apr 4, 2008 at 8:29 PM, Matt R <[EMAIL PROTECTED]> wrote:
imgArray[x] = [NSImage imageNamed:@"foo.jpg"];
Throughout the scope of my app, when the drawRect fires, these images
always
appear properly. But today I suddenly relea
On Fri, Apr 4, 2008 at 8:29 PM, Matt R <[EMAIL PROTECTED]> wrote:
> imgArray[x] = [NSImage imageNamed:@"foo.jpg"];
>
> Throughout the scope of my app, when the drawRect fires, these images
> always
> appear properly. But today I suddenly released that I never retained them,
> which has me kind
I'm sorry for asking a memory management question but I was hoping someone
could help me understand this situation.
I have a series of NSImages I place in an array (subclass instance variable)
when a custom NSView is init'd:
initWithFrame:
imgArray[x] = [NSImage imageNamed:@"foo.jpg"];
