-
I am attempting to recreate the issue in a simple application. While I am working on that, there is something that confuses me. This line is what is confusing me: int index = FirstDataSet.FindIndex(new TimeSpan(1, 2, 0, 31, 0), abt.Controls.SciChart.Common.Extensions.SearchMode.Nearest); It works fine until I add a SecondDataSet to the chart. I don’t change anything else. I just add a new dataseries have that data bound to the renderable series in the scichart. Why would calling FindIndex on FirstDataSet be affected by SecondDataSet?
-
I have no idea I’m afraid, but if you can recreate we can debug it and get to the bottom of the issue.
-
I figured it out! It was a silly mistake. As I was playing around with the values and learning about the different kinds of renderable series, I didn’t use the proper XyDataSeries property for the Append action. Thanks for your time!
-
That’s great! Glad you are sorted. Yes, the exceptions for unsorted data here http://support.scichart.com/index.php?/Knowledgebase/Article/View/17227/36/performance-tips-and-tricks are specifically designed to warn users if they have *accidentally* appended data unsorted in X. Intentional is fine if you set the DataSeries.AcceptsUnsortedData flag, just ideally you want the full power of scichart when your data ascends in X right?
-
Well, it is a confusing error to say the least. It tells me that the data is unsorted, but it is very clearly sorted. The issue was that, by appending a new data set to the series, it would throw an exception. It might have been that when I appended the new dataset to the dataseries, it found a conflict where the xaml for dataseries 1 and 2 were both bound to a certain x and y axis but they had different sets of data. i.e. the x values were different and it didn’t know how to handle that on the same x axis. What do you think?
-
I understand it. I thought about it a moment… I didn’t clear the data so while both data sets were ordered, appending one to another was not! Thanks again!