Sounds logical. And i think you can do it yourself by checking the isEnabled and isEnableAllowed flags in onBeforeRender of MarkupContainers and then use a visitor to update all childs. Only problem i see is that changes made after the container has done this are not detected but the same is true (i think) if wicket were to do this in the render phase.
Maurice On Nov 15, 2007 12:06 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: > so if i disable a form then all textfields should be renderd with > disabled=disabled in there tag? > > johan > > > > > On Nov 13, 2007 4:54 PM, Maeder Thomas <[EMAIL PROTECTED]> wrote: > > > Hi folks, > > > > we're currently struggling with the case of a complex component tree > > (nested AJAX tabbed panels) which we would like to enable/disable in one > > go (i.e. disable every component below a given root). I've tried the > > approach where I call setEnabled(false) on every child of the root in > > onBeforeRender(), but this doesn't work, since we have AJAX elements > > below the root. > > > > I've found a conversation in the old wicket lists where somebody was > > asking why enablement was not determined recursively like visibility. > > I.e. a component is rendered as disabled if the enabled-flag is set on > > the component or if the component's parent is disabled. However, the > > thread just ended without any resolution. > > I currently see no way to implement our desired behaviour short of > > touching every input component in our component tree. On the other hand, > > I see no reason why wicket should not determine enablement recursively. > > > > thoughts? > > > > Thomas > > >
