Of course, this is what the button does (in my opinion). It processes a MouseEvent and creates (dispatches) an ActionEvent .
Event events are semantic events - as a signal that a certain button (widget!) Has been pressed. The trigger for this action can be a mouse event ("the left button was pressed and released when the mouse cursor was in the rectangle defined by the AWT button widgets") or a keyboard event ("Space was pressed and released while the main focus was on the AWT widget" Button ").
I think you are not looking at technical conversion. In practice, you will have to listen to mouse events and trigger new actions for your action listeners.
Andreas_D
source share