isVisible is generally better imo because it is state driven. if you push instead of pull, the state can get stale.
Eyal Golan wrote: > > This is a "Best Practice" question. > Suppose I have a component and I want to set its visibility according to > certain parameters. > Suppose I can do it by overriding the isVisible but I can also use the > setVisible after creating the constructor. > > Is there a preferable way? > Does it depend on the parameters I check? > > thanks > > -- > Eyal Golan > [EMAIL PROTECTED] > > Visit: http://jvdrums.sourceforge.net/ > LinkedIn: http://www.linkedin.com/in/egolan74 > > -- View this message in context: http://www.nabble.com/isVisible-vs.-setVisible-tp17860615p17860647.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]
