public static class SystemFontsFinds a face to draw with on whatever machine this is.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
⚠ Borrowed from the operating system, which is a starting point and not a shipping answer. An application that ships decides what it looks like: it carries its own face as an asset and registers it against UiDocument.Fonts itself, because "whatever Arial the machine happens to have" is not a design. This is what a sample does, what a freshly scaffolded application does on its first run, and what an application does before its own asset has loaded.
Nothing found is not a failure. A machine with none of these leaves the document with no face, every label measures zero, and the controls draw their boxes and their chrome exactly as before — which is worth knowing about the framework as well as convenient here: text is a thing an element has, not a thing the layout requires.
This existed three times before it existed once: Samples/02-HelloUi's Fonts, the vixen-app template's AppFonts, and — with a committed face in front of it — Vixen.Editor.App's Fonts. The three candidate lists had already begun to differ.
Methods (2)
public static bool Install(UiDocument document)Registers a face as the document's default, if one can be found.
public static IEnumerable<string> Candidates()Where a plain TrueType UI face tends to live, best first.
Used by (1)
- UiApplicationVixen.Ui.Desktop