Vincent
Vincent
Agreed. We are actually using the following converter function in our code when binding our .Net standard VM to the UI. This allows us to only expose standard types from...
@Hot-Gun, the sample page is very basic. It only uses `Add()` because it was simpler to showcase the behavior of the `ObservableGroupedCollection`. Since it mostly just wraps an `ObservableCollection`, it...
This issue also happen with the system XAML.
I don't have this need yet 😊, but I agree that we can use `InfoBar` as the base brick for the `InAppNotificationControl`. `InfoBar` has an `IsIconVisible` property to control if...
I've tried with a basic xUnit test project. And everything stops to work as soon as I'm adding `x86;x64;arm64`. It seems to be more an AOT+xUnit issue than a csWinRT...
If I just have mstest tests, everything is working
I've opened https://github.com/xunit/xunit/issues/3219 in xUnit repo. I'd like to avoid to convert all our (UWP) tests to MSTests, we have too many of them 😅
It should be easy to combine the two. The `SelectorBar` would provide the "tabs" and the `Ribbon` the buttons.
@Tartarusome The reveal effect is on the `GridViewItem`s from the `GridView` used in the "Advanced" group in the sample. Since there is no custom style on those `GridViewItem`, they are...
I think I've found the root cause of the issue: `SplitButton` is not considering the `KeyDown`/`KeyUp` events as a sequence. The `Click` event is triggered for any `KeyUp` event (if...