can we now deprecate protected boolean callOnBeforeRenderIfNotVisible() ??
because you could do it now in onConfigure right?
I hate multiply things do do the same thing :(
On Wed, Jul 21, 2010 at 07:05, Igor Vaynberg igor.vaynb...@gmail.com wrote:
protected boolean
its already deprecated
-igor
On Tue, Jul 20, 2010 at 11:46 PM, Johan Compagner jcompag...@gmail.com wrote:
can we now deprecate protected boolean callOnBeforeRenderIfNotVisible() ??
because you could do it now in onConfigure right?
I hate multiply things do do the same thing :(
On Wed,
very nice feature,
thank you !!
On Wed, Jul 21, 2010 at 10:35 AM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
another new callback added to 1.4/trunk that is aimed at making life
easier when managing component states such as visibility, enabled,
etc.
/**
* Called once per
Excellent!
Op 21-07-10 07:05, Igor Vaynberg wrote:
another new callback added to 1.4/trunk that is aimed at making life
easier when managing component states such as visibility, enabled,
etc.
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
another new callback added to 1.4/trunk that is aimed at making life
easier when managing component states such as visibility, enabled,
etc.
/**
* Called once per request on components before they are about to be
rendered. This method
* should be used to configure such
Igor,
Thanks for the new feature!
/**
* Called once per request on components before they are about to be
rendered. This method
* should be used to configure such things as visibility and enabled
flags.
* p
* Overrides must call {...@code
