From 5fc9c62a6419893550987bbb8d62eb3a57f97579 Mon Sep 17 00:00:00 2001 From: Janne Valkealahti Date: Sat, 21 May 2016 14:09:31 +0100 Subject: [PATCH] Update docs - Notes for message passing #219 --- docs/src/reference/asciidoc/sm.adoc | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/src/reference/asciidoc/sm.adoc b/docs/src/reference/asciidoc/sm.adoc index b6fabc81..b4164191 100644 --- a/docs/src/reference/asciidoc/sm.adoc +++ b/docs/src/reference/asciidoc/sm.adoc @@ -826,6 +826,15 @@ with a custom event headers. This allows user to add arbitrary extra information with an event which is then visible to _StateContext_ when for example user is implementing actions. +[NOTE] +==== +Message headers are generally passed on until machine runs to +completion for a specific event. For example if an event is causing +transition into a state `A` which have an anonymous transition into a +state `B`, original event is available for actions or guards in state +`B`. +==== + === TimerTrigger _TimerTrigger_ is useful when something needs to be triggered automatically without any user interaction. `Trigger` is added to a