Posts

Post marked as solved
4 Replies
Just a follow up. I scoured the code and found several duplicated lines of code that were being executed multiple times that changed the state of the tableview. Once I reduced those and refactored the reloading to reload the only section of the table, this issue cleared up.Thanks!
Post marked as solved
4 Replies
Thanks a bunch for this answer. After I posted this, I was reading about how reloadData effects a lot of things, so I put a bunch of NSLog statements in close proximity to the reloadData statements and still couldn't pin down where editing was being turned off. I am in favor of replacing the reloadData calls since I don't believe it necessary to do this as much as the code does, which is a lot. I am going to try that next.As far as a rewrite, that's just not in the cards at this time due to time and budget constraints. We have a future project to convert this project to Swift, so there is hope I'll get back to it in the near future.Thanks again!