[Bug] FontWeight=0 error log

[Virginityrocks]

Using FontWeight=0 causes errors in the event log.

[balala]

Using FontWeight=0 causes errors in the event log.

I don't think this would be a bug. If you read the first sentence in the FontWeight option, its range is from 1 to 999. If you're out of this range, you get an error. Somehow normally.

The weight of the font in the range 1-999.

[jsmorley]

Correct. Do not use FontWeight to attempt to "hide" a meter.

in the world of fonts the weight just can't be "0", and it does not make sense to force / default an invalid FontWeight to "100" or "400" or "800" or anything really, as not every font always supports ANY particular weight value. Any default value will be making an assumption about both your intent and the font metrics that we can't legitimately make, so we produce an error if the value is below 1 or above 999, and throw the option away.

"1" means "lightest possible", "999" means "heaviest possible". We can't assume that "0" means anything at all. It can just be a broken formula. We need to warn you of broken formulas...

If you are using a formula to calculate a FontWeight, use Clamp() to ensure it can't be below 1 or above 999, or a ternary formula to force it to "400" or something if it is out of range. This is particularly important as using a dynamic #Variable# or (formula) as the value implies that DyanmicaVariables=1 will be on the meter, and that will cause the error to flood the log.

[Virginityrocks]

I suppose so. I guess I should have read the 1 to 999 bit. I figured the range started from 0 up. Thanks.