> TreeSelectionListener is called with parameters of type
> Sequence<Integer>, which I wanted to loop over.
Yeah, having TreeView deal in iterable sequences would be handy. It
uses the Sequence.Tree static methods a lot, and some developers have
overlooked those methods since they're disconnected from TreeView --
so we might be able to kill two birds with one stone here. I can
introduce:
Sequence {
Tree {
public static class Path implements Sequence<Integer>,
Iterable<Integer>;
}
}
Then TreeView will deal in Path instances rather than Sequence
instances, and callers can iterate over them :)
-T
