Jonathan Locke wrote:
i was originally hoping to avoid exposing that detail. you can visit child components with public final Object visitChildren(final Class c, final IVisitor visitor)
unfortunately, this recurses into subcontainers. we /could/ expose the iterator. or we could add a recurse boolean to visitChildren.
For the average Microsoft programmer this is not unfortunate, but a feature. On Windows (last time I programmed for that platform, which is a year ago using Borlands VCL) if you 'disable' a panel with (child) controls on it, the panel *and* it's children are disabled. IMNSHO this is the way UI programming should be done -> if you disable a parent control, the children should be disabled as well and vice versa, otherwise why do you have such a relationship. The same goes for all general control behavioural attributes ('read only' comes to mind). I think Swing has implemented this wrongly.
Martijn
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
