What is the benfit of disabling tree selection? How will this effect keyboard navigation?
It sounds like you present some options/actions for the selected item in a tree, why not just disable these actions. e.g. you can select this item, but then all of the buttons/menus become disabled. Then you could add an arbitrary attribute to the item and test for that (and perhaps add a different decorator/css style). Maybe take a step back and describe the GUI behaviour you want (provide functionality X for some subset of a tree of objects) rather than your proposed solution (disable some of the elements in the tree). Adam On 02/02/06, HJ <[EMAIL PROTECTED]> wrote: > Eric H. Jung wrote: > > Why not hide the unrelated windows--what is wrong with that? > > Well, there are two reasons. The first one is that people get confused > when we hide windows, and the second is that the selected tree row jumps > up/down (depending on the z index) when other window are opened/closed. > > > If you must show them and can't disable them, how about breaking the UI > > into two trees, one for "related windows" and another for "unrelated > > windows"? You can disable the entire "unrelated windows" tree. > > I think that this approach will also confuse people. There simply has > to be a better/working way to get my idea going. > > Thanks, > /HJ > _______________________________________________ > Project_owners mailing list > [email protected] > http://mozdev.org/mailman/listinfo/project_owners > _______________________________________________ Project_owners mailing list [email protected] http://mozdev.org/mailman/listinfo/project_owners
