>MIME-Version: 1.0
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
>X-Sender: [EMAIL PROTECTED]
>Date: Thu, 31 May 2001 17:48:37 +0200
>From: zero <[EMAIL PROTECTED]>
>Subject: [JAVA3D] WakeupAnd - strict or not
>To: [EMAIL PROTECTED]
>
>hi all,
>first thx for answering to all my question last time, saved me lot of work =)
>
>but again there's another question in my head:
>is WakeupAnd strict or not.
>
>becasue for implementing precise and effective intersection testing i wonder if
>taking up two WakeupOnCollsionEntry conditions - one with bounding and one with
geometry
>works how i want it to be..
>
>so if the first condition (Bounding check) fails, will the geomtry test
ignoered (not strict version)
>oer will it done.. ?
>
>greetings
>Michael Nischt
>
>
>p.s. with saying "NOT strict" i think of s.th. like that..
>False && x = False
>True && x = x
>in the first case x will never be tested..
>
Each wakeup condition in WakeupAnd/WakeupOr/WakeupAndOfOrs/
WakeupOrOfAnds are evaluate independently in Java3D.
When one of the wakeup condition satisify, it will tell
WakeupAnd (e.g.) to set the appropriate flag to
indicate one condition is satify. When all conditions
satify it call user processStimulus(). For WakeupOr,
as soon as one of the condition satifies it invoke
user processStimulus() immediately.
Returning to the questions.
cond1 && cond2
Event that tell cond1 or cond2 satisfy are come in
asynchronously. They are always false when start.
When cond2 set to true, it will "wait" until cond1
set to true before calling user processStimulus().
So I think the concept of "strict" did not apply
in WakeupAnd.
- Kelvin
---------------
Java 3D Team
Sun Microsystems Inc.
===========================================================================
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".
