gioneves commented on issue #20809: URL: https://github.com/apache/echarts/issues/20809#issuecomment-2704775007
Having two independent charts, each with its own `timeline`, is indeed a workaround—but it comes with its own set of drawbacks. First, it would require creating an additional `echartsinstance`, which increases memory usage and computational overhead, especially in complex dashboards. Managing multiple instances also means handling event synchronization manually if interactions are needed between charts. Second, even if I stick to one instance, I would have to swap option configurations dynamically to mimic independent timelines. This means manually reconfiguring series, axes, and other chart elements on every timeline tick—effectively reconstructing parts of the chart instead of smoothly updating them. This extra complexity adds unnecessary processing time and increases implementation effort, all for something that could be elegantly solved with a `timelineIndex` property within options.series. If axes, legends, and grids can be indexed, why not timelines? It would provide a much cleaner and more efficient solution. -- 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]
