Ah, so when it says "the method must derive the reference object from the
managed object’s values" it is talking about the managed object's persisted
values. So I could get rid of my extra attribute in my managed object class and
just set my UUID using a method similar to what you define below,
On Apr 3, 2010, at 9:44 PM, Gideon King wrote:
> Excellent, thanks for that. I thought that once a managed object ID had been
> assigned, that newReferenceObjectForManagedObject: should always return the
> same value, so I was regenerating it from the previous data instead of
> generating a ne
Excellent, thanks for that. I thought that once a managed object ID had been
assigned, that newReferenceObjectForManagedObject: should always return the
same value, so I was regenerating it from the previous data instead of
generating a new one if it either had a temporary object id or no object
On Apr 3, 2010, at 6:25 PM, Gideon King wrote:
> Phew, that's a relief. I'll look forward to hearing what I'm doing wrong in
> my sample project then.
>
> Regards
>
> Gideon
>
> On 04/04/2010, at 11:22 AM, Ben Trumbull wrote:
>
>>
>> On Apr 3, 2010, at 5:07 PM, Gideon King wrote:
>>
>>> W
Phew, that's a relief. I'll look forward to hearing what I'm doing wrong in my
sample project then.
Regards
Gideon
On 04/04/2010, at 11:22 AM, Ben Trumbull wrote:
>
> On Apr 3, 2010, at 5:07 PM, Gideon King wrote:
>
>> Wow, this is huge! Obviously the user doesn't expect the document to
>>
On Apr 3, 2010, at 5:07 PM, Gideon King wrote:
> Wow, this is huge! Obviously the user doesn't expect the document to
> disappear and a new one open up just because they did a Save As operation
I have I'm afraid led you astray. The invalidated objects are not coming from
the Save As operation
Wow, this is huge! Obviously the user doesn't expect the document to disappear
and a new one open up just because they did a Save As operation, so I would
have to go through every single part of the application, work out every
reference to a managed object, and either throw them away or fetch ne
On Apr 3, 2010, at 12:05, Ben Trumbull wrote:
> The canonical solution is to tell your controller objects like
> NSArrayController to refetch from the new document. It sounds like you're
> fighting the document based Save As behavior. It's "close the existing
> document, save the current sta
> When I create a document, save it, then save as, then save as again, it
> duplicates the persistent store, so the managed objects I have been using in
> my application are all invalidated.
>
> Now there are a whole lot of places in my application where I have KVO set up
> on properties of th
When I create a document, save it, then save as, then save as again, it
duplicates the persistent store, so the managed objects I have been using in my
application are all invalidated.
Now there are a whole lot of places in my application where I have KVO set up
on properties of the managed ob
10 matches
Mail list logo
