On Thu, Aug 23, 2012 at 3:45 PM, Roger L. Whitcomb <[email protected]> wrote: > So, what you would like is for TreeView / TerraTreeViewSkin to keep track of > the node enable/disable state and so instead of the application implementing > a disabledNodeFilter the app would traverse the nodes on its own and call > setNodeEnabled() on each and have TreeView keep (duplicate) track of the > state? >
Yes, you got it. The TreeView would need to track disabled nodes(and the apps will track them internally too). I think a new field in NodeInfo(?) or whichever object that maintains the state. I think I saw some bit-flag(in TerraTreeSkin) somewhere. But I don't know if it can be of help. The apps will any way create their own Object and stash it using setUserData. And in response to some external event (link to the host is down or host is unreachable), the app can set it's internal field and then call disableMouse() or disableUI(). Hope this example helps. > Just trying to understand. > > And so what you're really asking for is a method in Component / ComponentSkin > to disable UI interaction on disabled components in general? > Sorry, I'm not an expert and so I don't know when you say ComponentSkin.But, yes some method to disable mouse events on a disabled node. > ~Roger thanks
