Problem in cell selection in JTable Java Swing

Question

hii
I am using JTable that shows data from database. I have developed one functionality. I change one cell value and then select multiple cell. If I press F12 function key then it copies first selected value and past it to another selected cells. it is working properly but when I press F12 it sets the last selected cell in editable mode. I want that all cell which has been pasted should be selected (with default blue colour not in editing mode). I am using ListSelectionListener for JTable Cell Selection and KeyListener for F12 functionality.
Please give some solution
I can not override editCellAt Method because i have already extended JFrame. and i tried to do this with Jtable.getSelectedColumn and getSelectedRow it is displaying the same value, by this how can I get the particular area of selection means Row nd Column Selected.
How would I know the current selection when user selects more than one cell???
Thanks
Edited by: 850979 on 11-Apr-2011 02:13
Edited by: 850979 on 11-Apr-2011 03:59

Answer 1

camickr wrote:
Presumably, JTable installs an action for the F12 key that results in starting editing the last selected cell.
There are no bindings for F12. See the [url http://www.camick.com/java/blog.html?name=key-bindings]Key Bindings listing. (...)
Right.
Of course it doesn't make sense that a F? key should invoke the editorI thought he meant F2 ("edit" on Windows), so that sounded natural.
All KeyEvents are passed to the editor for the cell and the editor is psuedo invoked. That is, the caret is not placed on the text field used as the editor, but the character typed is added to the editor. You can then either use tab/enter to save the text or use the escape key to cancel the editing.Thanks for the explanation. I had never noticed (I kept on double-clicking my JTable cells when I wanted to edit them! :o)
Of course it doesn't make sense that a F? key should invoke the editor, but this is a by product of all KeyEvents being forwarded so you don't have to have special Key Bindings for every character.You're right - as always.
They (Sun) could have filtered out some of the keys such as those, though, because as noted by the OP the current behavior is unintuitive.
To better control when the cell is editable based on the KeyEvent you can override the table with code like <snipped>
As you suggested using a Key Binding will prevent this behaviour as well (but only for that key).Right again, but in this specific case that is acceptable (the developer wants to attach a specific behavior to a specific key only).
OP here is an SSCCE of that second approach:
public class TestKeyBindingsOnJTable {
    public static void main(String... args) {
        final DefaultTableModel dtm = new DefaultTableModel(new String[] {"A", "B"}, 0);
        dtm.addRow(new String[]{"A1", "B1"});
        dtm.addRow(new String[]{"A2", "B2"});
        dtm.addRow(new String[]{"A3", "B3"});
        JTable table = new JTable(dtm);
        table.getInputMap().put(KeyStroke.getKeyStroke(KeyEvent.VK_F12, 0), "clear");
        table.getActionMap().put("clear", new AbstractAction() {
            public void actionPerformed(ActionEvent e) {
                dtm.removeRow(0);
        JOptionPane.showMessageDialog(null, table);
}Edited by: jduprez on Apr 8, 2011 9:36 PM