On Mar 4, 2008, at 1:06 PM, Ben Trumbull wrote:
Bill,
On Mar 2, 2008, at 5:35 PM, Ben Trumbull wrote:
My question is, why would changing a property value cause another
property to have its retain count increase?
No idea. Why don't you run it in gdb and break on the -retain
method and ge
Bill,
On Mar 2, 2008, at 5:35 PM, Ben Trumbull wrote:
My question is, why would changing a property value cause another
property to have its retain count increase?
No idea. Why don't you run it in gdb and break on the -retain
method and get some stack traces ?
This works best if the cl
On Mar 2, 2008, at 5:35 PM, Ben Trumbull wrote:
My question is, why would changing a property value cause another
property to have its retain count increase?
No idea. Why don't you run it in gdb and break on the -retain
method and get some stack traces ?
This works best if the class you're d
My question is, why would changing a property value cause another
property to have its retain count increase?
No idea. Why don't you run it in gdb and break on the -retain method
and get some stack traces ?
This works best if the class you're debugging (in this case the value
window control
I have a Core Data app that has several entities. One entity, Window,
contains several properties such as openAtLaunch, windowName, and
wController. The wController attributes are Transformable, Optional
and Transient. The data are presented on a list, and when the user
double-clicks a r
