finestructure
commented
12 years ago Ok, the reason is that the timestamp can be identical if two shots are taken within the same second. The view can then return the rows in different order between updates. Need to make sure the order is always the same, probably by including the image_id in the key
Situation: With the dummy service, take two images in short succession, index 0 and 1 in the table view. Now, index 0 will get both updates (modified cell animation) while index 1 remains blank. After a full reload (stop and restart app), display is in order. That means the underlying data is ok, it's just the wrong cell getting the reload command.