Hi Andreas,
> can anyone explain the difference between
> WakeupOnActivation or WakeupOnViewPlatformEntry
There is not much info about that, but from the JavaDocs one can
see:
WakeupOn(De)Activation works against the scheduling bounds of the
behavior itself
wheras
WakeupOnViewPlatformEntry(Exit) works against another arbitrary
bounds object, given in the constructor to the Wakeup...
Also, the latter have a method getTriggeringViewPlatform(), which
might come in handy with multiple ViewPlatforms.
So, the latter have 2 conditions to be triggered:
- the behaviors scheduling region must be in activation volume of
a VP to become candidate for Wakeup
- the given bounds must firstly/lastly intersect with the VP's
activation volume
> and what is best used ?
As usual, this depends on what you want to do. Simple resource
preparation/cleanup should work easily with (De)Activation.
Besides, one open question (for me) is, what happens, when the
arbitrary bounds is not fully contained in the behavior scheduling
bounds as in this ASCII art (top view with BoundingBoxes):
Behavior scheduling bounds
|
| Wakeup bounds
| |
| v
| +-----------+
v | |
+-------------+ |
| | | |
| | | |
| | | |
| | | |
| +--------|--+
| |
| |
| |
+-------------+
When the VP approaches from south, intersects Wakeup bounds and
then disappears again to the south, a pair of Wakeup...Entry/Exit
events should correctly be generarted. When the VP instead
approaches from the north and disappears to the north, NOTHING
should be triggered: when the VP starts/ends to intersect the
Wakeup bounds, the Behavior isn't candidate for Wakeup.
What, when the VP approaches from south and diappears to the north?
We are left with an Entry event without a corresponding Exit
event!?? And, might be worse when VP comes from the north through
to the south, where you only get a single Exit event.
So I think, one should avoid intersecting Wakeup and Behavior
bounds.
regards
Georg
___ ___
| + | |__ Georg Rehfeld Woltmanstr. 12 20097 Hamburg
|_|_\ |___ [EMAIL PROTECTED] +49 (40) 23 53 27 10
===========================================================================
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".
