>But that's the point - how do I make an entire hierarchy of components >show that they are disabled.
The skins would need to be aware of the "blocked" state, and all ancestor skins would need to ensure that they repaint when their enabled states change. >It's quite a common requirement, and it's fairly tricky to implement >well in Swing because some of the composite components don't like me >calling setEnabled() on their children, so doing a straightforward >traversal of the tree is problematic. 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.
