ShanteshSindgi commented on issue #21744:
URL: https://github.com/apache/echarts/issues/21744#issuecomment-5693802182
@helgasoft
I have a couple of follow-up questions on choosing the right value, since we
need to apply this generically across many charts (varying series counts, axes,
legends, toolboxes, dataZoom, etc.):
What is the recommended value / how should it be chosen? The comparison is
against the total rendered element count (elCount in updateHoverLayerStatus),
not just data points. So a fixed +45 buffer works for large single-series
charts but falls short on smaller charts with more chrome (extra axes, legend
items, toolbox, dataZoom), where non-data elements alone push elCount past
dataCount + 45 and the hover layer re-engages — breaking the highlight again.
Is there a recommended way to compute a safe threshold, or a fixed
element-count value you'd suggest?
At what point should the hover layer be enabled? The docs describe
hoverLayerThreshold (default 3000) as a canvas repaint optimization ("avoid
re-painting the whole canvas," "extra canvas," "burden on mobile devices"). On
the SVG renderer, does raising this threshold (or setting it very high to keep
the hover layer off) carry any real performance/memory cost? Or is the hover
layer essentially a canvas-only optimization that has little benefit under SVG
— in which case is it safe to keep it disabled regardless of element count?
Essentially: for the SVG renderer, is there a concrete element-count number
above which enabling the hover layer is actually beneficial, or should it just
stay off?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
