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
I'm working on making a statechart library in C which will support importing/code generation from XMI files. I started with StarUML to draw the machines and I think I've found a bug in either how StarUML organises data internally or possibly how the XMI exporter -plugin behaves.
This is what one of my test machines looks like:
The specific problem I have is how the transitions are stored with the composite state 'E'. I would imagine that transitions inside a composite state with orthogonal regions would have it's transitions associated with the respective region. However it does not seem to be how StarUML does it. Now, I'm not exactly sure how this should be but the UML standard certainly states that any region can 'own' transitions.
Here is a part of the XMI file:
//Jonas
The text was updated successfully, but these errors were encountered:
Hello,
I'm working on making a statechart library in C which will support importing/code generation from XMI files. I started with StarUML to draw the machines and I think I've found a bug in either how StarUML organises data internally or possibly how the XMI exporter -plugin behaves.
This is what one of my test machines looks like:
The specific problem I have is how the transitions are stored with the composite state 'E'. I would imagine that transitions inside a composite state with orthogonal regions would have it's transitions associated with the respective region. However it does not seem to be how StarUML does it. Now, I'm not exactly sure how this should be but the UML standard certainly states that any region can 'own' transitions.
Here is a part of the XMI file:
//Jonas
The text was updated successfully, but these errors were encountered: