Is this a bug in setKeys:triggerChangeNotificationForDependentKey:?
Is this a bug in setKeys:triggerChangeNotificationForDependentKey:?
- Subject: Is this a bug in setKeys:triggerChangeNotificationForDependentKey:?
- From: Óscar Morales Vivó <email@hidden>
- Date: Mon, 25 Jul 2005 22:47:01 -0400
In one of my projects I've noticed that if in the +(void)initialize
method of a base class I call
setKeys:triggerChangeNotificationForDependentKey (and not call that
same method with the same parameters for the derived class), it won't
fire the corresponding key-value observing methods in my derived class.
In case it makes a difference, it's a Core Data project.
I'll file a bug report about it, but if there is any reason this is
by design I'd love to hear it (and have the bug cancelled).
Thanks in advance for your help:
Óscar Morales Vivó. _______________________________________________
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