Closed ghost closed 8 years ago
The full edit set are supported - insert, append and delete - so you don't need to reset it to update :-)
Sent from my iPhone
On Aug 14, 2016, at 7:54 AM, james-lavery notifications@github.com wrote:
Now this may be a stupid question bearing in mind we're talking about an ObservableCollection...
I'm displaying records from a table with potentially 1000's of records in my database table - all working really well regarding virtualisation, paging etc.
However, other processes can cause the data in the database table to be updated. Is there a built-in mechanism for Refreshing the data, rather than Resetting it?
My core data layer routines (using SQLite-Net) return IEnumerables, not ObservableCollections.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
Thanks - I understand that the full CRUD set is supported by my process. However I have another thread running which can update the DB and can raise an event or send a message to notify of the update.
Is there a mechanism to refresh/reset and then navigate to the same current page/record?
Sent from my Android phone using Symantec TouchDown (www.symantec.com)
-----Original Message----- From: anagram4wander [notifications@github.com] Received: Sunday, 14 Aug 2016, 23:42 To: anagram4wander/VirtualizingObservableCollection [VirtualizingObservableCollection@noreply.github.com] CC: James Lavery [james.lavery@microsec.co.uk]; Author [author@noreply.github.com] Subject: Re: [anagram4wander/VirtualizingObservableCollection] Refreshing when data has been updated (#13)
The full edit set are supported - insert, append and delete - so you don't need to reset it to update :-)
Sent from my iPhone
On Aug 14, 2016, at 7:54 AM, james-lavery notifications@github.com wrote:
Now this may be a stupid question bearing in mind we're talking about an ObservableCollection...
I'm displaying records from a table with potentially 1000's of records in my database table - all working really well regarding virtualisation, paging etc.
However, other processes can cause the data in the database table to be updated. Is there a built-in mechanism for Refreshing the data, rather than Resetting it?
My core data layer routines (using SQLite-Net) return IEnumerables, not ObservableCollections.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/anagram4wander/VirtualizingObservableCollection/issues/13#issuecomment-239702343, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABrKHtkecj3fJZYO1aiwdGxu439gSPycks5qf5nZgaJpZM4Jj6fx.
Ah - I see that current page/location are maintained when resetting. Perfect.
Now this may be a stupid question bearing in mind we're talking about an ObservableCollection...
I'm displaying records from a table with potentially 1000's of records in my database table - all working really well regarding virtualisation, paging etc.
However, other processes can cause the data in the database table to be updated. Is there a built-in mechanism for Refreshing the data, rather than Resetting it?
My core data layer routines (using SQLite-Net) return IEnumerables, not ObservableCollections.