Inconsistent transition target handling in behavior diagram layout
The behavior diagram layouter uses different transition target resolution in different places, which might result in inconsistencies and skipped layouting of transitions.
Note: I'm not sure what the original intention was with the grouping of transitions according to destination terminal? Were the transitions meant to be grouped by destination substate tr point, or just destination state?
transition path name is not unique
- substate tr point vs. terminal node in current state graph
- will have an effect if same path entry is present and one or more paths or transitions has the same path name: the count will be off and transitions that shouldn't be placed will be place, while others that should be placed may be skipped
self transitions:
- uses getTerminalState, so transitions going to different substate tr points will count as self transitions
- technically still works because it means it will be placed as an individual transition and not a path, but not sure if conceptually incorrect
- probably has a layout effect (grouping?) if there are multiple substate tr points and/or multiple transitions on the same (state -> substate tr point) path
Edited by Eyrak Paen-Rochlitz