-
Notifications
You must be signed in to change notification settings - Fork 231
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
New freezeAllDragEvents configuration property to prevent node drag-and-drop #388
New freezeAllDragEvents configuration property to prevent node drag-and-drop #388
Conversation
Ok I think I achieved what was originally asked for. The new prop also disables panning and zooming, while leaving graph elements clickable. |
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.
Thanks for the PR! 👏 Sorry I could not make it during Hacktoberfest. If you're still up to move this one forward, please consider my comments.
That's fine, with the new restrictions, I wasn't really going for it. I'll try to update the PR later today. |
I tried manually pulling out older versions of those sandbox/ and tools/ auto-generated files from previous commits, but for some reason, two of them still appear modified in "Files changed". |
Try running:
Explanation: |
Ah so the post commit hook was to blame after all? |
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.
👍
Hello and happy Hacktoberfest!
I implemented the resolution to the feature request in #308 that @danielcaldas described. It seems to work in that the nodes are frozen, but the entire graph still can be panned around and zoomed into. Let me know if the idea was to block those drag events as well (I can't tell with certainty from the discussion), and I can try to tackle this further.