This appears to be happening because some view I'm using is posting a
notification saying that it needs to reset its cursor rects. When I
set a breakpoint on -[NSCursor set], I get this:
I think it'd be best if you just made your view change its cursor
rects while it is tracking. I'd expect your view to be called to reset
its cursor rects, too. Can't you just set a flag there and update your
own cursor rects as needed?
It's not my view that is the problem—my view is a simple subclass of
NSView that only overrides drawRect:, mouseDown:, mouseUp: and
mouseDragged:. In other words, no cursor rects at all.
It's some other standard OS view that is causing the trouble. I'm not
even sure which one because it's not really evident from the stack crawl.
To be clear, I've tried changing my code so that in mouseDragged:, I
only set my own view's frame and not any other view's frames. In this
case everything works fine. It's only when I start calling setFrame: on
other views that there is a problem.
_______________________________________________
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
