WinBox graph does not respect extremum on decrease

Dear Community and Developers,

Thank you very much for the marvel, art, you do…

I am sorry, but just wanted to clarify the following rationale in awesome WinBox (v4.0beta20).
The graph rendering function respects the maximum traffic load values, but with those getting out of the graph range, the function still renders the graph with the maximum set to the value now in time missing from the time range of the graph. That makes the graph practically empty with any single moment in time with a value significantly higher than the average.

For example, a graph had been showing a traffic of 0-100 kbps for some time, and then, with a single second/point of 10 mbps, the whole graph looks empty due to all the rest points of 100 kbps now invisible laying at the very bottom of the whole render result.
The following preview shows two graphs of the same interface traffic load: on the left, we may see a graph with maximum extremum stored in the function (e.g. 400 mbps) which makes the whole graph almost empty; on the right - we may see a graph on a reloaded window with not yet stored so high extremum (e.g. 800 kbps) - and that at least allows to see the data visualized in more adequate manner.
mikrotik_winbox.png
Is it an expected behavior? If not, is it possible to reset the maximum on each render, so the graph would automatically adapt to the highest value?

Best and kind regards :sparkles:

Evidently, the ratio changes gradually. That is the graph maximum limt changes from 100.0 mpbs to 500.0 mbps just the moment a value crosses the first.
In the result, we have the following, and even with the peak leaving the graph in the future, the maximum won’t drop to the initial - 100.0 mpbs.
2025-05-08_23-38-18_Z_abIygHSu.png
2025-05-08_23-38-35_Z_p29nKqbt.png