P4
In both controls, TreeView and TableView (and I assume, ListView, but have not tested yet) items can be disabled independently of other items of the control itself. The general application-level idea of doing that is e. g. to indicate that some rows contain "invalid" data which cannot be processed further. This is a nice feature that other frameworks in fact are missing! :-)
Unfortunately the disabled state disallows to select items by mouse, while selection by keyboard is (correctly!) possible.
The is bad due to two reasons:
(1) People think that the mouse or application are broken, as keyboard is working well.
(2) Just because an item is disabled due to some kind of "invalid" backing data does not mean that nobody wants to move the selection to that item -- for example, in case the user wants to mark all "invalid" data as he wants to press the "delete" button after that...
Hence I want to propose that in a future release of JavaFX the fact that an item in all collection-typed controls can be selected by mouse just as it is by keyboard, even if the item is disabled. "Unklickable" in the sense of "won't fire action" must be something different than "Unselectable by mouse".
Unfortunately the disabled state disallows to select items by mouse, while selection by keyboard is (correctly!) possible.
The is bad due to two reasons:
(1) People think that the mouse or application are broken, as keyboard is working well.
(2) Just because an item is disabled due to some kind of "invalid" backing data does not mean that nobody wants to move the selection to that item -- for example, in case the user wants to mark all "invalid" data as he wants to press the "delete" button after that...
Hence I want to propose that in a future release of JavaFX the fact that an item in all collection-typed controls can be selected by mouse just as it is by keyboard, even if the item is disabled. "Unklickable" in the sense of "won't fire action" must be something different than "Unselectable by mouse".