-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple elements at the same line #130
Comments
When a note or signal is indented with '=' it is shown on the same height as the latest note or signal without indentation. This is just a PoC implementation of bramp#130. The formatting is mucked up and the logic is a bit hard to read. If we decide this is a useful feature we probably want to make 'lines' (collections of notes/signals that are on the same line) a first-class citizen.
Yes, I would love this too. I need to describe a system with broadcast messages, and have been unable to find ANY sequance diagram drawing tool that support it. Just a minor comment about the prototype: There needs to be a marker on the vertical line of the sender, to show who sent the message. |
You mean this diagram is ambiguous because it could also be interpreted to mean A and C sent 'broadcast' messages to each other? I suppose that makes sense - but might be something for a separate PR/issue. #129 would be an alternative way to remove this ambiguity. |
I mean if there was a fourth actor D, and B sent to A and D, there would be no visual indication that B sent the message rather than C. |
Ah yes, that's a more realistic example of the same ambiguity indeed :). |
+1 I was looking for a way to have concurrent notes. At least those are not ambigous. Maybe the start of a line can have a small dot. |
Right now each new element (arrow or note) is drawn at a new 'line'.
It might be neat to also allow multiple elements on one line - though it'll probably be up to the user to make sure they don't cause overlap.
This could be represented using indentation:
The text was updated successfully, but these errors were encountered: