On Tue, Jul 21, 2009 at 9:32 AM, Tim Schmidt<schmidt....@gmx.net> wrote: > Obviously CG's bitblock transfers access unallocated memory in this case.
No, it probably doesn't. Remember, 90% of the time, the bug is in your code. The other 10% of the time, the bug is in your code. > If > I accidently free said memory it completely eludes me where this might > happen (I am pretty confident I don't release any of my model/controller > objects unintentionally (I tried running with all the usual mallocdebug > options as well as NSZombies). Use Instruments. > Furthermore all NIBs are managed by > NSViewController subclasses. Can anybody point me to some advanced guides on > NSTableView (beyond the class reference and tables guide). There aren't any. It's not a hard class to work with. --Kyle Sluder _______________________________________________ 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
