> > The eventEnabled() method called by dispatchEvent() returns false
> > for any event id that it does not recognize (ie. any non-AWT event id), thus
> > preventing the event from being dispatched. However, custom components may
> > need to use event id values outside of the predefined AWT event ids, so as
> > not to be mistaken for an AWT event. These events will not be delivered
> > if dispatchEvent() is used to deliver the event, as is the case with the
> > new event queuing mechanism. This means that custom components can never
> > queue events.