Two things turn off slightly:
- setting the Popup component in a click is too late in the mouseEvents sequence (pop-ups usually start when clicked or released, which happen before clicking)
- the value is taken from the wrong cell: all coordinates in JTable are in the coordinate system, their conversion to view the coordinates will be completely disabled.
This suggests that getting the context associated with the cell is poorly supported. Often best (snippet below)
- override getPopupLocation (MouseEvent) and save the location somewhere
- implement a popup / action to access location
It doesn’t work (as it should be done in a well-organized application), the pop-up window may be caused by the keyboard: if this happens, you will need to provide some other marker (fi focused cell) in order to act.
final String popupLocation = "table.popupLocation"; final JTable table = new JXTable(new AncientSwingTeam()) { @Override public Point getPopupLocation(MouseEvent event) { // event may be null if triggered by keyboard, fi // thanks to @Mad for the heads up! ((JComponent) event.getComponent()).putClientProperty( popupLocation, event != null ? event.getPoint() : null); return super.getPopupLocation(event); } }; JPopupMenu popup = new JPopupMenu(); Action printLocation = new AbstractAction("print cell") { @Override public void actionPerformed(ActionEvent e) { Point p = (Point) table.getClientProperty(popupLocation); if (p != null) { // popup triggered by mouse int row = table.rowAtPoint(p); int column = table.columnAtPoint(p); LOG.info("" + table.getValueAt(row, column)); } else { // popup triggered otherwise // could choose fi by leadRow/ColumnSelection ... } } }; popup.add(printLocation); table.setComponentPopupMenu(popup);
Edit (caused by crazy comment):
You should check MouseEvent.isPopupTrigger as the trigger point is platform dependent. That means you need to control mousePressed, mouseReleased and mouseClicked
No, this is not necessary (just tested :-): the mechanism that shows componentPopup in response to mouseEvent - occurs in BasicLookAndFeel.AWTEventHelper - does this only if it is popupTrigger.
After reading the api doc (should have done yesterday ;-) again, it turns out that the method is always called before componentPopup is displayed, that is, also, if it is launched in other ways, the fi keyboard. In this case, the event parameter is null - and the source code will blow. On the bright side, with this guarantee, the entire logic of finding the target cell / s can be transferred to this method. They didn’t try, although perhaps this is not feasible (fi if then the location should be based on leadRow / ColumnSelection, which cannot be fully processed at this time)