-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Label events (enterLabel and clickLabel) #1319
Comments
Hi @cyclecycle, I see the usecase and I actually have seen multiple times people trying to interact with labels indeed. I think as long as it does not bring too much complexity and performance issues, it would be a great new feature! However, this feature would have to handle the fact that labels are now always drawn with the same shapes and dimensions, since the Lines 60 to 61 in 7b3a5ea
Here is a real life example of an app that uses a custom Also, since some features in the pipe require breaking changes, we are starting to work on a v3, and this might be a good time to improve the |
Hi @jacomyal, I see what you mean. The custom A solution might be for |
Here's a demo of the above suggestion: main...cyclecycle:sigma.js:label-events It kind of works: When running the 'events' example, I am able to trigger Let me know what you think. Cheers |
What happened to this brilliant idea? 👀 |
Hi all, Sorry about my silence on that topic. Basically, I understand that it would be very useful for many people. Here are some insights about labels management in sigma and why making them interactive is challenging:
The main solutions I have in mind to implement this are:
Since both solutions are impactful, I'll flag this feature for version 4. |
We would like to implement hover and click event listeners for labels, because we have found that users often try to click on labels instead of nodes.
If you agree this should be a feature, we would be happy to put in a PR for it. If this is already achievable without any feature additions, please guide me on how to do this.
Thanks!
The text was updated successfully, but these errors were encountered: