Skip to content

Commit a7144dd

Browse files
authored
Merge pull request statecharts#57 from larvanitis/patch-1
Update automatic-transition.md
2 parents 0fe3764 + fdeb8b3 commit a7144dd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_glossary/automatic-transition.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Automatic transitions are [transitions](transition.html){:.glossary} that are tr
1818

1919
Automatic transitions don't have an associated [event](event.html){:.glossary}, as the mere being in the state implies that the transition should be taken.
2020

21-
Automatic transitions are usually [guarded](guard.html){:.glossary}. Such a guarded automatic transition is checked immediately after the state is entered. If the condition doesn't hold then the machine remains in the state, with this automatic transition in play _for as long as the state is active_. Every time the statechart handles an event, the guard condition for these automatic transitions are checked. If ever the guard condition ever succeeds, then the transition happens.
21+
Automatic transitions are usually [guarded](guard.html){:.glossary}. Such a guarded automatic transition is checked immediately after the state is entered. If the condition doesn't hold then the machine remains in the state, with this automatic transition in play _for as long as the state is active_. Every time the statechart handles an event, the guard condition for these automatic transitions are checked. If the guard condition ever succeeds, then the transition happens.
2222

2323
If there are many automatic transitions in play, they are all checked. In some statechart systems, only one guard is allowed to be true at any point in time; in others, the transitions are ordered, and the guards are checked until a one of them succeeds.
2424

0 commit comments

Comments
 (0)