Re: How to implement NSSplitViewDelegate methods in an NSSplitViewController subclass

2015-08-08 Thread Bill Cheeseman
> On Aug 8, 2015, at 9:31 AM, Mike Abdullah wrote: > > One thing you might want to watch out for that caught me out: > > Although NSSplitViewController is documented to be the split view’s delegate, > I found that — at least for controllers created in IB — that relationship > isn’t actually ho

Re: How to implement NSSplitViewDelegate methods in an NSSplitViewController subclass

2015-08-08 Thread Mike Abdullah
> On 8 Aug 2015, at 14:06, Bill Cheeseman wrote: > > I think you're right on both counts. > > I will post this weekend about my solution to the other problem I posted > about -- how to make collapse and uncollapse work both from a toggle button > and by double-clicking or dragging the divider

Re: How to implement NSSplitViewDelegate methods in an NSSplitViewController subclass

2015-08-08 Thread Bill Cheeseman
I think you're right on both counts. I will post this weekend about my solution to the other problem I posted about -- how to make collapse and uncollapse work both from a toggle button and by double-clicking or dragging the divider. It turns out that the frameworks use two different techniques

Re: How to implement NSSplitViewDelegate methods in an NSSplitViewController subclass

2015-08-07 Thread Fritz Anderson
Speculation: This may be like the -window property of NSWindowController. Accessing it is the recommended way to force the controller to instantiate the window, even if you don’t care about the result. In this case, _you_ may not care what super’s NSSplitViewDelegate methods do, but NSSplitView

Re: How to implement NSSplitViewDelegate methods in an NSSplitViewController subclass

2015-08-07 Thread Quincey Morris
On Aug 7, 2015, at 12:33 , Bill Cheeseman wrote: > > But by calling super the way I showed in my original post, I am not making > use of any result that might be returned by super's implementation of the > method. And how could super's implementation return anything meaningful to my > applicat

Re: How to implement NSSplitViewDelegate methods in an NSSplitViewController subclass

2015-08-07 Thread Bill Cheeseman
Thanks, that helps me to understand it a little better. But by calling super the way I showed in my original post, I am not making use of any result that might be returned by super's implementation of the method. And how could super's implementation return anything meaningful to my application a

Re: How to implement NSSplitViewDelegate methods in an NSSplitViewController subclass

2015-08-07 Thread Quincey Morris
On Aug 7, 2015, at 05:47 , Bill Cheeseman wrote: > > I don't understand why the fact that NSSplitViewController "implements" these > delegate methods requires my override to call super, or what calling super > accomplishes in this situation. According to the latest header files, setting a diff

How to implement NSSplitViewDelegate methods in an NSSplitViewController subclass

2015-08-07 Thread Bill Cheeseman
The header file comments in NSSplitViewController (introduced in OS X 10.10 Yosemite) state with respect to certain NSSplitViewDelegate methods that are "implemented" in NSSplitViewController that they "require a call to super if overriden [sic] by a subclass." How do I call super in an override