@manojkkuldeep,
We have just released Chart v3.2.3 with a few bug fixes related to using Striplines with the logarithmic axis. Please refer to the release blog for more information. Do download the latest version from our download page and let us know your feedback.
— Shashi Ranjan Team CanvasJS
@zeffirsky,
As of now, it is not possible to detect mouseover on a stacked chart and calculate the hovered area or line programmatically.
@chaman-kumar,
Can you kindly share the complete sample project that we can run locally to reproduce the issue and understand the scenario better to help you out?
The sample project shared above has too many dependencies because of which we are unable to run the code locally for reproducing the issue you are facing.
As of now, mouseover event is available for dataPoint in which it gets fired only when you hover mouse on a particular dataPoint and not on area.
Considering this thread as a duplicate of Detect hovered area in Stacked Area Chart and hence closing the same.
@creteurlouis,
You can bind mouse events to the chart-container(div) and get mouse coordinates in pixels, which you can convert to corresponding value along axis using convertPixelToValue. Please take a look at this JSFiddle for an example.
Armin,
logarithmic axis can only plot positive values. There simply is no way to put negative values or zero on a logarithmic axis.
Fundamental: If 10L = Z, then L is the logarithm (base 10) of Z. If L is a negative value, then Z is a positive fraction of less than 1.0. If L is zero, then Z equals 1.0. If L is greater than 0, then Z is greater than 1.0. Note that there no value of L will result in a value of Z that is zero or negative. Logarithms are simply not defined for zero or negative numbers.
@bselianakis,
Earlier WebKit allowed 448MB of canvas buffer memory whereas now they have dropped it to 224MB. Because of this, there was some memory issue with CanvasJS Charts in the latest iOS.
However, we have optimized memory consumption in CanvasJS v2.3.1 and we will further optimize it in future versions.
We have optimized this in version 2.3.1 . However, we will further optimize this in future versions.
Daniel,
In the JSFiddle shared by you, stepArea chart is rendered before stepLine chart. Because of this, stepLine chart gets hidden behind the stepArea chart(in case of area chart entire region gets filled). Positioning dataSeries with area charts before that of stepLine chart should work fine in your case.
Within the redraw function, populating dpss array with just dataPoint values instead of pushing the entire chart-options should work fine in your case.
dpss
You can use fillOpacity property for dataSeries where Step Area Chart are used. This will enable you to show those dataSeries which were getting hidden due to overlapping with other dataSeries.
Is there any rule in which order the series are drawn to the chart, so that I can organize it in the correct order?
DataSeries are rendered in the same order in which they are passed to the chart-options.
You can achieve Stacked Step-Area chart using Step-Area Chart as shown in this JSFiddle.
@djabornig,
You can try using Stacked Charts to achieve your requirement. In case of line / step-line / area chart one series may overlap with another whereas, in stacked area chart, each series is stacked one on top of the other.
It seems like access to the above sample project is restricted.
Please share the complete sample project so that we can run code locally to understand the scenario better and help you out.