Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Error with proxy objects and to-many relationships with Core Data



On 2/26/06, mmalcolm crawford <email@hidden> wrote:
>
>
> The method returns a *proxy*, not the actual object.  So you can't
> use it as an "ordinary" object.  If you need the actual object, use:
>
>         [[fooBarController selectedObjects] objectAtIndex:0];


Fails with the same error as before. Since I'm in an NSArrayController
object is there anything special I need to do to create the object? I've
tried using the [self newObject] method as well as the one described before.


If you find deficits in the documentation, please file enhancement
> requests.  Please also bear in mind that, as in this case, many
> "issues" with Core Data are not specific to Core Data...


I completely understand. I guess what I'm looking for really is something
like a core/data/bindings best practices. When you want to say use more than
1 nib and propigate one or more selected objects across that boundary, what
types of patterns or best practices are there. I'd love to see something
akin to the new Quartz book that just came out. I'd buy that in a heart
beat.

Thanks,
Sean
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden

This email sent to email@hidden

References: 
 >Error with proxy objects and to-many relationships with Core Data (From: "Sean Willson" <email@hidden>)
 >Re: Error with proxy objects and to-many relationships with Core Data (From: mmalcolm crawford <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.