Came here hoping that this limitation of the original gauge.js code from tomerd would be removed but unfortunately not! (This is not to belittle the other improvements.)
To elaborate, it appears that the gauge's scale still has five major ticks with five minor ticks each (or whatever the tick preferences are defined), whatever the min and max value used is. Thus if min is -10 and max is +100, not only is there no easy way to see where the origin is, but the ticks are entirely misleading. I could be mistaken but I don't see an easy way to adapt the gauge to show the ticks correctly for an arbitrary range.
Supporting d3 scales may need writing a custom axis generator, but I hope you agree it would be a valuable improvement. Have been looking into supplying such a custom axis implementation, but so far have been a little put off by needing to work around the npm and xtend dependencies by hacking the code or installing and understanding browserify.
Came here hoping that this limitation of the original gauge.js code from tomerd would be removed but unfortunately not! (This is not to belittle the other improvements.)
To elaborate, it appears that the gauge's scale still has five major ticks with five minor ticks each (or whatever the tick preferences are defined), whatever the min and max value used is. Thus if min is -10 and max is +100, not only is there no easy way to see where the origin is, but the ticks are entirely misleading. I could be mistaken but I don't see an easy way to adapt the gauge to show the ticks correctly for an arbitrary range.
Supporting d3 scales may need writing a custom axis generator, but I hope you agree it would be a valuable improvement. Have been looking into supplying such a custom axis implementation, but so far have been a little put off by needing to work around the npm and xtend dependencies by hacking the code or installing and understanding browserify.