Chart EntryClick Series mis-identification

I have a simple app that charts the battery current and voltage of the device ( it uses the chart component included ).
I have a line chart with 2 series. I've added the 'entryclick' event to retrieve the series name, x and y value of the point clicked.

It works in that the x and y values are retrieved correctly, but the serie name is invariably the second serie name, even if I click a point of the first serie.

I followed this post advice Is it possible to have my Chart with text axis? - #19 by ABG not sure I did it correctly ( also chart documentation not very extensive on the point ).

Bat01_04.aia (49.8 KB)


Your two series are the average and current values of current.

Applying a Do It to their values, I see they vary widely in scale.

That probably explains why I only see one series (blue A(ist) ) on the graph, and why the only series I can click is the visible series.

You would have to discuss the different value scales with the extension developer.

I don't support extensions.

Thanks for the prompt reply.
In my case ( on my phone ) the average and istantaneous currents are both in the same scale and shown correctly.on the graph
The only annoying thing is that the serie name ( the first value in the box on top of the images ) is fixed to A(ist):

  • on the first image I clicked the first serie X=1265 Y=-165mA but serie name is A(ist) ( and should be A(avg) )
  • on the second image I click the second serie X=1630 Y= -440mA and serie name is A(ist) ( which is correct in this case )

P.S.
On your device you could divide the icurrentavg value by 10000000000000000 ( 16 zeroes if I counted right ; - ) to have both values on the same scale ( by the way ai2 uses a "decent amount" of significant digits in calculation )


You have found a bug.

I used the AI2 console to log notifications of series click events, after separating out the chart level events into series level events, and discovered that only the ist series was getting its event fired.

This was after setting up my own 'average' series calculated from the current readings series and elevated by 100 to separate it from the current readings.

I am reclassifying this as a bug.

Bat01_04.aia (51.4 KB)