Hi Quincey
> This is not a good approach to MVC programming. You're trying to take short
> cuts by updating your data model "by remote control" -- that is, by
> programming NSArrayControllers instead of your data model. That's a bit like
> trying to disassemble a precision watch using a crowbar and a hammer. :)
Heheh :-)
> Here's the rule of thumb I use: any line of code that refers to an array
> controller is a *last resort*, not a preferred solution, to be used only when
> there is no alternative.
How about, with a Core Data app, getting the content of an NSObjectController
after editing?
{
...
Customer *editedCustomer = [self.customerController content];
...
}
Joanna
--
Joanna Carter
Carter Consulting
_______________________________________________
Cocoa-dev mailing list ([email protected])
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]
