-
Notifications
You must be signed in to change notification settings - Fork 70
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
Support Realm 0.98's fine grained notifications in some way #66
Comments
@crsantos literally working on this right now. It will prevent the need to use the custom notification handling with |
Sorry, mis-clicked and forgot to paste the rest of the question :D |
@crsantos well scratch my first idea, I don't think I can drop |
As a result, using the collection notification in exchange for the current Realm notification in |
Realm is getting close to launching true fine grained notifications that include specific object changes, which then can be incorporated into RBQFRC. Once that is released RBQFRC will be irrelevant unless you want its sectioning ability. Realm doesn't yet support groups, so the index changes off its upcoming fine grained notifications will only be based on 1 section, but RBQFRC can fill in the gaps there. Until then, I think I am just going to leave things as is. |
Thought about that performance tradeoff too. Maybe it's better to leave it as it is: using the mark as dirty approach. Let's hope Realm launches that quickly :) |
Any update on this? |
This is more likely a doubt than an issue. So please tag it accordingly.
I don't know if this makes sense but, is there any improve if we use the new Collection Notifications from Realm's 0.98?
I'm just asking you that you have the know-how about this codebase so is it worth trying to use those notifications?
Thanks
The text was updated successfully, but these errors were encountered: