Sorry if this is a new feature that I haven’t seen yet, but it would be awesome of TMPro supported a reference font feature, similar to how you had reference atlases. Basically, I want to abstract the actual fonts used for different jobs in the UI, and be able to change those later without a huge hassle.
For example:
Reference Font “Main Text” points to “Cooper Black”
Reference Font “Numbers Only” points to “Impact”
etc.
Then later in development I may want to change the main font to a totally different font than Cooper Black, so I’d simply make a new font, then change the pointer on “Main Text” to point at the new font instead. Perhaps when changing the reference, TMPro might have a tool to create style materials for the new font that match the old font’s materials, and then they automatically get updated on all the labels too. (I realize this part is probably the biggest hurdle.)
You could sort of achieve that by creating a Style that would use the tag to specific what font asset to use. The in the Style dropdown of the text object pick your main style which points to your font asset.
When you would need to make the change to a new font asset, you would simply update the style definition to point to the new font asset where it could point to different fallbacks.
The only potentially issue that I could see with this is that the primary font asset would not be used and the text handled by a sub text object.
Test the above workflow to see if that presents any issues for you. It would be pretty clean allowing you to actually easily setup different Global or Local styles to test various combinations of font assets.
For reference this is the Style dropdown I am referencing.
I will give further thoughts to an alternative “Reference” and follow up when I have more information.
Hello! I was wondering if there was any further work on the concept of a Reference Font Asset, or is the Style route still the best way to easily swap fonts down the line across everything using that font?
