On 11/09/2013, at 5:33 PM, Etienne Samson <samson.etie...@gmail.com> wrote:
> I think the best way for what you're trying to do is to subclass > NSNotificationCenter (or at least provide your own framework-wide singleton > that quacks like it), wrap -postNotification: with some dictionary-munging > code that keeps tracks of the last notification send by notification name, > and have -addObserver:… (you'll have to find the one that actually is the > designated call, the one all the others expect) check that cache and issue a > -postNotification: call for that object only (you don't want to notify all > old objects, only the one that just registered). I'd disagree with this - subclassing something like NSNotificationCenter is a sledgehammer to crack a nut, and don't forget about the potential side effects where it is used for lots of other unrelated notifications. Why not just have a class method on the sender of the notification that stores the most recent data sent by an instance of that class? Then when a new instance of the notification receiver is inited, it can grab the latest data from the class method to set itself up? No hacks required. --Graham _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
