On May 20, 2012, at 02:21 , mlist0...@gmail.com wrote: > Your alternate approach is essentially to give up on tracking areas, no? The > tracking area approach has an attractive simplicity, especially once my view > hierarchy and cursor tracking needs get more complicated, but if it's broken, > I guess I'll have to roll my own solution. And file a bug report.
Not "give up:, really. Tracking areas are important because they provide much-improved 'mouseMoved:' behavior. The problem is that your code isn't the only code using tracking areas, and trying to predict which tracking area will "win" the cursor is difficult. Invoking 'cursorMoved:' from other events having a mouse location isn't an admission of defeat. It turns a fragile boundary-crossing solution into a robust state-detection solution. _______________________________________________ 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
