Begin updates and reloaddata

The surprise comes from the fact that even if a cell was already allocated for a particular cell identfier the table view does not give you back this cell in dequeueReusableCellWithIdentifier when calling reloadRowsAtIndexPaths , instead it returns nil. In contradiction reloadData reuses the cells it already allocated. However you would need to post a bit more code to give us insight what you are doing there. In principle the indexPaths of the new cells are identical to the old ones also with reloadRowsAtIndexPaths as long as you don't delete or insert rows.

Call this method if you want subsequent insertions, deletion, and selection operations for example, cellForRowAtIndexPath: and indexPathsForVisibleRows to be animated simultaneously. I think this is what you want. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. TableView reloadData vs. Asked 10 years, 1 month ago.

Active 3 years, 6 months ago. Viewed 46k times. I got a tricky problem regarding updating my TableView, i get different results using different methods of updating it, let me explain: Situation 1: I use [tbl reloadData]; where tbl is my TableView, to update the TableView - works as intended. Improve this question. Tobias Tovedal Tobias Tovedal 2 2 gold badges 8 8 silver badges 14 14 bronze badges.

In Situation 1 the button gets the correct tag, in Situation 2 - it does not. Add a comment. Active Oldest Votes. From the UITableView documentation beginUpdates Begin a series of method calls that insert, delete, or select rows and sections of the receiver. As you can see, the final array does not match the delta changes. This will explain the video, why the first item got moved to the last item. This could seems like BKDeltaCalculator is calculating delta wrongly. But it might not necessary be the case if we consider that BKDeltaCalculator is calculating the delta from the old array to the new array.

The from index is based on the old array and the to index is based on the new array. UITableView does adhere to this convention it seems, as illustrated in the example. Lets say I remove all false positives from the delta changes. So in this case it will only generate the insertion and deletion and no move. This will definitely work nicely with ASDK until we try to reload those cells that we have moved inside the begin and end updates calls. The problem is that the order of the calls to reload, delete and insert are important.

If reload is called after delete and insert, the index of the reload will be ambiguous. In our example, reloading either the first index and last index will make UIKit complains that we tried to do 2 actions to a single cell Either insert then reload or delete then reload. This can be rectified I haven't tested it yet by making sure reload are done before delete and then insert.

In this case, it is closer to UITableView implementation where reload and delete is based on old array indices. I think the solution might be to group pending blocks of reload, delete and insert in their own array and call them in order, maybe reload, delete then insert.

Here is a gist showing my solution. I have found that the current implementations of reloadSections , reloadRowsAtIndexPaths , moveSections , and moveRowAtIndexPath do not work as expected and typically resulted in crashes. Instead of using any of those methods, I only use delete and insert operations. All the deletes must be run before any inserts. Another issue I've found is that calling either insertRowsAtIndexPaths or insertSections will lock the datasource and any further tableView updates called within the beginUpdates block will cause a datasource locked exception to be thrown.

With the gist I posted combined with RFSectionDelta everything seems to be working fairly well for my app which requires pull to refresh, infinite scroll and also cells which need to move positions.

The biggest issue I've seen so far is sometimes I still see nodes flickering in and then moving off screen. Even though minor, I think it's a bug. Now, the original discussion started with slow reload, I don't know if you guys want to keep this one as discussion and have other issues as bugs? Just as a reminder, if you are seeing issues with flashing, simply enable the.

Skip to content. This repository has been archived by the owner. It is now read-only. Star Labels Bug discussion. Milestone v1. Copy link. This topic contains 2 replies, has 3 voices, and was last updated by leela 5 years, 6 months ago. I have a jqxGrid loading from a json data source.. I changes the data on the server and want the table to update to reflect..

Using jqxGrid refresh and refreshdata does nothing for this.. What you need to do is get to the dataAdaptor you connected the jqxGrid to, and give it a. The jqxGrid will then update to reflect.