robloo

Instead of InputBindings in might be good to look at the 'updated' concept of KeyboardAccelerator from UWP. https://docs.microsoft.com/en-us/windows/uwp/design/input/keyboard-accelerators https://docs.microsoft.com/en-us/windows/uwp/design/input/keyboard-interactions Oh, and then there is gestures for special touch input :)

Ironically, the ability to materialize flyout content before it's shown would solve an issue with the color picker control itself. This is a serious control lifecycle limitation that there are...

Yea, we should allow a way to set one or more string value to `Classes` directly. The existing syntax was kind-of hacky as well. However, I don't have a good...

> I think it can be usefull to have the NamingConvention option to specify, how the enum value must be converted to class name (PascalCase, camelCase, kebab-case, snake_case, or custom)....

I am referring the XAML variant of XML. Microsoft follows the same conventions as C#/.NET there for obvious reasons -- so the object model maps 1-to-1 -- same names, same...

Can this be done in the next WinUI 3.0 preview? Seems very simple to do and would close a few issues and help people porting from WPF.

It was always strange to me this wasn't supported. I just worked around it and moved on. It's nice it's added now for XAML compatibility!

Should the new constructor be an IDictionary interface rather than concrete class?

So a summary of reasons `Icon` (at least FontIcon, PathIcon, BitmapIcon etc.) are needed in my opinion: * Improved compatiblity with WinUI * Forces a sorely needed standardization in Avalonia:...

@Splitwirez Yes, `SymbolIcon` (as implemented in UWP) is very similar to a FontIcon. However, you do not manually specify the glyph as a Unicode value. Instead, you specify the symbol...