>> As to the context type, I would be interested to know of cases where the
>> observer doesn't have control over the context. My understanding is that the
>> context is something that the observer sets itself when calling addObserver,
>> and it is passed back to itself in the above method call. So the observer
>> should know what kind of entity the context is, and can determine the best
>> way to compare this value.
> Subclasses or superclasses can register observers, so it’s possible for your
> observer method to get called for observations that you didn’t create.
That makes me wonder: why isn't it possible to register several, different
observers for the same thing?
That way, I wouldn't need to care about observations I didn't create, would I?
Forgive my ignorance ...
Cocoa-dev mailing list (Cocoafirstname.lastname@example.org)
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 arch...@mail-archive.com