Skip to content
This repository has been archived by the owner on Feb 8, 2022. It is now read-only.

Ability to update the existing change #61

Closed

Conversation

bronenos
Copy link
Contributor

@bronenos bronenos commented Jan 9, 2016

Now it could be the wrong case for UITableView if we have addNotified object to Realm, and then notifyUpdate on it, inside one function.

Here is a little attempt to fix that.

@polqf
Copy link
Owner

polqf commented Jan 12, 2016

Could you paste a snippet showing which is the problem you are trying to solve?

@bronenos
Copy link
Contributor Author

Well, it's hard to extract the exact snippet from my project.
But I had some problems about cells from section #1 were displayed in section #2.

And then I discovered that I created object (which initially should be displayed in one section) and then updated that object the way it should be moved to another section. For example: create the person, addNotified, changed his name, notifyUpdate.

But the problem is actual for me when there are >100 objects those have updates during the runloop cycle. Not the single object.

These steps were executed during one runloop cycle.
And this bug was fixed for me with current PR.

And also it's hard for me to create the testing project.
Because I have a very bit of free time. Sorry. :(

@polqf
Copy link
Owner

polqf commented Feb 11, 2016

Closing it as should be covered by #67 , feel free to reopen or create an issue if necessary

@polqf polqf closed this Feb 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants