Impact: This bug makes it impossible to use standard features like activity stereotypes or data objects in activity diagrams with these PlantUML versions, severely limiting the ability to create visually accurate and semantically correct flowcharts. It also affects the parsing of more complex, but otherwise valid, activity diagrams.
The following method should only be used IF you are running plantuml server on your local laptop via docker and like to use it instead of the jar with say visual studio code simply due to the speed boost it provides over the jar.
I have experimented with multiple separate diagrams in the same file. I was hoping to do this to demonstrate the different themes. @startuml !theme amiga Alice -> Bob: Hello Bob -> Alice: Hi there! @enduml @startuml !theme aws-orange class Car { +String make +String model +int year } @enduml @startuml !theme black-knight c -> d: Hello d -> c: Hi there! @enduml The themes bleed into each other ...
I'm bypassing Plantuml's node layout and using the Graphviz one instead. I mean Graphviz can do html style nodes containing colours, tables, images, etc (see my answer to this question).
On my end, I haven't fixed the diagrams yet, as I prefer PlantUML to resolve the issue on their side so that all my existing diagrams continue to work as they did before without any changes.
