> > > for visibility it is currently: isVisible()&&isRenderAllowed() which > makes little sense to me because i have to deal with two concepts: > visibility and rendering. from my point of view as a user i dont care > to know about rendering, i just want to plop my components down and > tweak their visibility.
so just introduce an extra final method on component that does just that check. when we first introduced this i argued to make isenabled() and > isvisible() include the is*allowed() checks, but i didnt win that one > back then...but thats another thread. no i still think thats a bad idea, because then isEnabled and isVisible must be both final i guess because then with simple isVisible override by some developer the security is by passed. johan
