GroveStreams

multi gauge display errors? FYI557

ero4444 private msg quote post Address this user
Thanks for bringing the forums back.

My gauge widget was updated, and as I recall, all the values in gauges#2 through #5 (everything except gauge#1) were zero. I made a new multi-gauge widget and dragged the same/updated? streams into the new gauges and they populated with non-zero values, but I think they are probably assigned incorrectly. Configuration parameters (e.g. TITLE) in Gauge#1 are being incorrectly pushed into #1 and #2. Stream values (e.g. POWER) in Gauge#1 is being incorrectly pushed into #1 and #3.

I did not positively identify a workaround in gauges. Probably multiple widgets of single gauges, could work.

I will try to attach a screenshot with circles and arrows showing the issue. This is just FYI, I don't have an urgent need for a fix.


Post 1 IP   flag post
MikeMills private msg quote post Address this user
Potential fix in the next patch. Not sure if we reproduced your issue but found a similar one and fixed it. We'll see after the patch.
Post 2 IP   flag post
ero4444 private msg quote post Address this user
most of the issues I noted earlier in this thread, have cleared up and now do configure predictably. Thanks.

Just for my notes of minor remaining issue:
#1 any single datastream(same-stream-name) in a gauge, will share most properties of that gauge, to the NEXT gauge with the same-stream-name in the multi-gauge widget. So the instant-power-gauge will have "mostly" the same properties-values as the minimum-24hour-power-gauge (for example the gauge title text is the same in both gauges).
#2 max recorded value marks seem to always be instant, no history is marked on gauge, so the max-mark is always shown at the current pointer value. min-mark always seems to be zero.
Post 3 IP   flag post
MikeMills private msg quote post Address this user
#1 Adding another stream to a widget copies the previous stream's settings. That's by design. Except, it is not supposed to copy the Title Name. That was a bug.

#2 "max-mark is always shown at the current pointer value". Couldn't reproduce that, but min and max markers were not starting with the initial values. Let me know if there are still issues after the next patch.

Also fixed a bug in the removal of streams from a widget. It was not always removing the selected streams.

The above is addressed in the next patch - coming soon.

Thanks for reporting these!
Post 4 IP   flag post
MikeMills private msg quote post Address this user
Patch applied
Post 5 IP   flag post
3044 5 5
Log in or sign up to compose a reply.