I’m doing something vaguely similar to this using a subclass of
NSCollectionView, which sets up the collection view item differently
depending on some attribute of the represented object it’s operating
on. In this case, the class is just another attribute.
NSArrayController being in the controller layer of MVC, it doesn’t
care about the view, so it won’t be a problem for you.
Rob
On 9-Dec-08, at 2:24 PM, Todd Heberlein wrote:
Hi all,
I'm looking for documentation/tutorial/pointers on how to handle the
situation when an NSArrayController is managing an NSMutableArray
which will contain multiple types of objects but all of which have
the same base class. So the NSArrayController's "Object Controller"
"Class Name" is actually a base class.
Then when a user selects an item in the list, depending on the
subclass type a different view will be displayed, each with
different fields that will be views for the data in the subclass
instance.
Is this possible with controllers? Is it recommended/discouraged?
Any pointers?
Thanks,
Todd
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/rix.rob%40gmail.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
