Hello,
I'm going to customize a "bit" the MouseBehavior (and subclasses)
utility class for my purposes.
I was wondering why two modes have been implemented to listen to mouse
events.
One is based on WakeupOnAWTEvent, native in the Behavior mechanism,
the second is based on the MouseBehavior class implementing the
MousListener and MouseMotionListener interfaces and using the AWT event
mechanism.
The only difference I see is the possibility one has whether to specify
or not a particular listening component.
Are there other "deep" implications? Differences in performances?
Reliability? Memory usage?
Why was the AWT event/listener mechanism support introduced?
If there aren't particular reasons, I can then erase some more code for
my needs.
thanks,
Fabrizio NUNNARI
--
Fabrizio Nunnari (nunnarif at di.unito.it)
PhD Student - Computer Science Department - Torino - Italy
http://www.di.unito.it/~nunnarif/
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
