There is no way to know how many AWT events may have been generated
between invocations of the behavior. So, Java 3D buffers up all AWT
events that the behavior is interested in, and gives them to the bahvior
as an array. In your case, you are only generating one event per
behavior invocation. If, for instance, you were tracking mouse movement
instead, you would most certainly get a bunch of events in one invocation.
We decided to use an array to pass as many events to the behavior as
possible.
Doug Twilleager
Sun Microsystems
>MIME-Version: 1.0
>Subject: [JAVA3D] Behavior trigger decoding
>To: [EMAIL PROTECTED]
>
>Good morning everyone.
>
>I need some guidence on how to decode the trigger in my behavior class.
>
>It triggers on AWTEvent, but gives an Array of AWTEvents, How do you get the
>values out of the array to determine what keys were hit ? And why is it an
>array ?
>
>My logic says :
> 1 key hit
> 1 behavior wakeup
> 1 AWTEvent
>
>Why the array ?
>
>Jannie
>
>===========================================================================
>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".
===========================================================================
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".
