> Hans, like Martin said, this doesn't work, and I already tried it. When
> you
> use those options, it just renders the element tag with no contents.
Yes, I realised that too. I am sorry if my answer caused you effort.
> Thank you very much, guys! When you come to Brazil, the beer is on me :)
Cool!
On Tue, Jan 8, 2013 at 2:54 PM, Carlson Weber wrote:
> Hans, like Martin said, this doesn't work, and I already tried it. When you
> use those options, it just renders the element tag with no contents.
> Martin, your solution is amazing. Simple and it just works. Thank you very
> much.
> Th
Hans, like Martin said, this doesn't work, and I already tried it. When you
use those options, it just renders the element tag with no contents.
Martin, your solution is amazing. Simple and it just works. Thank you very
much.
The solution was to and an AttributeModifier to the component and then I
On Mon, Jan 7, 2013 at 5:10 PM, Hans Lesmeister 2 <
hans.lesmeis...@lessy-software.de> wrote:
> Martin Grigorov-4 wrote
> > I.e. at the server side add "style='display:none'" to the Panel. Wicket
> JS
> > will replace
> > the old with the new one and then your fadeIn effect will show it.
>
> And w
Martin Grigorov-4 wrote
> I.e. at the server side add "style='display:none'" to the Panel. Wicket JS
> will replace
> the old with the new one and then your fadeIn effect will show it.
And with:
panel.setVisible(false);
panel.setOutputMarkupPlaceholderTag(true);
the style-attribute is added for yo
Hi,
Your investigation is fully correct!
I think you can overcome this by adding an invisible panel. I.e. at the
server side add "style='display:none'" to the Panel. Wicket JS will replace
the old with the new one and then your fadeIn effect will show it.
On Mon, Jan 7, 2013 at 3:01 PM, Carlson
