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 they are selected (only one at a time). The objects contain a path which is drawn and used for hit detection and dragging. Drag actions incur in changes in the object's associated data. 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 ACCESS only happens after my code yelds control to system code. So I figured I mut be somehow misusing some NS classes...
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
