An Iconic Disaster
WinUI has delivered innovative and impressive new GUI elements, designs, and techniques, and the WinUI team has implemented many clever improvements. But of course, nobody is capable of 100% pure perfection, so some deficiences must exist in WinUI. So now I'd like to talk about a glaring exception in the impressive track record of WinUI; an area desperately in need of improvement: Icon rendering in WinUI hardly works -- it's a disaster currently. Icons are a very important topic, considering that most apps uses multiple icons in multiple places in multiple kinds of GUI elements (icons in buttons, toolbars, menus, tabs, standalone, etc). Thus it's really surprising to observe that, currently, icon rendering hardly works in WinUI/UWP unfortunately. Considering the extreme ubiquity of icons in apps, I consider this to be a **high priority** topic. # Use a PNG image as an icon? For starters, look at a really simple case where you have an instance of `Windows.UI.Xaml.Media.Imaging.BitmapImage` that was produced from a PNG, and you want to use this PNG `BitmapImage` as an icon. This should be super simple, right? But no, unfortunately neither `Windows.UI.Xaml.Controls.BitmapIconSource` nor `Windows.UI.Xaml.Controls.BitmapIcon` support the ability to render a specified **instance** of `BitmapImage` -- surprising but true. To use your `BitmapImage` **instance** as an icon, you are forced to use `Windows.UI.Xaml.Controls.Image` to render it because `BitmapIconSource` c
Posted by verelpode on Oct 24, 2019, 11:27 PM
Tags
Related issues
- He is not weirdly political, he has just more normal views, I know that is something hard to grasp for some tech bro.
- Of course you don't have a right to murder anyone.
- Unify Control and Container nodes, allow children to pick the behavior
- I was talking about this the other day with someone - broadly I agree with this, they're absolutely fantastic for getting a prototype so ...
- In theory you could express most things as a flowchart but the complexity of doing that quickly escalates.
- It's not really hard to onboard new engineers with Scala, Clojure or even Ruby backgrounds.
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
ux (EdTech)
He is not weirdly political, he has just more normal views, I know that is something hard to grasp for some tech bro.
Of course you don't have a right to murder anyone.
Unify Control and Container nodes, allow children to pick the behavior
I was talking about this the other day with someone - broadly I agree with this, they're absolutely fantastic for getting a prototype so ...
In theory you could express most things as a flowchart but the complexity of doing that quickly escalates.
It's not really hard to onboard new engineers with Scala, Clojure or even Ruby backgrounds.
Very understanding (or even no) partners is probably a large percentage of it!
Consider treeshaking module for serving files in dev mode
An Iconic Disaster
WinUI has delivered innovative and impressive new GUI elements, designs, and techniques, and the WinUI team has implemented many clever improvements. But of course, nobody is capable of 100% pure perfection, so some deficiences must exist in WinUI. So now I'd like to talk about a glaring exception in the impressive track record of WinUI; an area desperately in need of improvement: Icon rendering in WinUI hardly works -- it's a disaster currently. Icons are a very important topic, considering that most apps uses multiple icons in multiple places in multiple kinds of GUI elements (icons in buttons, toolbars, menus, tabs, standalone, etc). Thus it's really surprising to observe that, currently, icon rendering hardly works in WinUI/UWP unfortunately. Considering the extreme ubiquity of icons in apps, I consider this to be a **high priority** topic. # Use a PNG image as an icon? For starters, look at a really simple case where you have an instance of `Windows.UI.Xaml.Media.Imaging.BitmapImage` that was produced from a PNG, and you want to use this PNG `BitmapImage` as an icon. This should be super simple, right? But no, unfortunately neither `Windows.UI.Xaml.Controls.BitmapIconSource` nor `Windows.UI.Xaml.Controls.BitmapIcon` support the ability to render a specified **instance** of `BitmapImage` -- surprising but true. To use your `BitmapImage` **instance** as an icon, you are forced to use `Windows.UI.Xaml.Controls.Image` to render it because `BitmapIconSource` c
Comments (0)
No comments yet. Start the discussion.