On Jul 8, 2010, at 12:03 AM, Michael Ash wrote: > On Wed, Jul 7, 2010 at 6:34 PM, Paul Sanders <p.sand...@alpinesoft.co.uk> > wrote: >>> If you can require 10.6 (or iOS 4, maybe?) then you can use the new >>> associated object API. Use objc_setAssociatedObject to attach your >>> object to the NSEvent object, and the runtime will automatically take >>> care of destroying it for you when the NSEvent is destroyed. >> >> Sadly (and possibly mistakenly), I'm still supporting 10.4. I think I need >> to review this policy! Good idea though. > > In that case I'd guess you might want to use method swizzling on > -[NSEvent dealloc]: > > http://www.cocoadev.com/index.pl?MethodSwizzling > > Beware that swizzling is a powerful and dangerous technique, and you > want to code your override with the utmost caution, but it's a great > way to intercept methods like this.
Since the event is application-defined, any handler will, of course, also be application-defined. Can't you handle this in the handler? Or, alternatively, in an override of -[NSApplication sendEvent:]? Regards, Ken _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
