Yes but ... isVisible may be triggered several times, while setVisible should only be called once (say if I do it only once after creating the component). Usually I prefer the state driven way, but what if the logic has a lot of overhead?
Jonathan Locke wrote: > > > isVisible is generally better imo because it is state driven. if you push > instead of pull, the state can get stale. > > ----- Eyal Golan [EMAIL PROTECTED] Visit: http://jvdrums.sourceforge.net/ http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74 http://www.linkedin.com/in/egolan74 -- View this message in context: http://www.nabble.com/isVisible-vs.-setVisible-tp17860615p17860930.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
