[charts] Axis min/max does not allow dynamic rescaling of the other Axis when that axis has no min/max set about mui-x HOT 5 OPEN

@alexfauquette should we just move this to the board then? 🤷🏼

from mui-x.

perhaps this short video will help.... The series data points are floats (0.1 scale)

So I can handle this myself if necessary by removing the older datapoints from the dataset I provide the chart, but this shifts a bit of heavy lifting to the consumer for what should be a pretty cool built-in feature.

from mui-x.

one last example before I turn it over to y'all to classify / prioritize / dismiss / etc. This is the expected behavior:

Here's that heavy lifting I was referring to:

• Build logic in backend service to limit sample size based on time offset
• Account for latency / lag introduced due to network time, processing, and rebinding
• Introduce a progress indeterminate or similar to block UI action while waiting (TO DO)

I suppose I could also build a client side loop into the dataset, taking account of the time offset (zoom level) and setting the yAxis min/max based on the min/max observed samples within that zoom level. This will definitely speed things up and in hindsight should've been the path I took to work-around this.

from mui-x.

Thanks for the feedback

Effectively, the min/max are for now a just a basic way to override the displayed range of element, and the easiest solution might be to compute y min/max client side according to the data and the x range.

This feature might be supported when adding the "Zoom on mouse" in the pro package

from mui-x.

would love to see the "zoom on mouse" feature, would allow me to switch from the currennt lib i use to muix one.

from mui-x.