Open aaronventure opened 2 months ago
Yeah I would suggest that fiddling with the font files directly justifies a reload of HISE - that's a super niche edge case and I would prefer the benefits of keeping a font cache during the lifetime of the HISE instance.
How is it different than swapping out for another font completely? If you're trying out multiple custom fonts, you do this all the time. But when you edit one and want to see the changes reflected, it warrants a complete reload.
Expected: See edited font in use.
Observed: Edited font not in use. Quitting and reloading project loads in the new font.
Does HISE properly reload fonts on F5 compile, or does it just read metadata and ignore if same font already exists? If this impacts compile speed in any significant way, perhaps Shift+F5 could properly re-load all the font files?