On Apr 1, 2011, at 9:49 AM, Carlos Eduardo Mello wrote:
> The objects in this array are the main thing in my app. Various parts of the
> UI direct actions to each one of them, when they are selected (only one at a
> time). The objects contain a path which is drawn and used for hit detection
> a
On Apr 1, 2011, at 9:49 AM, Carlos Eduardo Mello wrote:
> It all works fine most of the time, but every once in a while (can't figure
> out why...) the object seems to be "pulled from under my feet" and I get BAD
> ACCESS crashes in apparently random places. I tried to debug it but the BAD
> ACC
Thanks for the confirmation.
You can of course check that by logging the address of the object.
I wonder what you're observing that makes you think this is the
problem?
The objects in this array are the main thing in my app. Various parts
of the UI direct actions to each one of them, when
On Apr 1, 2011, at 9:29 AM, Carlos Eduardo Mello wrote:
> Hi people,
>
> I just realized I may be doing something dangerous with an NSMutableArray. I
> searched Guides and References on this but couldn't find an explicit answer:
>
> - Does an NSMutableArray guarantee to retain an object on addO
Hi people,
I just realized I may be doing something dangerous with an
NSMutableArray. I searched Guides and References on this but couldn't
find an explicit answer:
- Does an NSMutableArray guarantee to retain an object on addObject:?
- Does it ever make a copy of the original instead of re
