I do understand perfectly well what is going on now. This solves
my problem because I've come to realize the top level objects
really RETAIN THE NIB OWNER. I had an extraneous retain count of
14, and 14 top level objects. Releasing all of these top level
objects put things back in balance.
I'm very surprised to hear that you can set up nib files that
retain the files owner. It sounds like a very dangerous thing for
Apple to allow for, as it would create retain cycles and memory
management mess.
It would be interesting to find out exactly what it is in your nib
file that's retaining the files owner. Shouldn't be so hard to
track down, as it's something you've got 14 copies of...
It surprised me too, as you can see by my astonishment and
confusion. It isn't my idea to set up nib files that retain the
file's owner, it's the way nib files work. It's in the
documentation, as I can now see after re-reading it with a clearer head.
I agree it sounds rather upside down, and I'd love to hear somebody
from Apple explain why it is that way.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
