[Wicket-user] .setVisble not working for webmarkupcontainer

2007-07-23 Thread atul
Hi, 1.I have a WebMarkupContainer with some components nested. I do setVisible(false) to it when page loadslater on an ajax request I try to do .setVisible(true) and repaint it adding it to AjaxRequestTarget IT DOES NOT SHOW UP Am I going wrong in something?

Re: [Wicket-user] .setVisble not working for webmarkupcontainer

2007-07-23 Thread Gerolf Seitz
iirc, you have to call .setOutputMarkupPlaceHolder(true) on the webmarkupcontainer to make this work. gerolf On 7/23/07, atul [EMAIL PROTECTED] wrote: Hi, 1.I have a WebMarkupContainer with some components nested. I do setVisible(false) to it when page loadslater on an ajax request I try

Re: [Wicket-user] .setVisble not working for webmarkupcontainer

2007-07-23 Thread Christian Alejandro Marquez Grabia
The problem is that you have hidden the container in which the components were placed, and later when wicket attempts to add the components, it can't find the place where to. As Dipu says, you must modify the visibility of the inner components, not the container, so when wicket attempts to add

Re: [Wicket-user] .setVisble not working for webmarkupcontainer

2007-07-23 Thread Eelco Hillenius
On 7/23/07, Christian Alejandro Marquez Grabia [EMAIL PROTECTED] wrote: The problem is that you have hidden the container in which the components were placed, and later when wicket attempts to add the components, it can't find the place where to. As Dipu says, you must modify the visibility

Re: [Wicket-user] .setVisble not working for webmarkupcontainer

2007-07-23 Thread Igor Vaynberg
On 7/23/07, Eelco Hillenius [EMAIL PROTECTED] wrote: On 7/23/07, Christian Alejandro Marquez Grabia [EMAIL PROTECTED] wrote: The problem is that you have hidden the container in which the components were placed, and later when wicket attempts to add the components, it can't find the