Re: Is this still true?
Re: Is this still true?
- Subject: Re: Is this still true?
- From: Scott Anguish <email@hidden>
- Date: Sun, 29 Jun 2008 19:37:42 -0400
the controller classes don't return old and new values, that's the
part that isn't implemented.
your own classes (provided they're written in a KVO compliant manner)
will return both.
On Jun 29, 2008, at 7:32 PM, Alex Wait wrote:
weird. I tried this:
[newPerson addObserver:observe forKeyPath:@"lastName" options:(
NSKeyValueObservingOptionOld| NSKeyValueObservingOptionNew)
context:NULL];
and below is my method
NSLog(@"observing");
//int oldLastName = [change o];
id oldName = [change objectForKey:NSKeyValueChangeOldKey];
id newName = [change objectForKey:NSKeyValueChangeNewKey];
NSLog(@"old value was %@", oldName);
NSLog(@"new value was %@", newName);
}
and sure enough I get both the new value and the old value. Am I
shooting
past the problem?
On Sun, Jun 29, 2008 at 3:45 PM, Hamish Allan <email@hidden>
wrote:
On Sun, Jun 29, 2008 at 9:48 PM, Alex Wait <email@hidden>
wrote:
But does the bug it talks about still exist?
I'm afraid so. But what I really want to know is, *why* won't it be
fixed any time soon? I presume there *is* a reason, otherwise why
would mmalc make such a claim?
Hamish
--
If you can't be kind, at least have the decency to be vague.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden