That's what's nice about the tag being visible by default.
On 10/17/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> Yep, totally. Anyting you like. If a component should /not/ be
> attached to a certain tag, it should tell you so by throwing an
> exception. Some of the formcomponents do this.
>
>
Yep, totally. Anyting you like. If a component should /not/ be
attached to a certain tag, it should tell you so by throwing an
exception. Some of the formcomponents do this.
Eelco
On 10/17/05, Jason Essington <[EMAIL PROTECTED]> wrote:
> I had some markup that looked something like:
>
>
>
>
I had some markup that looked something like:
[myPanel]
[myOtherPanel]
I want to make some of the columns visible or not at runtime, so
rather than adding another wicket:id to the td tag, and adding my
panel to a WebMarkupContainer, I did something like:
[myPanel]
