• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: MVC paradigm: multiple controllers?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MVC paradigm: multiple controllers?


  • Subject: Re: MVC paradigm: multiple controllers?
  • From: Scott Stevenson <email@hidden>
  • Date: Tue, 5 Oct 2004 14:23:09 -0700


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]

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
References: 
 >MVC paradigm: multiple controllers? (From: Keith Blount <email@hidden>)
 >Re: MVC paradigm: multiple controllers? (From: J Tichenor <email@hidden>)

  • Prev by Date: Re: Binding/KVC : valueForKey: and NSDictionary (was: valid accessor for framework objects. (was: implicit and explicit invocation of description method))
  • Next by Date: Re: MVC paradigm: multiple controllers?
  • Previous by thread: Re: MVC paradigm: multiple controllers?
  • Next by thread: Re: MVC paradigm: multiple controllers?
  • Index(es):
    • Date
    • Thread