Clarification on defining component visibility

2011-11-11 Thread Adam Gray
Recently some co-workers and I started questioning what is the (most) correct method for determining component visibility. In the past we've gone from calling setVisible() to overriding isVisible() and now are finding some people pointed to using setVisibilityAllowed() in onBeforeRender while

Re: Clarification on defining component visibility

2011-11-11 Thread Adam Gray
And, as usual, twitter ends up being faster. Thanks Igor. 8) Answer: none of the above (below?). Call override onConfigure() and call setVisible() from there. On Nov 11, 2011, at 4:14 PM, Adam Gray wrote: Recently some co-workers and I started questioning what is the (most) correct method

Re: Clarification on defining component visibility

2011-11-11 Thread vineet semwal
setvisible(boolean) inside onconfigure() On Sat, Nov 12, 2011 at 2:44 AM, Adam Gray adam.j.g...@gmail.com wrote: Recently some co-workers and I started questioning what is the (most) correct method for determining component visibility.  In the past we've gone from calling setVisible() to

Re: Clarification on defining component visibility

2011-11-11 Thread Igor Vaynberg
if the component itself controls its own visibility the best way is to override onConfigure() and call setVisible() inside if an outside component controls another's visibility the best way is to override the controlling component's onconfigure() and call controlled.setVisible() if you have a