-
Notifications
You must be signed in to change notification settings - Fork 11.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
[FEATURE] actionable labels on radar chart (I will pay $) #5344
Comments
This could be implemented with APIs that look inside the internal Something would need to be added to the click handlers. Perhaps a decent solution is to make a public API on the radar chart scale that exposes this as rectangles that way a click handler could do detection |
If you mean fixed boxes size of labels over the canvas, why not just make the labels that too? |
to then use template literals to pass in proper HTML/JS content. |
That would need to be designed in a more general way (all labels of all scales) to avoid multiplying inconsistent APIs. It should be flexible and use cases independent: for example, we should not hard code the hover behavior (changing colors, etc.) but instead offer an API that allows to tweak whatever properties dynamically, certainly via scriptable options. I really want to avoid I don't think users want to intersect themselves label boxes because detecting hover events is a bit more work than click events. It requires to monitor when the mouse enter and leave a label from I submitted a PR for the datalabels plugin (chartjs/chartjs-plugin-datalabels#40) that goes in that direction, maybe there are some ideas we can reuse here? It may be better to kick off this feature as an external plugin since it can become quite complex. Though, it may be easier to make the datalabels plugin fits your needs than the scale labels. |
I have created #6549 which links to a JSfiddle containing a workaround to achieve this for version 2.8.0. |
I'd like to make the labels on the radar chart actionable (onClick, onHover, etc) without resorting to hardcoded image locations on canvas. The idea here is to solve this issue.
It's just plain rude to request new features without offering cold hard cash for the work. I don't really have time to do this myself, and someone who's very familiar with the codebase can probably do it a billion times faster than me anyway, so I'm perfectly happy to pay. Anyone interested simply comment here or email me directly if you prefer (gareth.hayes A gmail.com).
The text was updated successfully, but these errors were encountered: