You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...when taking a transition from Action1 to Action2, the expected
exit set is [Action1]. However, getExitSet() returns an exit set that
includes Action1 in addition to allSibling* states (i.e. [Action1, Sibling1, Sibling2, ...]).
The issue here is that getExitSet() depends on finding a sibling of the
least-common-compound-ancestor (LCCA) in order to determine the bounds
of the exit set. In this case -- transitioning from Action1 to Action2 -- the LCCA is 'Child'. However, 'Child' has no siblings. When the LCCA has no siblings, getExitSet() takes the action of including all
subsequent states (in document order) in the exit set.
The text was updated successfully, but these errors were encountered:
Fixed an issue that caused getExitSet() to return an incorrect result in
certain configurations, leading to the unexpected exit of states unrelated to
the active transition.
fixestklab-tud#193
getExitSet()
can return an incorrect result in certain configurations, leading to the unexpected exit of states unrelated to the active transition.Given the following state chart definition...
...when taking a transition from
Action1
toAction2
, the expectedexit set is
[Action1]
. However,getExitSet()
returns an exit set thatincludes
Action1
in addition to allSibling*
states (i.e.[Action1, Sibling1, Sibling2, ...]
).The issue here is that
getExitSet()
depends on finding a sibling of theleast-common-compound-ancestor (LCCA) in order to determine the bounds
of the exit set. In this case -- transitioning from
Action1
toAction2
-- the LCCA is 'Child'. However, 'Child' has no siblings. When the LCCA has no siblings,getExitSet()
takes the action of including allsubsequent states (in document order) in the exit set.
The text was updated successfully, but these errors were encountered: