I wanted to be able to print exactly 'n' digits (in my case, 3), regardless of what the value of the number is. E.g., if the measure value is "155551", it would print "156 K"; if it's "15551", you would print "15.6 K"; and if it's "1551", print "1.55 K", and so on and so forth. The problem is, this is not easy to do in rainmeter! As you will see, this is not for the faint of heart.
In this example, there are a few things to note:
I consider 1 KB to equal 1024 bytes (you can change a few constants if you want it the other way 'round).
There is a substantial delay, because calc measures lag behind a cycle, and I use several tiers to accomplish this.
This is an example that uses cumulative network download as the "parent" measure.
Certain style elements MUST be correct for it to display properly, and they are highlighted.
The names are not very descriptive, so change them to your liking.
This is very ugly but I don't know of a better way to do it.
CalcThreeA figures out when we need to divide, and returns our exponent for our divisor.
CalcThreeB returns the scaled value of the parent measure.
CalcThreeC returns the suffix (KB, MB, etc.).
CalcThreeD returns our first digit after the decimal point (assuming we have one), as well as adding in the decimal point itself.
CalcThreeE returns the second digit after the decimal point if we have one.
CalcThreeF returns the primary value (0-999).
There's no easier way I can think of doing this, because of how rainmeter prints measures in the string meter. It treats them as a number, prints them, and then does the substitution after they've been printed. The thing that makes this so hard is that you can't set the decimal places dynamically and use AutoScale, because the NumOfDecimals is read when the config is loaded and never again (aside from refreshes/restarts, obviously). So, if you change it, it has no effect, and you have to approach it through this roundabout way. Also, you can't use separate NumOfDecimals for each individual measure in your meter--the setting is meter-wide. Worst part is you need this many calcs for each value you want to scale. Perhaps rainmeter can add this option as a feature in the future so we don't need to use such an ugly method?
Anyway, enjoy, and let me know if you think of any improvements.
Edit: There are some bugs in this, where some rounding leads to "10" for a digit. I'm working on fixing it and I'll update the post when done. Edit2: Fixed so it will always print 3 digits, but no more rounding as a result (e.g. 10239 bytes will round to 9.99 KB instead of the ideal 10.0 KB)
