What about the all other keys from the input map? There are a lot of them that we have not yet addressed. Many of them, we can skip in this presentation because their handling is very similar to what we have already seen. For example, the shift left arrow key, is mapped to the selectPreviousColumnExtendSelection action. This action can be defined with code similar to that for the selectPreviousColumn, action, but it will extend rather than change the selection. This could even be handled by the current code if another constructor argument is added indicating how the selection is to be handled.
Much more interesting are a set of keys that are handled correctly when the main table has focus, but are not handled correctly when the row header has focus. The page down and page up keys behave this way. When page up is pressed in the main table, both the main table and the row header shift. However, when the key is pressed in the row header, only the row header shifts, the main table stays in place. This is clearly not desirable behavior.