Uli's Web Site
[ Zathras.de - Uli's Web Site ]
Other Sites: Stories
Abi 2000
Stargate: Resurgence
Lost? Site Map!
     home | blog | moose | programming | articles >> blog

 Blog Topics

15 Most Recent [RSS]

 Less work through Xcode and shell scripts
2011-12-16 @600
 iTunesCantComplain released
2011-10-28 @954
 Dennis Ritchie deceased
2011-10-13 @359
 Thank you, Steve.
2011-10-06 @374
 Cocoa Text System everywhere...
2011-03-27 @788
 Blog migration
2011-01-29 @520
 All you need to know about the Mac keyboard
2010-08-09 @488
 Review: Sherlock
2010-07-31 @978
 Playing with Objective C on Debian
2010-05-08 @456
 Fruit vs. Obst
2010-05-08 @439
 Mixed-language ambiguity
2010-04-15 @994
 Uli's 12:07 AM Law
2010-04-12 @881
 Uli's 1:24 AM Law
2010-04-12 @874
 Uli's 6:28 AM Law
2010-04-12 @869
 Uli's 3:57 PM Law
2010-04-12 @867


Tied up in Bindings

I just spent about an hour tracking down a memory leak in my application, just to find the culprit was my use of Cocoa Bindings. I had hooked up a simple text field to an NSString instance variable.

In my case, the target was File's Owner in my NIB file. Since bindings apparently retain the object to which they are hooked up, the File's owner was waiting for the text field to release it, while the text field would not release its bound target until the File's Owner released it.

Delegates are, by convention not retained by the object delegating to them. So whose nutty idea was it to make bindings retain their targets???

Is it me, or does anybody else get the impression that bindings are a really sucky implementation of a concept that sounded jolly good on paper ... ?

Created: 2004-12-09 @524 Last change: 2004-12-09 @528 | Home | Admin | Edit
© Copyright 2003-2023 by M. Uli Kusterer, all rights reserved.