[GitHub] [echarts] ob-ARC commented on issue #19036: [Bug] time axis interval setup impossible, splitNumber outcome unpredictable.

["ob-ARC (via GitHub)" <gi...@apache.org>]

ob-ARC commented on issue #19036:
URL: https://github.com/apache/echarts/issues/19036#issuecomment-1693275566

   > > No way to reliably control time axis intervals.
   > 
   > It seems you want to set programmatically _splitNumber_ and/or _interval_ just **once**. Lets assume this is done. What would happen next, when users **zoom in** ? Would they be happy seeing a bunch of data over an empty axis line ? Or would a developer be happy handling zoom events and recalculating axis label positions and frequency ? Hmm, I think the status quo is a good deal.
   
   I'm sorry, what? If I set splitNumber to e.g. 5, this obviously should be the guideline for number of splits on any given zoom state. As stated above - in the simple example there is just no reason why the desired splitNumber should not work. Or do you know any? This works nicely for value axes (even if zoomable), so why should I not want that to work on time axes as well? 


-- 
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: commits-unsubscribe@echarts.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@echarts.apache.org
For additional commands, e-mail: commits-help@echarts.apache.org