The cell consumes the event loop and dispatches events. Look at the
code via http://developer.apple.com/samplecode/PhotoSearch/listing9.html
ie:
if ([theEvent type] == NSMouseEntered || [theEvent type] ==
NSMouseExited) { [NSApp sendEvent:theEvent]; }
But do please log a bug; at worst, we c
Hi Corbin. Thanks for the note.
Well, the trouble is, if you are consuming the event loop, then you
need to dispatch things.
Have you seen: http://developer.apple.com/samplecode/PhotoSearch/
?
Yes, I studied this before I started and used the patterns in there.
The cell consumes the even
On Feb 4, 2009, at 5:51 PM, Luke Evans wrote:
OK, FWIW for the record here is the resolution I've arrived at:
mouseEntered and mouseExited events from tracking areas that are
active when mouse dragging begins are dysfunctional in the drag,
specifically when autoscrolling at the boundaries
OK, FWIW for the record here is the resolution I've arrived at:
mouseEntered and mouseExited events from tracking areas that are
active when mouse dragging begins are dysfunctional in the drag,
specifically when autoscrolling at the boundaries of the cliprect. I
have a drag event loop per
