On Jul 24, 2012, at 13:36 , Markus Spoettl wrote: > My view reacts to -mouseDragged: but doesn't check if there's been a > -mouseDown: first because that's implicit. Did that change?
The Cocoa Event Handling Guide says "Mouse events are dispatched by an NSWindow object to the NSView object over which the event occurred", so I guess there's a lag/race condition that's putting your view under the mouse pointer at the moment the event is generated. I think it's implicit that a mouseDown has occurred before a mouseDragged, but I don't see anything that guarantees they're sent to the same view. In that case, you should really set a state flag in mouseDown that's checked in mouseDragged. _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
