Hi to all, > Right. Arguably, pivot.util.ListenerList could be using > WeakReferences, which would eliminate this problem (treeData would > never develop a string reference back to treeView). However, it would > also arguably hurt the performance of listener lists, which would be > unfortunate. That's assuming that weak references are slower than > strong references, which I thought I read somewhere... A stupid question, but have a default version like the current, and another using the right (but slower) approach ? Leaving to the user the choice ...
> Yeah, and we could add a similar interface. For all data driven > components to do that is a lot of overhead though for a corner-case > problem :) Same as over, leaving the corner-case as non-default ? Bye, Sandro
