Travis,
Problem solved!
The collision detection "bug" was mine. I split the functionallity of the
CollisionDetector into a behavior which does "WakeupOnCollisionEntry" and
another one which does "WakeupOnCollisionExit" and in their
"processStimulus" methods I timestampt the corresponding events. Now I
consider that the object is colliding the hand iff the TimeStamp for the
Entry event is more recent than the TimeStamp for the Exit event. It
works fine.
I think the reason for the "bug" was that the Unified CollisionDetector
(copied from TickTockCollision) can only process either an Entry or
(exclusive or) an Exit event at a given time. Since the glove produces
events in a very rapid succession, sometimes one of the events would get
lost, since the CollisionDetector was not in the appropriate mode to
process it.
The "unified" CollisionDetector works just fine in the TickTockCollision
demo because the sequence of Entry-Exit events is well separated in time.
Anyway,... I thought this might be useful to other people as well...
If you are still interested on a copy of the application without the glove
I could send you one.
-------------------------------------------------------
Helmuth Trefftz
Rutgers University
e-mail: [EMAIL PROTECTED]
tel: (732) 445 0561 fax: (732) 445 4775
-------------------------------------------------------
=====================================================================
To subscribe/unsubscribe, send mail to [EMAIL PROTECTED]
Java 3D Home Page: http://java.sun.com/products/java-media/3D/
