Hi Raffi,
Current implementation will buffer the AWT event when behavior
disable to prevent any loss of events. Behavior disable can only
disable behavior scheduler to run user processStimulus().
To workaround this, you may want ignore part of the event
in the first processStimulus call when behavior enable again.
Thanks.
- Kelvin
----------------
Java 3D Team
Sun Microsystems Inc.
>X-Unix-From: [EMAIL PROTECTED] Tue Jul 3 09:13:35 2001
>From: "Kasparian, Raffi J." <[EMAIL PROTECTED]>
>To: "Java 3D Beta Program (E-mail)" <[EMAIL PROTECTED]>, "Java3D Interest
Group (E-mail)" <[EMAIL PROTECTED]>
>Subject: Behavior processStimulus Bug
>Date: Tue, 3 Jul 2001 12:13:04 -0400
>MIME-Version: 1.0
>
>Attached is a program that demonstrates what I think is a bug with
>Behavior.processStimulus( Enumeration criteria ). When the program disables
>the behavior and then enables it, "criteria" includes events that occurred
>when the behavior was disabled. Surely this is not the intended behavior.
>
>To use the program, click on the Canvas3D. System.out prints the number of
>MouseEvents "criteria" contains. (Should be "1"). Now click the "Toggle"
>button. This will toggle the behaviors enabled state. Click a few times on
>the screen. System.out prints nothing (because the behavior is disabled).
>Now click the "Toggle" button again and click once on the screen. System.out
>prints the total number of clicks that occurred when the behavior was
>disabled plus the most recent click.
>
>Has anyone else experienced this problem. Does anyone have a good
>work-around?
>
>Thanks,
>
>Raffi
>
> <<BugTest.java>>
===========================================================================
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".
