Hi - I am trying to do some match with values I am fetching from WebParser. The WebParser values come through to my skin fine but the CALC measures are only returning ZERO.

Hi - I am trying to do some match with values I am fetching from WebParser. The WebParser values come through to my skin fine but the CALC measures are only returning ZERO.

You have to do two things:

Use the WebParser measure name into the Formula options of the Calc measures as section variables:

The decimals numbers provided on the site are using decimal comma, not dot. But Rainmeter uses dot as decimal separator. So add the Substitute=",":"." option to all WebParser measures ([MeasureOverall], [MeasureDeaths] and [MeasureRecovered]).

The decimals numbers provided on the site are using decimal comma, not dot. But Rainmeter uses dot as decimal separator. So add the Substitute=",":"." option to all WebParser measures ([MeasureOverall], [MeasureDeaths] and [MeasureRecovered]).

Thank you as usual Balala.

The values from the website I am gathering are as such - they are 341,000 - its not a decimal, its three hundred forty one thousand.

I've uploaded my work in progress here - with some tweaking its still not working but values of 14,751 and 14751 (with and without substitute) the CALC measure is chopping off the values to the first two digits.

CoronaCounter_.rmskin

You do not have the required permissions to view the files attached to this post.

The reasons are:
1. Substitute option has to be Substitute=",":"".
2. You have missed NumOfDecimals=x option in the [mTotalLabel] meter.Default value of the NumOfDecimals is 0, so 0.04318 and 0.28999 are both displayd as 0.

For formatting I would like to keep the original values with a comma - so I guess I can just have two MEASURES - one from the WebParser and then another one that removes the comma.

Thanks to you both. Now to work on creating a BAR GRAPH with this percentage!

For formatting I would like to keep the original values with a comma - so I guess I can just have two MEASURES - one from the WebParser and then another one that removes the comma.

Yes, this is the best approach in such a case.
Glad if you got it working well.

You are missing Substitute=",":"" in the measures [MeasureOverall] and [MeasureDeaths], so syntax errors have occurred in [decOverall] and [decDeaths]. Substitute=",":"" is not necessary in these two Calc measures.

Thanks - I have sorted it out. I am keeping display measures with the comma and then creating a String measure to hold the value without commas for calculations.

2020-03-23_20h59_43.png

This simple skin uses Chameleon to make "most" of the colors adapt to the image below the skin.

CoronaCounter_.rmskin

You do not have the required permissions to view the files attached to this post.