On Thu, Aug 14, 2008 at 7:55 AM, Graham Cox <[EMAIL PROTECTED]> wrote: > Here's the hack. The two object classes define different strings for the > "did change" notification, but my UI management code would prefer not to > care about what actual object type is in use. So I made the literal string > constant for one object's message the same as the string constant for the > other class. As hacks go it's probably fairly mild as they both mean much > the same and the two object types are unlikely to get confused with each > other elsewhere.
Well, despite the cause of your problem, if your two classes really are conceptually sending the same notification, I would define the notification symbol in your application, and have the linked bundle reference it as an extern symbol. If not, then don't make them the same notification. To me, if both classes want to say "something changed!", they should be using the same declared notification. If you really want to say "something about foo changed!" and the other to say "something about bar changed!", then make them two separate symbols. --Kyle Sluder _______________________________________________ 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]
