I'm not sure if it's documented as such, but I *think* this is
expected behaviour. The reality is that the dragging is really
implemented by the underlying window (ultimately using Carbon) so if
the view has no reference to its window when the drag types are
registered, they probably just "get lost". A nib-instantiated window
won't have this problem as it's most likely built top down.
Generally it's probably wise to build structures completely (in this
case window+views) before trying to set up high-level behaviours on
them which probably do assume that things are fully constructed.
G.
On 7 May 2008, at 1:34 am, Michael Gardner wrote:
Upon further investigation, I've found that if I call -
registerForDraggedTypes: before adding the view to its parent window
with -setContentView:, I never get the -draggingEntered: messages.
If I do so afterwards, everything works properly. Is this expected
behavior?
_______________________________________________
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 [EMAIL PROTECTED]
