Font loading behavior is very inconsistent
X-posting this from the thread that Nevcairiel started at http://us.battle.net/wow/en/forum/topic/20743805540
Including Nev's post for context: Quote:
There is indeed something very strange going on. I also tested with SUF, but in theory it should be the same with any addon that uses AceGUI-3.0-SharedMediaWidgets for its font config. Here's what happens for me: My own addon, TellMeWhen, does not use AceGUI-3.0-SharedMediaWidgets for its font config - it uses its own dropdown which display the available fonts in an essentially identical way. Both LSM widgets and TMW's config set their fonts by calling fontString:SetFont(fontFile, ...). When I open TMW's font dropdown, only a small handful of fonts show up with the correct font face - the ones that are correct seem to be all the ones that I use elsewhere in my UI. The rest show up with a default font face. Opening it repeatedly ( :SetFont() is called each time it is opened on each item in the list) does not change the results. However, when I open SUF's config and open its font selection dropdown, the game freezes for a split second while the fonts are loaded, and then the dropdown appears with all fonts using themselves for their listing. When I go back to TMW, all the fonts are suddenly showing up correctly. It seems that there is some condition under which when you call :SetFont(), the specified font face will not be loaded, neither immediately nor once the FontString actually needs to be rendered. For reasons that I cannot determine, LSM Widgets seems to be doing this "correctly", but I am not doing it "correctly" in TellMeWhen. However, this goes against what Nev is reporting - LSM Widgets in SUF's config is not working correctly for him. So, I really can't begin to guess what the issue might be since we're seeing different behavior in the exact same library/addon combo. |
The pointers are probably messed up with the new fileID system.
|
My issue was long fixed in a build long ago, FWIW.
|
Ok. It sounded like it could have the same root cause as my issue, but I guess not. My issue still persists. :confused:
|
All times are GMT -6. The time now is 12:15 AM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI