> Well, in the past, the "canned" answer was "override > isEnabled/isVisible." Changing that paradigm and doing a complete 180 > is troubling.
I don't think that's the case though. We've had many discussions on this list (and in private even), and we've always felt uneasy about supporting two rather than one way of achieving the same thing. Ultimately we decided to support both, but there have been several times where we were near making isVisible final. Eelco
