I'm using the timeserieslinechart to display multiple speeds in a combined chart, eg. current transferspeed. This is quite peaky at times, rendering the graph incomprehensible when speeds are low again (i.e. peak at 3.5GB/sec back to normal 80MB/sec becomes a gnarly little dot).
For every update after adding new data I call
tslc.SetViewTimeRange(curStat.startTime.Add(-60*time.Second), curStat.startTime)
This is to only show data from the last 60 seconds, and that works for the X-scale.
But I'd like the graph to auto-adapt the Y-scale to the shown data, but I can't see how to do this with the current implementation. Looks like you can never "go back" to a smaller Y-auto-scale.
Also the graph does not allow you to remove data points, making it a memory hog for long running tasks.
I could of course just recreate a new graph for every update, adding the last 60 datapoints, but I'd rather not do that for performance issues.
Great library otherwise - cool graphs! Not sure if this is a bug or a feature request :-)
I'm using the timeserieslinechart to display multiple speeds in a combined chart, eg. current transferspeed. This is quite peaky at times, rendering the graph incomprehensible when speeds are low again (i.e. peak at 3.5GB/sec back to normal 80MB/sec becomes a gnarly little dot).
For every update after adding new data I call
tslc.SetViewTimeRange(curStat.startTime.Add(-60*time.Second), curStat.startTime)This is to only show data from the last 60 seconds, and that works for the X-scale.
But I'd like the graph to auto-adapt the Y-scale to the shown data, but I can't see how to do this with the current implementation. Looks like you can never "go back" to a smaller Y-auto-scale.
Also the graph does not allow you to remove data points, making it a memory hog for long running tasks.
I could of course just recreate a new graph for every update, adding the last 60 datapoints, but I'd rather not do that for performance issues.
Great library otherwise - cool graphs! Not sure if this is a bug or a feature request :-)