You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Though I haven't tested this super extensively, it appears that when using imported TTF fonts, the drop-down font selector in ctrlr displays using the font family metadata, rather than the actual title of the font: for example, "Lunchtype22 Light", Bold etc just display as "Lunchtype22". This becomes an issue when using multiple fonts from the same family, as they show with the same name.
When I edited the metadata of the font file itself to use the "light" designation in the family field, it displayed correctly in ctrlr.
Using version 5.6.23 on MacOS ARM.
The text was updated successfully, but these errors were encountered:
I noticed that too, ctrlr uses the metadata name on windows and the file name for mac (or the other way around). So I have to open the panel file in a text editor and search/replace font names in the xml.
Though I haven't tested this super extensively, it appears that when using imported TTF fonts, the drop-down font selector in ctrlr displays using the font family metadata, rather than the actual title of the font: for example, "Lunchtype22 Light", Bold etc just display as "Lunchtype22". This becomes an issue when using multiple fonts from the same family, as they show with the same name.
When I edited the metadata of the font file itself to use the "light" designation in the family field, it displayed correctly in ctrlr.
Using version 5.6.23 on MacOS ARM.
The text was updated successfully, but these errors were encountered: