-
Notifications
You must be signed in to change notification settings - Fork 418
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
WIP feat(selection-visuals): add marker to related elements #290
base: main
Are you sure you want to change the base?
Conversation
242aed0
to
8d57bf5
Compare
6228fcd
to
6a5e6d0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the user perspective, which alternatives did you consider for implementing this feature?
The following shows a quick recording of the look and feel in bpmn-js:
Two things immediately get apparent:
- It is not possible for a user to distinguish the actual selected element from the connected element. This is a major UX flaw and needs to be addressed.
- Highlighting the label that belongs to an element only works for connections. Why is that? Any element may reference external labels (cf. start event in the screencapture shown above).
From the implementation perspective I'd ask you not to patch the stuff into the SelectionVisuals
but to provide this as a new feature (call it highlight-related
or something). This way users may decide to use it (or not) and the code base remains maintainable.
I already addressed:
- fix commit message style (using feature name
selection
as context) - correct import to relative path (6a5e6d0); importing from an absolute
lib
path within thelib
directory works in tests only but fails in the final bundle
6a5e6d0
to
e611acf
Compare
edc4b0b
to
8d08b9f
Compare
8d08b9f
to
f8a2dda
Compare
@nikku Thanks for the feedback! Let's discuss the points you've mentioned
I've just made the opacity of the related element's outline a little less to make clear, which element is actually selected or hovered. What do you think? Sure, we can discuss coloring the related element boxes with another color or giving them another shape, but this would break the current experience a little bit.
Done!
I've just created a new feature inside the |
Niklas Kiefer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
.djs-outline
class is set all the time, regardless the shape is selected before or notRelated to camunda/camunda-modeler#369