Chart not updating when changing Axis value ShowSeparatorLines

[rteuteu55]

Describe the bug
When changing the ShowSeparatorLines value of an Axis, the chart is not update automatically. I'm using live charts v2 (2.0.0-beta.101 also tested with 2.0.0-beta.60) and I have the following Nugets added to the test project: liveChartsCore & liveChartsCore.SkiaSharpView.WinForms.

To Reproduce

1. create a chart with some values and an axis
2. try to toggle the "ShowSeparatorLines" of this Axis. Nothing will update.

• chartTest.XAxes.First().ShowSeparatorLines = !chartTest.XAxes.First().ShowSeparatorLines;
  Note: If I toggle the Axis IsVisible value twice (through a button) the axis will display the Separator Lines correctly

Expected behavior
My understanding is that all the values from an Axis trigger change Notification. Some values do impact the Axis instantly (like changing the SeparatorsPaint value, the label rotation, the visibility).

Screenshots
See attached Gif

Desktop (please complete the following information):

• OS: Windows 10

[langejay]

This might help?

#407

In my code I use:

View.Chart.CoreChart.Update(new ChartUpdateParams { });

[beto-rodriguez]

strange 🤔 I will investigate this.

[rteuteu55]

This might help?

#407

In my code I use:

View.Chart.CoreChart.Update(new ChartUpdateParams { });

Thank you for this link. I do not hold a reference to the Chart in the ViewModel normally so this might be an issue, but still worth investigating!

[beto-rodriguez]

Fixed with the referenced commit and will be included in the next version of the library.

[rteuteu55]

Hi @beto-rodriguez the changes you made have improved the situation, but it seems the issue partially remain still:

• Changing ShowSeparatorLines works when an axis is first made visible with ShowSeparatorLines as true.
• Changing ShowSeparatorLines doesn't works when an axis is made visible with ShowSeparatorLines as false.

See following gif:

[beto-rodriguez]

Thanks for the update, I will take a look.

[beto-rodriguez]

Ok it seems that I got this now with the referenced commit.

Thanks for the update and the issue, this will be included in the next version of the library.