Settings and activity
1 result found
An error occurred while saving the comment An error occurred while saving the commentKjell commented
Appreciate your interest in the idea.
I think your take on it is about what I had in mind too. The two waterfalls do not need to be one logical chart entity, but only drawn to be placed on top of each other. The first waterfall series (positive y side) could be a master, responsible for drawing the x and y axes. The master would need to extend the y-axis into the negative domain to be able to display all of the second (slave, negative y) series. The maximum of the second, slave series will need to be known and passed to the master. The slave series will then be positioned to draw exactly within the master's plot area, with identical y range and pixel length of the x axis. Labels should typically be placed in the waterfall boxes to avoid collisions.
Hope this gives some convergence.
An error occurred while saving the commentKjell commented
Here is a link to a ppt file with a simple sketch of the concept.
I can also send some sample data if you wish. Basically there will be two separate waterfall series with a possible option of having a final "reconciliation" value/bar that makes the sum of the two series equal (preferably automatically computed). This highlights that the chart is good for "account balancing".
KjellKjell shared this idea ·
I was able to put something together that in my view looks very nice. The basic implementation techniques came from the Highcharts example with synchronized charts. The key to making it work as a "canned" chart routine, however, turned out to be a very flexible "normalizing" processor for the two series.