Ah, wait a minute... we do check whether the form component itself is visible, but that component might have children that are visible. They should not be included in updating and validating, but they might in the current situation. Is that what you mean Johannes?

Eelco

Juergen Donnerstag wrote:

I thought we fixed that in HEAD. Which version are you using?

Juergen

On 7/13/05, Johannes Fahrenkrug <[EMAIL PROTECTED]> wrote:
Hi,

It seems that updateModel() is called for invisible child components.
This causes an exception in the attached use case.

An IMHO crude workaround is to make all children explicitly invisible
instead of just setting the invisible state on the parent. However, the
FormComponent.IVistor in Form#updateModels shouldn't visit children of
invisible components at all.

Regards,

Johannes







-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user



-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to