Re: Cocoa Bindings master-detail interface with sets of data in the detail part
Re: Cocoa Bindings master-detail interface with sets of data in the detail part
- Subject: Re: Cocoa Bindings master-detail interface with sets of data in the detail part
- From: Paul Bruneau <email@hidden>
- Date: Thu, 16 Aug 2007 14:49:50 -0400
On Aug 16, 2007, at 2:14 PM, mmalc crawford wrote:
On Aug 16, 2007, at 10:28 AM, Paul Bruneau wrote:
I am nervous that I don't have a controller for operationTypes but
I don't think I could instantiate it in IB due to needing one for
each of my WorkCenter objects (rather than just a single
instance). Do I have to create a controller programatically for
each operationTypes array?
No -- you just need to create an array controller for the
operationTypes for the currently-selected WorkCenter...
OH!! That was an eye-opener!! Thank you!!! I've never absorbed this
from anything before.
But you got the employees from the Department object. The
employees table is a detail of the selected department.
I hate to differ, since I know that you are right and I am wrong,
but I can't see it. The department is not in a list from which one
can choose, it is set with each document, a single object.
... indeed, but the again the principle is the same. There's a
single *selection* in the object controller. In a similar way, you
can in IB instantiate a new array controller to manage a collection
of OperationType objects. The 'contentArray' comes from
[WorkCentersController].selection.operationTypes.
And just like that it works! You are awesome. So OK a new controller
that my code doesn't have to know about...hey just how many
controllers can a medium-size application expect to have?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden