Re: Copy and Paste of rows in a NSTableView
Re: Copy and Paste of rows in a NSTableView
- Subject: Re: Copy and Paste of rows in a NSTableView
- From: Luke Adamson <email@hidden>
- Date: Tue, 12 Jun 2001 21:11:22 -0700
Ah. Yeah, this exposes what I consider to be a minor deficiency in the
responder chain mechanism. When you're using tab views, or any
configuration of swapped content views, you end up wanting the
controller for your active view to be in the responder chain. It
becomes especially troublesome when you need to do menu validation based
on the active view and its associated controller.
The hack I've been using to combat this is to insert the controller for
the active view into the responder chain as the next responder of the
content view of the window. This is a little shifty, since controllers
generally aren't subclasses of NSResponder, and -setNextResponder:
expects just that, but it turns out that it works, and it makes things
look nice from the design standpoint.
Cocoa has some nice support for non-NSResponders in the responder chain
(main/key window delegate, document class, application delegate), but
the mechanism for configuring this needs to be made a little more
flexible for responder utopia, IMHO.
---
Luke
On Tuesday, June 12, 2001, at 02:35 AM, Stiphane Sudre wrote:
complex case here. The main controller is the controller of the window
and there are secondary controllers for multiple NSTabView contents.