Re: _arrangedObjects not allocated
Re: _arrangedObjects not allocated
- Subject: Re: _arrangedObjects not allocated
- From: John Stiles <email@hidden>
- Date: Tue, 13 Dec 2005 11:35:00 -0800
If they're private members, they may be used in ways that you can't
predict. It seems like whatever you are trying to figure out is
probably a bad idea. Is there a reason you can't use the public
methods to do what you need to do?
On Dec 13, 2005, at 11:26 AM, Chris Outwin wrote:
I am trying to understand why _arrangedObjects for a subclassed
NSArrayController has a value of 0x0 in the debugger after
addObject is called.
I have a NSImageView which sends add to the custom
NSArrayController when an image is dropped.
- (void)add:(id)sender {
BFOSImage* image = [[BFOSImage alloc] init];
if (image != nil) {
[image setInputNSImage:[sender image]];
[self addObject:image];
[image release];
- (void)awakeFromNib {
[self setObjectClass:[BFOSImage class]];
Why are _contentObjectArray and _arrangedObjects shown as not
being allocated in the debugger? Thank you.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40blizzard.com
This email sent to email@hidden
_______________________________________________
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