> On 1 Feb 2015, at 5:23 am, Markus Spoettl <ms_li...@shiftoption.com> wrote: > > I did the same conversion a while back and have had no such issue. I found it > completely straight forward and surprisingly painless. Are you sure you're > implementing all the required protocols? > > + In the view starting dragging NSDraggingDestination (if it wants to receive > something, too), also are you calling -registeringForDraggedTypes: in that > view > + In you object you're calling "obj" NSPasteboardWriting > + In the object you're calling "source" NSDraggingSource > > In my implementation "obj" and "source" are the same object, but that should > not matter. Looking at my code, I think that's all the needs to be done. >
Hi Markus, Yes, I'm conforming to all the protocols, and I'm registering for the dragged types - actually that pertains to receiving only, but I can drag and receive the same types. Temporarily turning off the registering for dragged types (so that the same view won't immediately start responding to the drag it started) doesn't fix things, so that isn't a cause of what I'm seeing. It's most odd - nothing is logged that might give a clue. The legacy code still works perfectly. --Graham _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
