We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am just converting and app from C#/WPF to C#/UWP (Windows 10) and it seems that IList does not update the UWP ListView.
So first question - should it ?
and if not then how should I bind the IList property to ensure the ListView will update if items are added or removed?
Maybe some more context - new items are getting created on a background thread - and the exact same method/code seems to work fine with C#/WPF.
<ListView x:Name="siteListView" SelectionChanged="SiteListView_SelectionChanged" DataContext="{x:Bind _this}" ItemsSource="{x:Bind Customer.items, Mode=OneWay}" > ...
public class Customer : RealmObject { [PrimaryKey] public string id { get; set; } = Guid.NewGuid().ToString(); public string name { get; set; } public string address { get; set; } public string contact { get; set; } public float complianceScore { get; set; } public string completionStatus { get; set; } public IList<Site> sites { get; } }
The text was updated successfully, but these errors were encountered:
This comment goes into a little bit of detail why this is happening: #1759 (comment). I'll close this as a duplicate of #1759.
Sorry, something went wrong.
No branches or pull requests
I am just converting and app from C#/WPF to C#/UWP (Windows 10) and it seems that IList does not update the UWP ListView.
So first question - should it ?
and if not then how should I bind the IList property to ensure the ListView will update if items are added or removed?
Maybe some more context - new items are getting created on a background thread - and the exact same method/code seems to work fine with C#/WPF.
The text was updated successfully, but these errors were encountered: