[WPF] Columns from ColumnSeries disappear from chart if Y axis is zoomed too much

[CodeWithMichal]

[WPF] Columns from ColumnSeries disappear from chart if Y axis is zoomed too much

[beto-rodriguez]

Got it with the previous commit, and the will be included in the next release (beta.13), thanks again!

[CodeWithMichal]

@beto-rodriguez did you manage to reproduce this bug ? :)

[beto-rodriguez]

I am rolling this fix back, I am now experiencing a bug because of this fix.

This was never a bug, I miss-understood the problem, The library automatically fits the view to the data on your chart.

The problem for your case was that your Y Axis had a limit from 0 to 4, if you look at your data, none of the values were in that range, thus you got that, and that was correct that is what the library should do, if you wanted to preserve the X range, then you must set the X axis limits too, or set a valid range in the Y Axis.

Notice this huge difference when zooming and panning, in the first image, the library is able to fit the view to the current data.:

Previously:

Now (after 126d232):

[CodeWithMichal]

Well, I think I didnt desrbice it clear enough. I was talking about situation when you have zooming and panning disabled and you keep MaxLimit on Y axis defined. Its because you want specific Y range.

I have FFT ColumnSeries chart which is updated every 500ms. I keep MaxLimit on Y axis set to 100 because for the most time these values are much lower than 100. But for time to time these values could increase far above 100 but I dont want to change MaxLimit as I dont really care about that kind of artifacts. Its fine for me to see only a piece of a column below 100. But you cant do it before 126d232 because if all columns exceeds MaxLimit then they dissappear from chart, like you can see on my screen

[beto-rodriguez]

Well, I think I didnt desrbice it clear enough. I was talking about situation when you have zooming and panning disabled and you keep MaxLimit on Y axis defined. Its because you want specific Y range.

I Agree, but notice in your image, that the library respects your range in the Y axis, but because you don't have a a range the X axis, then the library is trying to fit the view to the current data, since you have no points in that Y range, then the X axis messes up.

I think that the library should be smarter, and maybe use the previous valid range if the new one is not valid.