Re: NSTrackingArea message lag
Re: NSTrackingArea message lag
- Subject: Re: NSTrackingArea message lag
- From: Markus Spoettl <email@hidden>
- Date: Thu, 26 Jun 2008 00:51:09 -0700
On Jun 26, 2008, at 12:19 AM, Graham Cox wrote:
Why do you need to use tracking areas? I doubt that they are
designed to handle hundreds of small regions. If you are dragging
within the view, just hit-detect the rects yourself and mark them as
needing update. If you need that to happen with just the mouse
passing over the view (button not pressed) you can turn on
mouseMoved: events and do the same thing.
Tracking events are awkward at the best of times, and are mostly
intended for cursor management. I think you'd find a more
conventional approach a lot more fruitful.
Well, it certainly doesn't sound like that in the guide. There's no
indication whatsoever that tracking areas are meant for cursor
rectangle updates only, this is just one way to use them.
The documentation discourages using mouseMoved: events and encourages
use of tracking areas. I can also see why. If I do it using
mouseMoved: messages I basically have to do everything that tracking
areas provide manually. There is no reason why the system's
implementation should be any slower (it's exactly the same task). So,
following the documentation, I was convinced that that's the way to go.
It appears I stand corrected.
Regards
Markus
--
__________________________________________
Markus Spoettl
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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