Thanks Quincey for your thoughts.
The evidence you've cited so far only points to the tracking area being in the "wrong" place, not necessarily to it being the wrong tracking area. I'm inclined to think that the misbehavior is an artifact of view coordinate systems.
Well, I'm pretty confident in saying that when mouse events are dispatched in my drag event loop after the autoscroll: (or scrollRectToVisible:) the tracking area is in the wrong place (or to put it another way, the 'wrong' tracking area is responding to the location of the mouse and generating the mouseEnter when the mouse returns to the clipview after leaving it (beginning the autoscroll).
Incidentally, I thought I saw that logging the NSTrackingArea instance when you've just created one, produces different output to logging the instance sent to you in a mouse event (i.e. the descriptions were different). I'm sure that's no more than a curiosity if I wasn't dreaming it, but it might be that the actual underlying objects are different.
More debugging of this one awaits me tomorrow... _______________________________________________ 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
