> TableViews don't support checked items. Ok, but we can put checkbox in a column and for me this is enough.
> 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. Ok. >> 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? For example here: http://www.computerhope.com/issues/ch000306.htm The first sample is <F1> on Windows that means "Help", etc ... But what I've written (and badly explained probably) was that when a function key is pressed, to ensure that Pivot can handle even combination of it and other modifiers, all here. > Again, the application is free to do this - but I don't think that it should > be encoded into the skin. I don't agree, but I respect your opinion. >> 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. :-) I understand, and me too :-) ... > There are not many use cases for "type over" behavior these days. Yes, i agree, and for me is enough to have written is some place (here) how this key is (not) handled. Thank you for your comments, Sandro
