If you have both Scale and AutoScale on a String meter, AutoScale wins... Scale is ignored. It might look like Scale is also being applied, but that is just rounding. By default, AutoScale is displayed with one decimal point of precision and rounded. Add some NumOfDecimals and you will see that it's really AutoScale that is controlling things.

Code: Select all

```
[Rainmeter]
Update=1000
DynamicWindowSize=1
AccurateText=1
[MeasureCalc]
Measure=Calc
Formula=2000
[MeterScale]
Meter=String
MeasureName=MeasureCalc
FontSize=11
FontWeight=400
FontColor=255,255,255,255
SolidColor=47,47,47,255
Padding=5,5,5,5
AntiAlias=1
NumOfDecimals=1
Scale=1000
[MeterAutoScale1Dec]
Meter=String
MeasureName=MeasureCalc
Y=5R
FontSize=11
FontWeight=400
FontColor=255,255,255,255
SolidColor=47,47,47,255
Padding=5,5,5,5
AntiAlias=1
NumOfDecimals=1
AutoScale=1
[MeterBoth3Dec]
Meter=String
MeasureName=MeasureCalc
Y=5R
FontSize=11
FontWeight=400
FontColor=255,255,255,255
SolidColor=47,47,47,255
Padding=5,5,5,5
AntiAlias=1
NumOfDecimals=3
Scale=1000
AutoScale=1
```

1.png

So while in the second meter the auto scaling to 1.95 will be rounded to 2.0 to display with one decimal place, when you add some more decimals, you will see that it is really 1.953125. The Scale of 1000 is never used.

Scale is "fixed". If you use Scale=1024 it will simply be divided by 1024 and will always represent kbytes, no matter how large or small the number. If you use Scale=1048576 it will always represent megabytes, no matter how large or small the number. If you use AutoScale=1, then the result is based on how many "powers" of 1024 the number can be divided by, again by default rounded to one decimal place.

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