fsm:use_fsm
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
fsm:use_fsm [2007/04/29 14:15] – fgm | fsm:use_fsm [2007/12/22 14:45] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 26: | Line 26: | ||
Syntactic sugar: the idle() method is a shorthand for apply_events(fsm:: | Syntactic sugar: the idle() method is a shorthand for apply_events(fsm:: | ||
+ | |||
==== Filtering events ==== | ==== Filtering events ==== | ||
- | The OSInet FSM has three event processing modes, controlled by the " | + | The OSInet FSM has three event processing modes, controlled by the {get|set}_event_mode methods: |
* fsm:: | * fsm:: | ||
Line 36: | Line 37: | ||
* fsm:: | * fsm:: | ||
* Switching from fsm:: | * Switching from fsm:: | ||
+ | |||
Line 41: | Line 43: | ||
==== Disabling post-events actions ==== | ==== Disabling post-events actions ==== | ||
- | Firing of post-event actions is enabled by default, but can be disabled by setting the $action | + | Firing of post-event actions is enabled by default, but can be disabled by setting the $allow_actions |
In that case, applications can still decide to fire the event themselves by reading the fsm_action field in the fsm_result returns by fsm:: | In that case, applications can still decide to fire the event themselves by reading the fsm_action field in the fsm_result returns by fsm:: |
fsm/use_fsm.txt · Last modified: 2020/11/23 17:23 by 127.0.0.1