Re: MVC paradigm: multiple controllers?

FROM : Scott Stevenson
DATE : Tue Oct 05 23:23:09 2004

On Oct 2, 2004, at 10:19 PM, J Tichenor wrote:

> I am not using Bindings yet, and don't know whether one should give
> every table in one's interface it's own NSArrayController -- assume
> so, but again I'm just learning...


You need one NSArrayController for each particular array you're trying
to manage. It doesn't really matter how many views use the array
controller.

The only exception to that is if you *don't* want the selected
objects/rows in each view to stay in sync with each other.

    - Scott


--
http://treehouseideas.com/
http://theobroma.treehouseideas.com/ [blog]