Icons don't warn about Win10 not supported about winui-gallery HOT 13 OPEN

Thats a good point, would you expect there just to be a "Windows 10" disclaimer or also depending on the Windows build when it was available?

from winui-gallery.

It's called out in the Expander.

But I agree, it doesn't jump out.

Maybe we could add an InfoBar at the top calling this out and warning folks that some icons might not render at all and testing is required?

from winui-gallery.

That message isn’t helpful. Many of the icons do work on Win10 but not all. I’d like to see the warning in the icon detail when you select an icon that isn’t available in win10

from winui-gallery.

Interesting. I wasn't aware some icons wouldn't be available in the MDL2 font. I wonder how many of them are missing. In my opinion, I think the code area (for the specific icon)would be the most appropriate place.

from winui-gallery.

If they are on this page they are supported: https://learn.microsoft.com/en-us/windows/apps/design/style/segoe-ui-symbol-font
If they are on this page, Windows 11 is required: https://learn.microsoft.com/en-us/windows/apps/design/style/segoe-fluent-icons-font

from winui-gallery.

If they are on this page they are supported: https://learn.microsoft.com/en-us/windows/apps/design/style/segoe-ui-symbol-font
If they are on this page, Windows 11 is required: https://learn.microsoft.com/en-us/windows/apps/design/style/segoe-fluent-icons-font

Technically, it's not about the OS, but a matter if the Fluent font is installed. Important difference.

from winui-gallery.

As you said: Technically. In practice though it'll catch developers out.

from winui-gallery.

Yes, there is a clear correlation between the two. But when the Fluent font is installed on Windows 10 (which is super easy) a message calling out the OS would be invalid. Just trying to keep it accurate.

from winui-gallery.

But when the Fluent font is installed on Windows 10 (which is super easy)

Define "super easy". You shouldn't be expecting your users to be doing this. If anything you should include it in your app, but it's still worth pointing out that there's something you need to do and be aware of if you want to use those symbols on Windows 10.

from winui-gallery.

If I may suggest:

from winui-gallery.

Define "super easy"

It's literally as simple as installing the font. The OS will pick it up automatically 🙂 But indeed, this is not so common. I emphasize that the core of your issue is valid!

from winui-gallery.

No you don’t just do that. You need to build an app installer that does this. That’s not “super easy”. Again apps shouldn’t require people to do this themselves just to use the app. And that still doesn’t change the fact that someone needs to know they need to ensure this font is available. If it’s not installed all you get is a place holder icon and a poor app experience

from winui-gallery.

Wait. My comments were based on old ideas. Back when Project Reunion wasn't renamed yet, there was a font (file) that basically acted as MDL2v2. I once installed it and, because of the same internal name, Windows 10 picked it up as the System Icon font. But that's long ago and will not work nowadays. Apologies. 🙇🏻‍♂️

from winui-gallery.