Re: icon styling in an aesthetic sense, all the glyphs referred to by the v1 styles are already sourced from Fluent UI System Icons in the current font, so nothing should change there. Apps really don't want to mix-and-match from a design perspective. The design language between Segoe Fluent and Segoe MDL2 is drastically different. I think the reason would be that v2 styles and V1 styles have different border thickness/corner radii and the icon styling also matches a specific version. The following table of glyphs displays unicode points prefixed from E7- to E9-.X:Key="SymbolThemeFontFamily">ms-appx:///Assets/Fonts/WinSymbols3.ttf#Regular Likewise, since all of the new icons are sized and positioned the same, they do not have to be made with zero width we have made sure they work as a set. This means that some older "tricks" like the progressive disclosure arrows no longer apply. Icons in the Segoe Fluent Icons font are not intended for use in-line with text. This is useful when creating a symbol font, but it creates an interoperability problem when Segoe Fluent Icons is not available. The PUA range is a non-standardized range of Unicode that allows font developers to define their own characters. Most of the icons included in the Segoe Fluent Icons font are mapped to the Private Use Area of Unicode (PUA). Segoe MDL2 Assets will still be available, but we recommend updating your app to use the new Segoe Fluent Icons. With the release of Windows 11, the Segoe Fluent Icons font will replace Segoe MDL2 Assets as the recommended symbol icon font.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |