> huh? that doesnt make any sense. the callbacks like onconfigure simply > give you checkpoints for calculating and caching visibility rather > then calculating every time.
I wasn't arguing against onConfigure (which is a fine trade-off) but saw an example of where relying on just setVisible would be problematic. Now the problem is that we have three ways of achieving the same thing. And yet another overridable method. It's probably too late in the game, but I would be more in favor of a delegation mechanism (e.g. interfaces for the functions of isVisible, isEnabled and whatever else makes sense) and a way to set those functions. So you'd do things more through composition. Might even consider making working with such functions a generic capability that also supports detaching (which then can also be used to let the component manage detachment of multiple models if there's more than one), etc. Would be a significant break though, so I'm not expecting a lot of cheering :-) Eelco
