-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[UX] Update icons to Segoe Fluent Icons #13385
Comments
@niels9001 I've seen so many cases you always manually want to change stuff. Just let the software (OS, xaml, WinUI or whatever...) do the job for you. If the font is already installed, then it's already used. If not yet installed - imagine installing Powertoys and your OS suddenly looks different and you have no idea why or how to fix. I would be pissed!
...but it DOES! As I said earlier, on my Surface I simply installed one font and Windows uses it. Everywhere. refs: |
This comment has been minimized.
This comment has been minimized.
I don't think you're informed on how this would work: fonts can be easily embedded in the app. So we could embed ' Segoe Fluent Icons' for WPF based apps and reference it directly. We then make sure everything is consistent on W11. By using this method, we wouldn't be touching the OS. For WinUI/XAML Islands icons should fall back on Segoe Fluent Icons by default on Windows 11. Apparently it does not do that on my machine using TextBlock - not sure if this is a WinUI or a XAML Island bug, but it shouldn't happen. So without manually installing anything FontIcons (red) use the new icons - but then TextBlocks (blue) use Segoe MDL2 Assets.
|
Oh I see. You mean to use the font inside the app(s). That's not as bad as I thought. Still, shouldn't be necessary if OS = Win11, because there it is standard. Right? The FontIcon versus Textbox is a specific thing. I'mma guess this happens because in some controls the font is explicitly declared to be "Segoe MDL2". If I'm right, that's just one more example not to manual hardcode. This is why CSS was invented in 1994. It's not inside the <Button
x:Uid="EditButton"
Background="Transparent"
FontFamily="Segoe MDL2 Assets" Hm, in my head I had a "link" for that issue, but I guess I just wanted to say that there are other things that have way more priority. |
I think, if we use "System icon font" everywhere, this issue would be solved |
Is this still an issue? /needinfo |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment. |
4 similar comments
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment. |
Since Windows 11 is rolling out soon, and we're adopting more and more the new visual style, now might be a good time to start migrating icons to Segoe Fluent Icons.
For WPF applications, this means we need to embed the .ttf file as I don't believe ModernWPF will automatically select Fluent. It should for Settings, but somehow it's not doing that (probably due to XAML Islands).
We can fix #10331 while at it.
The text was updated successfully, but these errors were encountered: