Re: [Wicket-user] Redefining a child component/panel

[Jonathan Carlson]

I think I like your setVisible(boolean) option better, although the replace() method works great.  Options are good. >>> [EMAIL PROTECTED] 2005-02-09 12:29:01 PM >>> another better option might be to just hide/show two panels.  call setVisible(true) on the one you want showing and setVisible(false) on the other one. Jonathan Carlson wrote: > I have several self-links (see example below) that change the panel > being displayed, however I'm getting an error: A child component with > the name "xyz" already exists.  (Multiple pages is not really an > option for me, but I can explain why if you want to know) >  > new Link("someLink") > { >    public void linkClicked() >   { >     changePanel("xyz") >   } > } >  > Can someone either show me a better way to do it, or allow me to > remove the panel before replacing it with a different one?  (I noticed > the #removeAll method on Container, but didn't see a #remove("xyz") > method). >  > Thanks! >  > - Jonathan > > > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > > www.katun.com > ********************************************************************** ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user