Imagine you have a counting calc or loop measure that operate within a certain number range. (1-100)
But you need a different range of numbers for a animation elsewhere in the skin (0-255), but synced to the first measure.
Instead of creating measures for each and every little thing, you can convert (1-100) to (0-255) with a formula.

Good point, but I have a suggestion here.
In such cases, when you're using the calculated value into an option which needs integer value (like ImageTint or FontColor), I'd round the calculated value, using a Round function. For example in the code of the uploaded skin, I'd replace the existing FontColor option of the [Text] meter (FontColor=255, 255, 255, (([MeasureRange] - #in_min#) * (#out_max# - #out_min#) / (#in_max# - #in_min#) + #out_min#)) with something like the following one: FontColor=255,255,255,(Round(([MeasureRange] - #in_min#) * (#out_max# - #out_min#) / (#in_max# - #in_min#) + #out_min#)).
Yes, this doesn't have too much importance, because in such cases, the not integer value is converted to integer, but just to be a little bit more precise.

Good point, but I have a suggestion here.
In such cases, when you're using the calculated value into an option which needs integer value (like ImageTint or FontColor), I'd round the calculated value, using a Round function. For example in the code of the uploaded skin, I'd replace the existing FontColor option of the [Text] meter (FontColor=255, 255, 255, (([MeasureRange] - #in_min#) * (#out_max# - #out_min#) / (#in_max# - #in_min#) + #out_min#)) with something like the following one: FontColor=255,255,255,(Round(([MeasureRange] - #in_min#) * (#out_max# - #out_min#) / (#in_max# - #in_min#) + #out_min#)).
Yes, this doesn't have too much importance, because in such cases, the not integer value is converted to integer, but just to be a little bit more precise.

Astute observation balala, sharp as always ;P
I have updated the skin and documentation with your suggestion.
Thank you