🚀 go-pugleaf

Typically, you have an ActionListener that listens to a number of components
that generate ActionEvents.
getActionCommand() can then used to work out what component generated the
event

Unfortunately, if you use the JBuilder visual designer then an
actionlistener is created for every button that generates action events and
getActionCommand() becomes redundant.

Michael Nguyen wrote in message <3662EE39.91524673@home.com>...
>The swing components have actionCommand that can be retrieved via
>getActionCommand as
>in the example below.  When jButton is clicked, its event handler
>'actionPerformed'
>is called and I already know that jButton1 is clicked.  So when is
>getActionCommand
>needed ?  Thanks for the info.
>
>Michael,
>
>  void jButton1_actionPerformed (ActionEvent e)
>  {
>    System.out.println (e.getActionCommand ());
>  }
>
>