Hmm, haven't tried that. That might work - sometimes you just don't check all the methods thoroughly enough.. :)
Benjamin Ernst wrote: > > Hi, > > what about setVisible(false)? > > - Benjamin > > > 2007/12/18, wfaler <[EMAIL PROTECTED]>: >> >> >> Hi, >> I basically want to add a single component onto a page optionally, >> dependent >> on other data/state in a page. >> >> So far I have done this by using a ListView, and passing an empty List >> into >> it if the component is not to be displayed. >> However, I feel this is a bit heavy handed, is there any other way of >> achieving the same result? >> >> (I find ListViews to be brilliant when actually iterating through things, >> but for just a single optional component it feels like overkill). >> -- >> View this message in context: >> http://www.nabble.com/Ways-of-making-components-in-a-page-optional--tp14399390p14399390.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] >> >> > > -- View this message in context: http://www.nabble.com/Ways-of-making-components-in-a-page-optional--tp14399390p14400885.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]
