-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
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
Added db objects are not shown at the Winui3 ItemsControl loading completed. #3659
Comments
➤ PM Bot commented: Jira ticket: RNET-1173 |
I didn't test your linked project. You can bind the ItemsControl's ItemsSource directly to... public IQueryable Users => _users; ...to leverage collection change notification just like ObservableCollection. [Sent from mobile app] |
Yes, i fix it. But the problem already exist. |
I tested your updated project Here is the updated XAML
|
Hi @daniDevKr , |
I replaced |
In your updated project, you used
Try with the following code (taken from https://www.mongodb.com/docs/atlas/device-sdks/sdk/dotnet/react-to-changes/#std-label-dotnet-collection-notifications) to make sure the collection change notifications actually fires ( It correctly fires on a few machines/configs of mine, except for a [v12.0.0-v12.3.0] when compiled under x86 on amd64 Windows machine. So make sure you compile your project against x64).
Actually the notifications are triggered, which indicate it's not realm-dotnet issue but Not all list based controls behaves the same in WinUI. None play correctly with RealmCollection change notification in WPF. You can actually work around this by using the mentionned |
What happened?
Added db objects are not shown at the Winui3 ItemsControl loading completed.
Repro steps
Version
net8.0-windows10.0.19041.0
What Atlas Services are you using?
Local Database only
What type of application is this?
Other
Client OS and version
Windows 11 Pro 23H2, build 22631.3958
Code snippets
Sample code repo link: Link
Stacktrace of the exception/crash you're getting
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: