Changes
The first full version of the icon set was completed in September 2019. The tables on this page show the icons, along with a description of their intended purpose (some have multiple), and the natural language In-App Name, and Hex code suffix, both of which can be used to call the icons using XAML.
Using XAML, Glyphs can be called in two ways. One method is to use the Hex Code, and another is the In-App Name. The Of these two below examples show how one might use both methods , the recommended method is to use the In-App Name, as it uses a natural language attribute as opposed to create a User symbolglyph code, making it more immediately apparent which icon is being requested by the code.
The two below examples show how one might use both methods to create a User symbol.
{{Attention|Notice that both of the examples make use of the <code>xmlns:controls="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"</code> namespace, and will not work unless this namespace is declared in the XAML.}}
<br>
<syntaxhighlight lang="xml">
<ctrls:GlyphLabel
Style="{DynamicResource UBIKSymbolLabel}"
VerticalOptions="Center" />
</syntaxhighlight>
<br>
====Hex Code Usage:====
In the below example, the attribute <code>Glyph=</code> and the following Hex Code is used to call the <I>User</I> icon. These Hex codes can be found using a Character Map program, or by searching through the icon tables below.
<syntaxhighlight lang="xml">
<ctrls:GlyphLabel Glyph=""" PrimaryColor="{DynamicResource UBIKLightThemeColor}" />
</syntaxhighlight>
