-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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 legend group titles should always toggle the group, even when groupclick=item #5911
Comments
This would be a huge plus and make groupclick much more useful. I flip back and forth between the modes as I visualize data from multiple sources and each source provides multiple "views" of the same data. Sometimes all views from a producer will be unhelpful but sometimes a producer that produces many views will have one useful view. So in that case I want be able to easily say "Give me all views from producer 1, no views from producer 2, and the third view from producer 3" which can be cumbersome if each producer gives me up to 100 views. If anyone has any other suggestions/workarounds in the mean time that would also be helpful. |
Is this the function that would need to change? I can't identify the line it handles legend group title clicks. plotly.js/src/components/legend/handle_click.js Lines 64 to 70 in 8050b27
|
Am I missing something or you want to revert a previous work with groupclick="toggleitem" in legend ? |
No we are not going to revert the previous work. |
Any updates? |
If the group title is clicked then shouldn't it do togglegroup? For example, if I have groupclick = "toggleitem", I want the individual trace to be toggled, but if the group title is clicked I want the group itself to be toggled. Is there a way to implement that? |
This is what exactly what I'm looking for. I really need this |
Hi! Could anyone please shed some light on this:
and thus toggle group via group title click and individual trace via respective trace item click? And is it so that this is not currently supported? In my experience with |
Follow up on #5906
The text was updated successfully, but these errors were encountered: