OK, finally near the bottom of this problem.
It turned out that I had an override of -didTurnIntoFault in my tree item
entity. In there I was nil'ing out a couple of relationships (which are in
principle nil'ed out by the nullify delete rule) - I did this while trying to
track down some other d
On 14, Jan, 2013, at 03:31 PM, Jerry Krinock wrote:
>> Will -autorelease work with ARC?
>
> I don't think so. I didn't realize you were using ARC. I suppose you could
> opt out of ARC in your Method Replacement file, in order to compile that
> -autorelease.
>
>> Could you hint how to do th
> Will -autorelease work with ARC?
I don't think so. I didn't realize you were using ARC. I suppose you could
opt out of ARC in your Method Replacement file, in order to compile that
-autorelease.
> Could you hint how to do that? A category on NSTreeController?
I can't find the article on A
On Jan 13, 2013, at 9:32 PM, Jerry Krinock wrote:
>
> You've established previously that this is definitely a bug in Mac OS 10.6.
I'm not sure I had reached that decision. I have now been able to reproduce the
problem with a bare-bones core data document app. But still I wonder if it is
some
You've established previously that this is definitely a bug in Mac OS 10.6.
Your mission is to find a workaround.
On 2013 Jan 12, at 23:29, Martin Hewitson wrote:
> 2) Whenever I do [NSTreeController selectedObjects] I seem to end with an
> additional reference count. Is that expected?
If y
Now that I know how to get instruments to track retains and releases, I can see
what is happening to my entity. I'm still uncertain how to interpret the
results, but I see two strange things in the history of the object being
deleted:
1) It has a reference count of 3 after all the deletion stu
OK, I tried with the MOC's undoManager set to nil, but the problem persists.
Most annoying. I'll keep digging and post back if I discover anything.
Martin
On 10, Jan, 2013, at 06:46 PM, Peter wrote:
>
> Am 10.01.2013 um 18:38 schrieb Martin Hewitson:
>
>>
>> On 10, Jan, 2013, at 06:25 PM, P
Am 10.01.2013 um 18:38 schrieb Martin Hewitson:
>
> On 10, Jan, 2013, at 06:25 PM, Peter wrote:
>
>>
>> Am 10.01.2013 um 18:06 schrieb Martin Hewitson:
>>
>>> And I forgot to mention: the persistent store seems to get saved since when
>>> I restart the app (it's unusable after the CoreData
On 10, Jan, 2013, at 06:25 PM, Peter wrote:
>
> Am 10.01.2013 um 18:06 schrieb Martin Hewitson:
>
>> And I forgot to mention: the persistent store seems to get saved since when
>> I restart the app (it's unusable after the CoreData error) the removed
>> entities are not present. Curiouser an
Am 10.01.2013 um 18:06 schrieb Martin Hewitson:
> And I forgot to mention: the persistent store seems to get saved since when I
> restart the app (it's unusable after the CoreData error) the removed entities
> are not present. Curiouser and curiouser.
>
> Martin
>
>
>
> On 10, Jan, 2013, at
And I forgot to mention: the persistent store seems to get saved since when I
restart the app (it's unusable after the CoreData error) the removed entities
are not present. Curiouser and curiouser.
Martin
On 10, Jan, 2013, at 06:05 PM, Martin Hewitson
wrote:
>
> On 9, Jan, 2013, at 04:26
On 9, Jan, 2013, at 04:26 PM, Mike Abdullah wrote:
>
> On 8 Jan 2013, at 05:53, Martin Hewitson wrote:
>
>>
>> On Jan 7, 2013, at 08:44 PM, Mike Abdullah wrote:
>>
>>>
>>> On 7 Jan 2013, at 16:35, Martin Hewitson wrote:
>>>
Hi Francisco,
Thanks for the feedback!
>>>
On 8 Jan 2013, at 05:53, Martin Hewitson wrote:
>
> On Jan 7, 2013, at 08:44 PM, Mike Abdullah wrote:
>
>>
>> On 7 Jan 2013, at 16:35, Martin Hewitson wrote:
>>
>>> Hi Francisco,
>>>
>>> Thanks for the feedback!
>>>
>>> What you suggest sounds like it might fix the problem, but I'm wonder
On Jan 7, 2013, at 08:44 PM, Mike Abdullah wrote:
>
> On 7 Jan 2013, at 16:35, Martin Hewitson wrote:
>
>> Hi Francisco,
>>
>> Thanks for the feedback!
>>
>> What you suggest sounds like it might fix the problem, but I'm wondering how
>> best to do this. Currently I'm just calling -remove:
On 7 Jan 2013, at 16:35, Martin Hewitson wrote:
> Hi Francisco,
>
> Thanks for the feedback!
>
> What you suggest sounds like it might fix the problem, but I'm wondering how
> best to do this. Currently I'm just calling -remove: on the tree controller
> to delete the selected object(s). Of c
Hi Francisco,
Thanks for the feedback!
What you suggest sounds like it might fix the problem, but I'm wondering how
best to do this. Currently I'm just calling -remove: on the tree controller to
delete the selected object(s). Of course, if I clear the selection first, then
-remove: doesn't do
16 matches
Mail list logo
