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
> >
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 visibi
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 the
Don't change the visibility of the container you are trying to repaint.
Instead try changing the visibility of the components nested inside the
container.
Hope that makes sense.
Regards
Dipu
On 7/23/07, atul <[EMAIL PROTECTED]> wrote:
>
> Hi,
> 1.I have a WebMarkupContainer with some componen
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
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?
___