Code: Select all
[Variables]
[Rainmeter]
Update=1000
DynamicWindowSize=1
AccurateText=1
BackgroundMode=2
SolidColor=47,47,47,255
---Measures---
---Meters---
[MeterTest]
Meter=STRING
X=0
Y=0
FontFace=Consolas
FontColor=255,255,255,255
SolidColor=47,47,47,255
Padding=5,5,5,5
FontSize=16
AntiAlias=1
MeasureName=MeasureTest
Text="Test = abc "
DynamicVariables=1
On the other hand, if one adds another character, even a zero-width space character like [\x200B] at the end of the Text option's string, the meter / skin won't trim the "trailing" spaces anymore (well, technically they're not trailing in this case, since they precede the [\x200B] character).
Preview: Now, while this couldn't exactly be classified as a "bug", but rather as a "feature" (it should be mentioned in the manual though, as a small note), I'm interested in something else: would this "feature" be persistent in future Rainmeter versions, or it could be subject to change depending on, say, an actual bug report? I'm asking because I think about using this "feature" in my skins, in order to avoid creating duplicated variables just because of a few trailing space difference between some similar strings used in different contexts, and I need to know if I can rely on this behavior in the future or there is a possibility of another Rainmeter version breaking this behavior (and hence, my "trick").