WindowsCommunityToolkit | Windows Community Toolkit is a collection | Runtime Evironment library

I'm using the UWP Community Toolkit Expander in my App. I'd like to be able to disable the expansion of the control (so it doesn't expand when clicked when certain criteria are met).

Ideally this would hide the expander arrow or make it grey as well as stopping the expansion from happening.

I could fork the code and make the necessary changes, but I was wondering if there are any simpler ways to achieve this?

Thanks in advance.

The issue is continued in WindowsCommunityToolkit repo: https://github.com/windows-toolkit/WindowsCommunityToolkit/issues/3949

TL;DR - See bold text in description.

As seen in the gif below, the mouse/cursor is on the grid splitter until the grid-splitter collides/stops. The mouse/cursor will continue to move outside, which is correct. Now, when I move the mouse back, the grid-splitter is moving without having the cursor fixed to it (the grid splitter is based on mouse movement and not mouse position). So, what I want is for the cursor/mouse to always be on the grid-splitter when is moving.

I'm trying to customise the header content of a UWP DataGrid. I can add the necessary controls by changing the header style like this, however I want to be able to bind the controls inside the template to instances of a class that are only available when the grid columns are (dynamically) created.

How do I make the binding in the code below valid (or another workaround)?

DataGrid example XAML:

I successfully bind two ToggleButton's to an ObservableCollection, the button's IsChecked state is where I get a problem:

XAML:

Web-scraping with PowerShell Issue: My code won't pull in the needed information. Why?

My code up to this point will pull the correct information. the info it shows is:

Currently when Microsoft.Toolkit.Uwp.UI.Controls.InAppnitification shows up, it always comes from botttom to top. But it's weird when I set the InAppnitification's VerticalAlignment to Top.

So is there any example to redefine it's coming in direction.

Also, I have post a feature request on Github. If you want it, please vote.

I need something like this: AdvancedCollectionViewControl which is from the UWP community toolkit and I can get it all working for a custom ICollectionView except they don't have Grouping implemented.

I need an ICollectionView that does Filtering, Sorting and Grouping so I can Bind it to a UWP ListView that does grouping and has a SemanticZoom control. This does not exist in UWP

How could I take the UWP toolkit example and get the "public IObservableVector CollectionGroups property working so it will do grouping? I would just use CollectionViewSource except I need the added sorting and filtering capabilities.

The documentation says to use the ICollectionViewGroup interface on items that will be stored in the IObservableVector CollectionGroups property; I can't find any example or how to implement this. Here is all the documentation Microsoft has: https://docs.microsoft.com/en-us/uwp/api/Windows.UI.Xaml.Data.ICollectionViewGroup?view=winrt-18362

Put simply as I can, I need an example on how to implement the ICollectionView interface with grouping. If you don't know how to do this then please, don't comment.

Following the response on this windows-toolkit issue, I'm using x:Bind to bind elements of an ObservableCollection of AlertEntry's to DataGridColumn cells. My XAML is as follows:

I've been trying to implement the MasterDetailsView from the UWP Community Toolkit, with very little success. I mirrored the SampleApp source code with my own classes, and could not get the List I was using to display in either the Master or the Details panes. Finally, I tried creating a new project in VS, and copying the source code listed in the SampleApp exactly, using the same Email class as the Sample App uses. Despite copying everything perfectly, I get the same results.

I noticed several binding errors (shown below) in the Output window of VS which point to this being a binding issue, but as far as I can see I've followed the normal binding format that I've used on other applications and with other controls.

Error example: