Graphic Bar Chart-2

Sato

Hi kl3m3n,

Thank you. Tomorrow will test it

Regards

Hub

Thanks for developing and adding new widget settings. In addition to the YTC (ticks on vertical axis) parameter, it would also be very useful to specify the minimum and (or) maximum value of the vertical axis.

By the way, an idea for discussion: optional displaying value above the bar.

Best regards,
Hubert

Sato

Hi @kl3m3n,

This don´t compile show error: unable to find string literal operator......
String cmd="|MBCH UID:mbch1 X:75 Y:64.5 W:47 H:60 SHG:1 SCI:1 FSZ:3.5 FFA:"font10" YTC:12 PLCO:#6D9DC5 XMA:2 YMA:2 MCHV:";

This compile, the FSZ can be sized but i think that is not the font10, i think that assumes the default font0
String cmd="|MBCH UID:mbch1 X:75 Y:64.5 W:47 H:60 SHG:1 SCI:1 FSZ:2.3 FFA:"font10" YTC:12 PLCO:#6D9DC5 XMA:2 YMA:2 MCHV:";

What make i wrong?

Thank you
Regards

Sato

@Sato

I was too hasty, I did more tests and it turns out that the font changes as well as the size.

FFA:\"font4\" //like this works

Sorry

Regards

kl3m3n

@Hub said in Graphic Bar Chart-2:

Hello @kl3m3n,

Thanks for developing and adding new widget settings. In addition to the YTC (ticks on vertical axis) parameter, it would also be very useful to specify the minimum and (or) maximum value of the vertical axis.

By the way, an idea for discussion: optional displaying value above the bar.

Best regards,
Hubert

Hi,

yes, I can add the minimum and maximum value option. I will put it on my TODO list.

I will also check what needs to be done in order to display values above each bar.

Best regards,
Klemen

Sato

Hello kl3m3n,

Could you please check this:

//mo = "0" or "1" or "2" Freeze, to use Gui-O again i have go to settings - applications and force Gui-O to stop
it is no problem for me, i can initiate mo with "3" that works, but if you want analyse that!

mo = "3"; tu = "0"; we = "0"; th = "0"; fr = "0"; sa = "0"; su = "0"; // works
String mchv=""" + mo + "," + tu + "," + we + "," + th + "," + fr + "," + sa + "," + su + """;
String cmd="|MBCH UID:mbch1 X:75 Y:64.5 W:47 H:60 SHG:1 SCI:1 FSZ:3.5 FFA:"font6" YTC:10 PLCO:#6D9DC5 XMA:2 YMA:2 MCHV:";
cmd += mchv;
cmd += " MCHL:"Monday,Tuesday,Wednesday,Thursday,Friday,Saturday,Sunday"\r\n";
mqttClient.publish(&In[0], cmd.c_str());

Regards

kl3m3n

@Sato This is probably a bug. I will check it.

But your parameters also do not make any sense. Your maximum value is 3, but you are dividing the Y axis to 10 segments... If YTC is specified, the step is always an integer...

But, in any case it is a bug on my side.

Best regards,
Klemen

Sato

Hello @kl3m3n,

I know it doesn't make much sense as it stands, but the point is that it's meant to be daily data on a weekly basis. Every Monday between 00:02 and 00:05 it rewrite all the daily files with "0".
By the end of the week, each day could have 10...300 units, for example.

Thank you
Regards

kl3m3n

@Hub @Sato

I have added support for specifying low and high Y axis values along with auto-scale option (off by default). If auto-scale is enabled (YASC:1), then YLO, YHI, YTC values are applicable. This also makes it possible to control if Y axis values are displayed as integers.

The manual is already updated. The feature is implemented in app v1.0.66.

@Hub Specifying the labels above the bar is currently not possible.

Best regards,
Klemen

Sato

@kl3m3n,

Thank you

Regards

Sato

Hi @kl3m3n,

Good work, congrats

Regards

Hub

@kl3m3n Tank you for update.

I've noticed a small problem with rounding numbers on vertical axis.

Example 1:
'|MBCH UID:mbch1 X:50 Y:50 W:100 H:30 FSZ:2 PLCO:#b51d1d YASC:0 YLO:3 YHI:4 YTC:4\r\n'
'@mbch1 MCHL:"u1, u2, u3" MCHV:"3.2,3.42,3.54"\r\n'

Example 2:
'|MBCH UID:mbch1 X:50 Y:50 W:100 H:30 FSZ:2 PLCO:#b51d1d YASC:0 YLO:3.2 YHI:4 YTC:4\r\n'
'@mbch1 MCHL:"u1, u2, u3" MCHV:"3.2,3.42,3.54"\r\n'

The difference is YLO:3 -> YLO:3.2.
The problem occurs when the scale range is defined by floating-point numbers.
Could you please limit the number of decimal places?

Maybe it's a good idea to add a minimum value on the vertical axis?

Regards,
Hubert

kl3m3n

@Hub Hi!

I would say that it is unusual to specify decimal value for YLO, but it still is a valid option
Specifying integer values for YLO and YHI probably covers most cases.

I will see about adding the minimum value on Y axis as well as dealing with so many number of decimal places.

Thanks for pointing this out!

Best regards,
Klemen

Hub

@kl3m3n Hello!

I plan to use the widget to monitor the voltage of a series of Li-Ion batteries. The useful voltage range in this case is 2.8-4.4V.
It'll look a little weird, but the solution may be to use integers 28-44 and add the label x0.1V.
Alternatively the range could be 2-5V.
Could you add a minimum value on the vertical axis?
The range of values would be clearer.

Regards,
Hubert

kl3m3n

@Hub Hi!

Next release will include new features that will probably suit your needs... I will also update the manual (the design tool will be updated with slight delay).

A quick preview:

Best regards,
Klemen

Hub

@kl3m3n Hello!

I'm impressed. The widget looks great.
Thank you for your work.

Regards,
Hubert

Hub

@kl3m3n Hi!

I just tested the new version of the widget.
Now there is everything what I needed: defining the range of the vertical axis in floating point numbers, number of ticks on vertical axis. And even more: defining the number of digits after the decimal point on the vertical axis, displaying values above the bars.

Everything works great.
Thank you very much for this update.

Best regards,
Hubert

kl3m3n

@Hub

I am happy you find the improvements useful!

Thanks.

Regards,
Klemen