Re: Why does this leak memory?
Re: Why does this leak memory?
- Subject: Re: Why does this leak memory?
- From: Matt Ball <email@hidden>
- Date: Sun, 10 Jul 2005 22:19:17 -0400
No. If I have 50 rows, there will be 50 images in the array. The other
indexes contain other information about the row, such as whether a
button should be enabled or disabled.
I put that NSLog() into my code, and it reports "NSImage" as expected,
even when it crashes (signal 11).
- Matt Ball
On 7/10/05, Rosyna <email@hidden> wrote:
> So if there are 50 rows, you'll have 301 images in the array?
>
> If I was me and I were having this issue, I'd make sure to log the
> class of the return value from NSImage *image = [array
> objectAtIndex:indexToQueryForImage];
>
> NSLog(@"%@", NSStringFromClass([image class]));
>
> @"%@" isn't necessary, but I use it in practice all the time incase
> the object I'm trying to print is NULL.
>
> Ack, at 7/10/05, Matt Ball said:
>
> >Yes. The number of images in the array changes. I have a button in my
> >window which adds a new row to the tableView. For each row, my array
> >stores several pieces of information. The row*6 + 1 determines what
> >index the requested image is at.
>
> --
>
>
> Sincerely,
> Rosyna Keller
> Technical Support/Holy Knight/Always needs a hug
>
> Unsanity: Unsane Tools for Insanely Great People
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden