-
Enhancement
-
Resolution: Unresolved
-
P4
-
8u20
SelectionModel has two types of methods
- the basics: changing the selectionIndex to a specific index
- the sugar: navigate the selection, either relative to the focus/selectedIndex or to specific locations
the first type has two notions:
- "add" a selection: select
- "set" a selection: clearAndSelect
the second type only has the notion of "add".
Arguably the sugar adds value (or not) - but if it's there, it should have the same notions as the basic types, that is:
clearAndSelectXX with XX = Previous, Next, First, Last
Similar for basic methods in MultipleSelectionModel:
we have: selectRange, selectIndices
missing: clearAndSelectRange, clearAndSelectIndices
Having these (not only, but particularly in combination with RT-38509) will significantly cleanup the navigational code in yyBehaviour (with yy == List, Table, ...)
- the basics: changing the selectionIndex to a specific index
- the sugar: navigate the selection, either relative to the focus/selectedIndex or to specific locations
the first type has two notions:
- "add" a selection: select
- "set" a selection: clearAndSelect
the second type only has the notion of "add".
Arguably the sugar adds value (or not) - but if it's there, it should have the same notions as the basic types, that is:
clearAndSelectXX with XX = Previous, Next, First, Last
Similar for basic methods in MultipleSelectionModel:
we have: selectRange, selectIndices
missing: clearAndSelectRange, clearAndSelectIndices
Having these (not only, but particularly in combination with RT-38509) will significantly cleanup the navigational code in yyBehaviour (with yy == List, Table, ...)