Well..
public class MyCentrallyEnabledPage/Panel xxx {
private boolean centralEnable;
CentrallyEnabledTextField extends TextField {
....
isEnabled() {
return centralEnable;
}
}
I think you get the idea. It can be an inner class or any kind of
class (just needs the necessary built-in handle).
**
Martin
2009/7/19 slowery23 <[email protected]>:
>
> can u give an code example of what your "centrallyenableddisabledcomponent"
> looks like?
>
>
> MartinM wrote:
>>
>>> That certainly will work. But if I have a form and I want to disable all
>>> of
>>> the elements in the form except for the "Edit Form" link, it is, IMO,
>>> much
>>> simpler to disable the form and override the one link so it is enabled,
>>> rather than disabling many form components.
>>
>> You can just make your own "centrallyenableddisabledcomponent". That's
>> what we did and works great.
>>
>> **
>> Martin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/override-isEnabledInHierarchy--tp24535687p24559838.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
