A rare case

This is one rare case where two interfaces are defined to match up with single event class:

• MouseListener interface
• MouseMotionListener interface

Probably done for efficiency purposes,

• because handling mouse motion events consumes lots of computer resources.