linechart symbol markers at the end of each line
At SSB we have a lot of auto generated charts, and need symbol markers on charts to fulfill accessibility requirements, but on a lot of our linecharts the point density is so great that the chart becomes unreadable, but not dense enough for the "null" option to kick in and remove the markers.
Therefor, what we need is that marker symbols appear at the end of each line, while also appearing at the corresponding legend.
(We tried a solution that was posted in another feature request, but found no way to implement it with auto generated charts and also it removed the symbols from the legend, which again makes symbols on the lines useless.
(it was this feature request: https://highcharts.uservoice.com/forums/55896-highcharts-javascript-api/suggestions/2407939-allow-series-data-marker-config-obj-to-overwrite ) )
Erik Chrisander Gustavsen
shared this idea
I have implemented a new option, enabledThreshold. Now we can explicitly add a marker to the last data point to achieve the required effect: http://jsfiddle.net/highcharts/sj167xkm/
-
It's hard to say without seeing your actual code - what I can say is that the point configurations must be objects, then you set that marker configuration on the last of the objects.
-
Erik Chrisander Gustavsen
commented
I'm having some trouble setting the marker on the last data point when getting data from tables and parsing it.
Should the "arrayname[arrayname.length - 1].marker = { enabled: true };" be placed inside or outside the parsing function?
-
Erik Chrisander Gustavsen
commented
I have looked at the jsfiddle and that is exactly what I had in mind, it looks and works great :D
-
Erik Chrisander Gustavsen
commented
Hmm, yes, I think that would solve our problem.
Also make sure the markers on the legends still appear, and I think this solution will work nicely :)Do you have a rough estimate on when this will be implemented?
-
Thanks for using Highcharts!
> on a lot of our linecharts the point density is so great that the chart becomes unreadable, but not dense enough for the "null" option to kick in and remove the markers.
Does this mean we could solve your case by adding an option for when to remove the markers? Currently they are removed when the closest distance between two points is less than twice the marker radius, i.e. before markers start overlapping. We could easily add an option to increase the threshold. Then if we add a single marker in the cases when they are auto-removed, it would meet your requirement?