Re: trackingAreas can be snuck up on without triggering?
Re: trackingAreas can be snuck up on without triggering?
- Subject: Re: trackingAreas can be snuck up on without triggering?
- From: "email@hidden" <email@hidden>
- Date: Sun, 20 May 2012 10:48:34 -0700
Belt *and* suspenders? ;)
_murat
On May 20, 2012, at 7:43 AM, Quincey Morris wrote:
> On May 20, 2012, at 02:21 , email@hidden 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 (email@hidden)
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:
This email sent to email@hidden