Allow setting of static FontFamily within Fonts class to allow using custom otf reference for WPF apps about fontawesome5 HOT 7 CLOSED

Hi, thanks for the details information. I will try to fix it or provide a way to change the font family paths.

from fontawesome5.

Hi,

ok i committed a fix in develop, where you can adjust the Font families in the Fonts class. I provided as well another way to reference the Fonts through a ResourceDictionary (see Readme.md), which was mentioned in the ticket you posted.

It would be great if you could give me feedback, if this fix worked for you.

from fontawesome5.

Hi Martin,

It took me some time to test, as our application is wired into the pro version. But I can confirm that with these changes I am able to use configuration to derive a path to the physical files.

The only issue I came across was the context from which we are loading, whereby we have a forms application hooking in some WPF views which meant that I needed to add the following code:

if (Application.Current == null)
{
    new Application();
}

It might be beneficial then to just add some Application.Current null checks in those Typeface getters.

When I remapped to using the Free version, remapped icon usage to accommodate and added the application initialization to set the current application:

Out of the Box - Loads from library

_ With Resource Dictionary _ - Loads from library

_ With Helper to set Fontfamilies _

So having this facility is great as it means we can have a path defined in configuration for the files and be able to set those absolute paths to the fonts and circumnavigate this strange issue.

Thank you very much for looking into this and getting a solution for us so fast.

As we are using the Pro Version, will this be incorporated into that build in the near future?

from fontawesome5.

Hi, ok this means the ResourceDictionary solution did not work at all. I removed it. I improved the Fonts class with some static functions for saving the Resource files to any directory (Fonts.SaveFontFilesToDirectory) and a function for setting the Font Families to load from a specific directory(Fonts.LoadFromDirectory).

Now the Fonts static constructor will save the otfs files to the users temporary directory and load it from there, as default behaviour. I kept a Fonts.LoadFromResource method to activate the old behaviour, if it gets fixed.

I will copy these changes over to the FontAwesome5.Pro repository.

FYI: I added an ImageSourceSvgConverter, which uses the SVG information instead of the font. This should solve the problem as well.

Thanks for the great help. :)

from fontawesome5.

I updated the develop branch in FontAwesome5.Pro with the changes.

from fontawesome5.

Thanks again Martin, completely forgot to test the SvgConverter as well, ill give that a whirl tomorrow and let you know how it goes.

from fontawesome5.

Just tried the ImageSourceSvgConverter and it works brilliantly:

from fontawesome5.