[dzarras]

Sounds good -- I'll give it a whirl...

[dzarras]

This is working great now -- thank you very much.

[chellegaard]

Strange bug with getNearestDrawnValue

We're in the process of evaluating a migration of our charting to SmartGWT pro.
We've followed the examples of dzarras, but discovered a bug with getNearestDrawnValue(): whenever the last CellRecord to be added to the graph doesn't have a value for the last x-index the getNearestDrawnValue() call breaks down and the facetValueMap ALWAYS contains the name of the last record and the highest x-value (the largest x-coordinate, which this record doesn't have a value for).

The attached screenshot may be a bit blurry - but it shows that no matter which point (on any graph) is clicked or hovered on the result is series2 (the green 2nd series and the last to be added) and id49 (last x-index value on the graph).

The workaround is of course to inspect the list of CellRecord's and add one with a value for the highest x-index as the last one!!
...just thought you wanted to know about this bug ;)

[Isomorphic]

Sounds like an already-fixed bug - have you tried this with the latest build?

[weaxler]

Our build from last week has this problem also.

[chellegaard]

Latest build has the same problem!!

[Isomorphic]

Thanks for pointing this out, this has now been fixed for tomorrow's 4.0 builds.

[chellegaard]

Build of 21/4 works perfectly ;)