On Thu, Jan 24, 2013, at 07:05 AM, Markus Spoettl wrote: > Maybe the superclass (NSButton) isn't smart enough to understand the > someone > else may change the tracking areas and does something nasty with it (like > assuming all tracking areas currently added are owned too). What if you > remove > before calling super and add afterwards. That way, the superclass doesn't > see > your custom tracking areas in -updateTrackingAreas
Neither NSButton nor NSControl appears to own any tracking areas (they are owned by the cell). Neither NSButton nor NSControl overrides -mouseEntered:. So the superclass has no opportunities to subvert Nick's efforts. Nick should really debug this like a memory management issue to see what zombie object is actually being messaged. Until we have that information, we're just grasping at straws. --Kyle Sluder _______________________________________________ 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
