标签:
下述情况下会发生这个错误:
This error occurs if the series.data
option contains object configurations and the number of points exceeds the turboThreshold
. It can be fixed by either setting the turboThreshold
option to a higher value, or changing your point configurations to numbers or arrays. See turboThreshold
This error occurs if the chart.renderTo option is misconfigured so that Highcharts is unable to find the HTML element to render the chart in.
This happens if you pass in a string as a data point, for example in a setup like this:
series: [{ data: ["3", "5", "1", "6"] }]
Highcharts expects the data values to be numbers. The most common reason for this is that data is parsed from CSV or from a XML source, and the implementer forgot to run parseFloat
on the parsed value.
For performance reasons internal type casting is not performed, and only the first value is checked (since 2.3).
This happens when you are trying to create a line series or a stock chart where the data is not sorted in ascending X order. For performance reasons, Highcharts does not sort the data, instead it is required that the implementer pre-sorts the data.
This error happens the second time Highcharts or Highstock is loaded in the same page, so the Highcharts
namespace is already defined. Keep in mind that the Highcharts.Chart
constructor and all features of Highcharts are included in Highstock, so if you are running Chart
and StockChart
in combination, you only need to load the highstock.js file.
This error happens when you are setting chart.type
or series.type
to a series type that isn‘t defined in Highcharts. A typical reason may be that your are missing the extension file where the series type is defined, for example in order to run an arearange
series you need to load the highcharts-more.js
file.
This error happens when you set a series‘ xAxis
or yAxis
property to point to an axis that does not exist.
This error happens when you try to apply too many ticks to an axis, specifically when you add more ticks than the axis pixel length. In practice, it doesn‘t make sense to add ticks so densely that they can‘t be distinguished from each other. One cause of the error may be that you set a tickInterval
that is too small for the data value range. In general, tickPixelInterval
is a better option, as it will handle this automatically. Another case is if you try to set categories on a datetime axis, which will result in Highcharts trying to add one tick on every millisecond since 1970.
In Highstock, if you try to add a point using the object literal configuration syntax, it works only when the number of data points is below the series‘ turboThreshold. Instead of the object syntax, use the Array syntax.
标签:
原文地址:http://www.cnblogs.com/jayzee/p/4538795.html