[BUG]Raimeter crashes when using a specific font

[death.crafter]

With Windows Insider Preview Build 21376, Microsoft added a new font family to Windows named Segoe UI Variable. So when I try to use the Segoe UI Variable Display Semibold typeface, Rainmeter crashes. There are no logs generated so I can't attach them. But here is the font file. You can try it for your self.

Segoe UI Variable:

SegUIVar.zip

[eclectic-tech]

This works for me without crashing.

Code: Select all

[MeterString]
Meter=String
FontFace=Segoe UI Variable
FontWeight=600
Text=Segoe UI Variable Semi Bold

There is only one Family name "Segoe UI Variable" and you can set as Semi Bold using either FontWeight or InlineSetting. InlineSettings

[death.crafter]

This works for me without crashing.

Code: Select all

[MeterString]
Meter=String
FontFace=Segoe UI Variable
FontWeight=600
Text=Segoe UI Variable Semi Bold

There is only one Family name "Segoe UI Variable" and you can set as Semi Bold using either FontWeight or InlineSetting. InlineSettings

Actually the problem here isn't that. I know how to do it. It's just that all the other typefaces in the mentioned font family work perfectly. Just the Semibold one crashes Rainmeter. I thought it was worth reporting since Microsoft is planning to make Segoe UI Variable default(not certain, just mentioned in flight notes).

[Brian]

I am assuming you used FontFace=Segoe UI Variable Display Semibold instead of the "preferred" family name of FontFace=Segoe UI Variable as eclectic-tech suggested?

Either way, this shouldn't crash Rainmeter. The problem stems from attempting to create a font object similar to our old rendering system (GDI+). The conversion functions only accept a "type face" name that is less than 32 characters long. We didn't take this into account, which is understandable since the vast majority of fonts do not have that long of names. Since these are Windows API functions, the FontFace option will truncate to 31 characters in some cases.

Anyway, the problem has been fixed. Thanks for reporting!

-Brian

[eclectic-tech]

I didn't have the entire font family on my system to test, so thanks for reporting death.crafter.
As always, thanks for the explanation and fix, Brian.