From: "Yazel, David J." <[EMAIL PROTECTED]>
Sent: Wednesday, October 04, 2000 9:09 AM
> ...The keybehavior I wrote uses a thread to compute new
> transformations. I capture key presses and post them to the thread object
> which monitors them to create a series of transformation transactions.
The
> thread wakes up frequently and applies all the appropriate changes based
on
> the current set of depressed keystrokes.
Dave,
Lately, I've been moving into wakeupOnElapsedTime() Behaviors repeating
functions that I used to do in threads. So far, I haven't been bitten, but
I wonder whether you have any feeling on whether and when this is a good
idea. I've stripped out the wakeupOnElapsedFrames(0) Behaviors, so my scene
progresses at the wuOET() periodicity anyway.
I can't really articulate a motivation to do it that way. My code just
'feels' better there on the scene graph. Do you spawn threads in Behaviors?
Your method of handling the the view and content transformations in a queue
is pretty heroic.
Fred Klingener
===========================================================================
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".
