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
Within simulation mode in the editors please can a feature be added to show what actions are to be executed when a given event occurs. Identifying the actions by name/type and when fired (entry/exit/transition) in the log (or other) in a way that shows the fired action sequence relative to the state changes.
This would be very usefull in debugging complex compound/nested state machines (eg the deep test with actions) to see exactly which actions are fired and in what sequence for a given state and event/transition. Thanks
I suppose some generated abbreviation would be needed in cases where the action function is directly written in the machine config (ie unnamed).
Category
Editor
The text was updated successfully, but these errors were encountered:
I think a simple way to do this, as starting point at least, is to enable within the new editor simulation the current state object properties to be viewed as is done in the legacy visualiser (see Image below). The actions value then shows the current actions defined in the state. This provides a means to debug a complex action sequence for a transition. Would be very usefull for IOT application development amongst other use cases. Thanks for consideration. Regards, Simon
Details
Within simulation mode in the editors please can a feature be added to show what actions are to be executed when a given event occurs. Identifying the actions by name/type and when fired (entry/exit/transition) in the log (or other) in a way that shows the fired action sequence relative to the state changes.
This would be very usefull in debugging complex compound/nested state machines (eg the deep test with actions) to see exactly which actions are fired and in what sequence for a given state and event/transition. Thanks
I suppose some generated abbreviation would be needed in cases where the action function is directly written in the machine config (ie unnamed).
Category
Editor
The text was updated successfully, but these errors were encountered: