>Date: Wed, 1 Nov 2000 11:31:41 -0800
>From: Kelvin Chung <[EMAIL PROTECTED]>
>
>>Date: Wed, 1 Nov 2000 11:53:15 -0500
>>From: Fred Klingener <[EMAIL PROTECTED]>
>>Subject: Re: [JAVA3D] Consistent rendering timing concurrent with
>complexcalculation.
>>To: [EMAIL PROTECTED]
>>
>>> Because Java3D guarantees that rendering is halted during
>>> execution of a behavior's processStimulus() method we can
>>> guarantee that (a) the computation thread gets put in the run
>>> queue next and (b) that the rendering thread waits until it is
>>> signalled that computation has completed before rendering
>>> a new frame.
>>
>>I wonder. Does this mean that rendering waits until _all_ Behaviors
>>triggered by a PostID from a processStimulus() run to completion? Does
>>anyone know?
>>
>
>In current implementaton (v1.2), rendering thread and behavior thread
>can run concurrently.
>
>- Kelvin
This is correct, but may be a little misleading. The behavior
scheduler and, thus, a Behavior's processStimulus method, does run
concurrently with the renderer. However, a new frame will not start
until both the renderer (i.e., the previous frame) and the behavior
scheduler are done. In subsequent versions we may change that, except
that we will always make the guarantee that all behaviors with a wakeup
condition of "WakeupOnElapsedFrame" will be executed before the next
frame starts rendering.
--
Kevin Rushforth
Java 3D Team
Sun Microsystems
[EMAIL PROTECTED]
===========================================================================
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".
