Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Candlestick in the navigator is not displayed when points are given as objects #1905
It happens because the data is simply copied from the base series to the navigator, and the area series in the navigator doesn't understand the object literal with open, high, low and close properties. A fix would mean that we iterate over the data set and either add y properties or translate it back to array format. It wouldn't be very effective though.
The data may be referred at somewhere else, so the object literal could be useful.
So is it possible to reuse the translated xData, yData and zData from the base series in the navigator series?
Done a test for a stock chart with around 8000 data entries (8000 x 4 = 32000 numbers as every stock data point have four values for open, close, high and low).
The difference between using the number array and object array is 44ms
So even we do the translation from object array to number array again for the navigator series, it may be desired to pay the additional tens of milliseconds performance cost to use the options which need to be passed as object array as mentioned in previous comment:
So could you please look into it?
Test results for Stock chart with 8000 data entries: