> 4 - Yes, and why not also on TerraTableViewSkin ? TableViews don't support checked items.
>> What would be the use case? Checkboxes are often used as a more >> "user-friendly" alternative to multi-select lists - it is less common to see >> them combined. > I have many (web) applications where using checkboxes in a > multi-select List (or on a multi-select Table or Tree) are difficult > to handle (or the user interaction doesn't like them), so in these > cases a multi-selection clicking directly in the element is simpler, > also for users ... I'm not saying it's a best practice, but in many > cases could be less "confusing" for users, having less elements to > click. > So if it's not too complex I'd prefer to have also this. That's non-standard selection behavior - checked lists are a more elegant solution to this problem. However, this can be done at the application level if desired. > 7 - A last note, probably unnecessary, but just to remember it: > when should also verify to handle in the right way all function keys > (<F1> .. <F12>) standalone, or combined with other modifiers ... Can you provide some examples of non-application-specific behaviors associated with function keys? > 8 - And, important, on handling Home/End, Page Up/Down and > combinations with <Ctrl>, <Shift>, <Alt> discussed yesterday, how is > the sate of the art for Pivot 2.x ? > I'm thinking on changing selection using these combinations (if I > remember well yesterday Greg and Todd said that they prefer to change > the viewport but not the selection with them) ... but at least having > a dedicated style that enable this behavior ? Again, the application is free to do this - but I don't think that it should be encoded into the skin. > 9 - in Text components the key <Insert> is not handled (toggle on/off > the overwriting of next chars), open an issue ? > You can file a ticket for this but I can guarantee you that I will never personally implement this. :-) There are not many use cases for "type over" behavior these days.
