On Thu, Aug 14, 2008 at 8:45 PM, Graham Cox <[EMAIL PROTECTED]> wrote: > > As it turns out I can get the functionality I need by simply subscribing to > both notifications, but I was trying to avoid linking in the headers for all > the object types that are contained by my data management code - the UI for > that model doesn't otherwise "need to know" what object types they are, as > apart from this one notification, they conform to a common protocol.
Why not make the notification part of the common protocol, if it really is a common notification? It's extremely bad to have two different symbols for notifications which just *happen* to be equal so that you can receive them both with a single method. It would be much better to have a single symbol, which makes it obvious what's going on. > So this isn't in any way a showstopper - but I'd like to understand the > nature of this behaviour so that a) I can avoid it again in future and b) > file a bug if it is one. This is almost certainly a bug in your code somewhere, but without seeing it, it's hard to say what it would be. Mike _______________________________________________ Cocoa-dev mailing list ([email protected]) 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]
