Verel Pode

# An analogy with the Image Control `Windows.UI.Xaml.Controls.Image` defines these `Source` and `Stretch` properties: ```cs public class Image : ... { public Windows.UI.Xaml.Media.ImageSource Source { get; set; } public Windows.UI.Xaml.Media.Stretch...

Hi @kikisaints, thanks for the quick reply. > IconSource's API structure/behavior is inconsistent with that of similar components, like Image and ImageSource. Correct. > Subclassing IconSource to Bitmap/Symbol/Font/PathIconSource all result...

# Library of icons in app (re ResourceDictionary) I remembered another important part of this issue. When using `PathIconSource`, obviously every app needs to store a collection of all the...

# Classes were not updated for IconSource When the `IconSourceElement` and `IconSource` classes was created in WinUI in order to replace the defective `IconElement` subclasses, unfortunately various other classes were...

# Icons in "Visual Assets" in manifest On the topic of icons, unfortunately I also had a disappointing experience when configuring the icons in the "Visual Assets" tab in the...

On a few occasions in the past, I produced amateurish work, but I'm proud to say that I revisited my work and transformed it from amateurish to professional, and the...

@moshegutman -- Oh yes, "unplated" is another problem; thanks for reminding me. I can explain "unplated". Surprisingly, the newly-invented term/jargon "unplated icon" means "a normal icon" in the normal sense...

Here are a few more things that are unfortunately bungled in "Visual Assets". Firstly, imagine that I wrote an app and in my app there is a place to choose...

Unfortunately I still haven't finished the substantial work of documenting the list of defects in "Visual Assets" :frowning_face: In the following screenshot, you can see that I've set **"Tile background"**...

I've saved the best for last. Here is the number 1 most absurd thing about the current version of "Visual Assets". When you use "Asset Generator" with its "Recommended Scales"...