Greg Brown wrote: > I think it's probably tricky to implement in any framework because it > requires too many assumptions about what the "correct" behavior is. For > example, when you re-enable an ancestor, do you recursively re-enable all > child components? What about child components that were previously disabled? > For this reason, we decided to leave the implementation of this type of > functionality to the application developer. > > Which is why I'd like to see a setEnabledRecursive() method at Component level, so that sub-classes could override it and DTRT.
But there are always other hacks available, like using a transparent pane to temporarily block a group of components. Regards, Noel Grandin.
