Trying the web-version of trend-data. This seems to be a impressive tool, but I lack/cant find a number of what I would think are important parts.
There does not seem to be a way to get away from the dot.notated variable naming in the legend.. A developer might want the dot-notation but an end-customer will surely not.
For instance I want to display 12 temperatures, instead of t1, t2 etc.. they will be named.
Trying the web-version of trend-data. This seems to be a impressive tool, but I lack/cant find a number of what I would think are important parts.
There does not seem to be a way to get away from the dot.notated variable naming in the legend.. A developer might want the dot-notation but an end-customer will surely not.
For instance I want to display 12 temperatures, instead of t1, t2 etc.. they will be named.
gvl_io.unit[1].trend.temps.t1_a
gvl_io.unit[1].trend.temps.t1_b
gvl_io.unit[1].trend.temps.t1_c
gvl_io.unit[1].trend.temps.t2_a
..
gvl_io.unit[1].trend.temps.t4_b..
gvl_io.unit[1].trend.temps.t4_c..
Quite a lot of unnecessary text/data taking space from the actual trend =>
Is there a way to access/interface the legend-data programmatically so I can change the presentation/naming?
Related
Talk.ru: 1