Multiple internal transitions are not rendered nicely about state-machine-cat HOT 3 OPEN

Hi @noricor - I guess you mean that this...

...could render nicer? State-machine-cat runs into the limitations of the auto-layout engine in some occasions. I'm on the lookout for an other one.

That said if I interpret your last sentence correctly: would something like this work? Or does this miss something?

Initial.initial,
On: 
events.GetState / Action.GetState
events.GetVersion / Action.GetVersion
events.SetLogLevel / Action.SetLogLevel
 { 
   foo:events.GetState / Action.GetState, 
   bar;
   
 },
 Off.final;

Initial.initial -> On;
On -> Off.final : events.Exit / Action.Exit;
On -> On : events.Reset;

from state-machine-cat.

Hi,

yes, you identified the rendering issue correctly, especially for large state machines (20-30 states with lots of transitions and stuff) this becomes a readability issue.

Regarding the second part. Yes, this would work and it is also more in line with the UML 2.5 spec which introduces an "internal transition compartment" for states

Internal Transition compartment
This compartment contains a list of internal Transitions, where each item has the following syntax:
{trigger}* ['[' guard']'] [/behavior-expression]
Where is the notation for Triggers (see sub clause 13.3.4), is a Boolean expression for a
guard, and the optional is the specification of the effect Behavior to be executed if the
Event occurrence matches the trigger and guard of the internal Transition. It is an expression written in some
textual surface language, which may be either a vendor-specific or some standard language (see sub clause
16.1).

Cheers

from state-machine-cat.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

from state-machine-cat.