SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and now iOS Charting & Android Chart Components
Please use the forums below to ask questions about SciChart. Take a moment to read our Question asking guidelines on how to ask a good question and our support policy. We also have a tag=SciChart on Stackoverflow.com where you can earn rep for your questions!
Please note: SciChart team will only answer questions from customers with active support subscriptions. Expired support questions will be ignored. If your support status shows incorrectly, contact us and we will be glad to help.
I don’t think this is a bug, but the expected behaviour of the CategoryDateTimeAxis. Please see our article on Category Axis vs. Value Axis here.
Value Axis vs. Category Axis
SciChart ships with a value-axis and a category axis to handle DateTimes. The Value axis includes the Date-value when measuring the X-coordinate, e.g. a sequence of dates such as Monday, Tuesday, Wednesday, Monday, Tuesday, Wednesday will have a large X-gap between the Wednesday / subsequent Monday points. However the CategoryDateTimeAxis is a category axis and would treat each data-point (regardless of value) as equally spaced in the X-direction. As an illustration, consider the following screenshots of SciChart with a DateTimeAxis and CategoryDateTimeAxis respectively, which renders stock price data with gaps overnight (outside of trading hours):
What we do in our examples is we ensure DataSeries on a CategoryDateTImeAxis have the same number of data-points. We do this by pre-pending Moving Averages with double.NaN (a null value). So you can see in the Candlestick and Lines example, the series have different numbers of data-points but are aligned because of padding values.
Please login first to submit.