This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
When handling low-level MouseEvents one can intercept double-clicks and prevent them from doing anything. But how can one do the same thing with higher-level ActionEvents? Multiple ActionEvents are generated with multiple clicks.
In case the answer is to take care of this by writing your own MouseEvent handlers to consume double-clicks, does one have to handle multiple-clicks in all methods of MouseListener?
Why don't you store the time, when your action listener code executes (by a call to System.currentTimeInMillis()). Each execution you check that the time is at least, say 500 milliseconds later than the last execution, and if not ignore the event.