-
-
Notifications
You must be signed in to change notification settings - Fork 262
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
Clicking on data flow does not open it in properties #785
Comments
I understand the frustration @jbaptistemariebio , but this is the behaviour inherited from the drawing package and can not be changed. If you need to select with a single click then use the end points of the dataflow and click on either of them |
We can try and improve the documentation to emphasise this behaviour, given that there is not much we can do about it |
I'm on Windows, on Threat Dragon (desktop app) 2.1.3.0 and have the same issue. And just before posting this I accidentally stumbled upon a workaround to the workaround. I.e., if your data flow ends are tied to a process, and you can't simply click the end of the data flow, because it selects the process, the solution may be (works for me, at least for the couple of cases I tested) to first hover the mouse cursor over the data flow, for it's boundary box to appear, and then carefully move the cursor along the data flow until its end (making sure not to leave the boundary box), i.e., until the cursor changes (to show, that you can grab and move the ending point) and then click it. It may not be trivial, if the data flow line area between the processes is small. You can use zoom in, to make it a bit easier. |
Would it help to have a list of the objects on the side? At least this would make it possible the edit them from there. |
will have another attempt at improving the selectability of the dataflows and trust boundaries |
This is fixed in pull request 'Migrate to version 2.x antv/x6' #1099, where the selection of dataflows and trust boundary curves is greatly improved |
Describe the bug:
Clicking on an existing data flow does not set its properties into the properties section. A double click is needed, but it results in an addition of a new point on the data flow.
Expected behaviour:
A single click on the data flow makes its properties accessible in the properties section
Environment:
To Reproduce:
The text was updated successfully, but these errors were encountered: