Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
macOS & iOS Developer Playground
macOS - Development and Darwin
Mimicing Interface Builder behavior
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="themabbit" data-source="post: 45432"><p>Hello all. I am trying to mimic the behavior of IB for an application I am writing. More specifically I have a palette panel with a toolbar and dragable images in the content view of the panel. I want to be able to drag the data that the images represent to an NSOutlineView in the main application window. I don't know if this matters but the two windows are in separate NIBs. Anyway I wan't the NSOutlineView to conform to the NSDraggingDestination protocol but I am trying to avoid subclassing NSOutlineView. I can get a handle via interface builder to the NSOutlineView object and register it for the correct data types but the NSDraggingDestination messages are swallowed by the view class (im assuming) and never make it to my delegate. Can I add a category to NSOutlineView and reimplement the NSDraggingDestination methods to get around this?, or should I subclass?, or is their a simpler method that I missing. Any help is greatly appreciated.</p><p></p><p>Thanks a bunch</p></blockquote><p></p>
[QUOTE="themabbit, post: 45432"] Hello all. I am trying to mimic the behavior of IB for an application I am writing. More specifically I have a palette panel with a toolbar and dragable images in the content view of the panel. I want to be able to drag the data that the images represent to an NSOutlineView in the main application window. I don't know if this matters but the two windows are in separate NIBs. Anyway I wan't the NSOutlineView to conform to the NSDraggingDestination protocol but I am trying to avoid subclassing NSOutlineView. I can get a handle via interface builder to the NSOutlineView object and register it for the correct data types but the NSDraggingDestination messages are swallowed by the view class (im assuming) and never make it to my delegate. Can I add a category to NSOutlineView and reimplement the NSDraggingDestination methods to get around this?, or should I subclass?, or is their a simpler method that I missing. Any help is greatly appreciated. Thanks a bunch [/QUOTE]
Verification
Post reply
Forums
macOS & iOS Developer Playground
macOS - Development and Darwin
Mimicing Interface Builder behavior
Top