Bug #1972
Composite state transitions are displayed erronous
| Status: | New | Start date: | 09/01/2014 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | P. Holthaus | % Done: | 0% | |
| Category: | - | |||
| Target version: | Language Engineering - Language Refactoring |
Description
The state which is transitioned to after a composite state is always included within the composite state itself (see image)
@startuml
title example
[*] --> s1
state s1
s1 --> composite_s1
state composite_s1 {
state sub_s1
sub_s1 --> external_s2
}
state external_s2
@enduml
Leads to:
however, a different plantuml syntax (moving the following state before the composite state) created the correct image:
@startuml
title example
[*] --> s1
state s1
s1 --> composite_s1
state external_s2
state composite_s1 {
state sub_s1
sub_s1 --> external_s2
}
@enduml
Leads to:
So, should we adjust the DSL to work with this?
Associated revisions
History
#1 Updated by S. Wrede over 9 years ago
This seems to be a bug in the plantUML renderer. Rendering all top-level states at the top of the file and all transitions at the end of the file should help. This can be enforced in the generator implementation.
#2 Updated by S. Wrede over 9 years ago
- File rendering-error-2.png added
- File rendering-error-2.png added
Even worse the following
@startuml
title example
[*] --> s1
state s1
s1 --> composite_s1
state external_s2
external_s2 --> sub_s1
state composite_s1 {
state sub_s1
sub_s1 --> external_s2
}
@enduml
leads to the following diagram:
#3 Updated by N. Köster over 9 years ago
- Priority changed from Normal to High
The lsp-csra kitchen scenario plantuml is also affected by this. Moving transitions at the bottom solves this issue. Its quite important, as all rendered images which include composite states have those errors and need to be modified by hand.
#4 Updated by S. Wrede almost 8 years ago
- Assignee changed from S. Wrede to P. Holthaus
- Target version set to Language Refactoring
Is this still a problem?
#5 Updated by S. Wrede almost 8 years ago
This seems to be fixed in master. See solution Test, Model Issue1972.