OK. The window nil thing may have been a herring rouge thanks to the
debugger not showing values correctly <grr>.
However, the effect remains:
- I start the drag in the window/view
- Drag to the outside of the window
- Drag events are dispatched to the window, and always arrive in my
view (even when the mouse is outside the window)
- Drag back into the bounds of the window/view
- NSMouseEntered arrives in my event loop when I cross back over the
tracking area covering the view, but when dispatched to the window it
fails to arrive in my view
At this point I have no idea who is eating the mouse entered event -
i.e. where it goes after being dispatched to the window and which view
handles it (if any).
I could send events directly to the view concerned (probably), by
sending the events directly to mouseEntered:, mouseExited: etc. when
I'm in my drag loop.
However, I'm not sure if that would subvert any critical handling
elsewhere (is there any?).
_______________________________________________
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
