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 PROTECTED]> wrote:
> On Sun, Jun 29, 2008 at 9:48 PM, Alex Wait <[EMAIL PROTECTED]> 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 (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
