Re: Ordered to-many relationship CoreDataGeneratedAccessors

2014-03-31 Thread Fritz Anderson
On 29 Mar 2014, at 3:11 AM, Rick Mann rm...@latencyzero.com wrote: I'm getting -[WireSegment replaceObjectInNodesAtIndex:withObject:]: unrecognized selector sent to instance When I try to send that message. This is one of the CoreDataGeneratedAccessors, for an ordered to-many

Re: Ordered to-many relationship CoreDataGeneratedAccessors

2014-03-31 Thread Gordon Apple
: Fritz Anderson fri...@manoverboard.org To: Rick Mann rm...@latencyzero.com Cc: Cocoa dev cocoa-dev@lists.apple.com Subject: Re: Ordered to-many relationship CoreDataGeneratedAccessors Message-ID: ccc92aa3-1729-48b6-bfeb-5bcc878a6...@manoverboard.org Content-Type: text/plain; charset=windows-1252 On 29

Re: Ordered to-many relationship CoreDataGeneratedAccessors

2014-03-31 Thread Rick Mann
From: Fritz Anderson fri...@manoverboard.org To: Rick Mann rm...@latencyzero.com Cc: Cocoa dev cocoa-dev@lists.apple.com Subject: Re: Ordered to-many relationship CoreDataGeneratedAccessors Message-ID: ccc92aa3-1729-48b6-bfeb-5bcc878a6...@manoverboard.org Content-Type: text/plain; charset

Re: Ordered to-many relationship CoreDataGeneratedAccessors

2014-03-31 Thread Sean McBride
On Mon, 31 Mar 2014 17:05:30 -0600, Gordon Apple said: One thing you are missing, is that, as far as I know, the generated accessors are still broken. You have to write your own. I did find a set of macros someone wrote for this, but haven1t tried them yet because I had already written many of

Ordered to-many relationship CoreDataGeneratedAccessors

2014-03-29 Thread Rick Mann
I'm getting -[WireSegment replaceObjectInNodesAtIndex:withObject:]: unrecognized selector sent to instance When I try to send that message. This is one of the CoreDataGeneratedAccessors, for an ordered to-many relationship. I don't see anything in the docs about those. What am I missing?