@Beta
public abstract class EffectorBody<T>
extends java.lang.Object
#main(ConfigBag) to do the work of the effector
See also EffectorTasks: possibly this will be deleted in preference for an approach based on EffectorTasks.
| Constructor and Description |
|---|
EffectorBody() |
| Modifier and Type | Method and Description |
|---|---|
abstract T |
call(ConfigBag parameters)
Does the work of the effector, either in place, or (better) by building up
subtasks, which can by added using
DynamicTasks methods
(and various convenience methods which do that automatically; see subclasses of EffectorBody
for more info on usage; or see DynamicSequentialTask for details of the threading model
by which added tasks are placed in a secondary thread) |
public abstract T call(ConfigBag parameters)
DynamicTasks methods
(and various convenience methods which do that automatically; see subclasses of EffectorBody
for more info on usage; or see DynamicSequentialTask for details of the threading model
by which added tasks are placed in a secondary thread)
The associated entity can be accessed through the entity() method.