commonInit assertion causes confusion about reorderingtableviewcontroller

[shusta]

Yeah, I actually filed a radar on that. Very annoying. I think I removed it a while back but apparently didn't commit it. Oops.

-- Daniel Shusta

On Jul 1, 2012, at 1:29 AM, Jonathan Lundell [email protected] wrote:

If you instantiate a UITableViewController that contains a ReorderingTableViewController and then reference its view (in my case in order to make it a subview of my root view), that reference instantiates the tableView. In doing so, the assertion in commonInit also references the view, but apparently before it gets created, so it gets created twice. Or something like that; it's very confusing.

The original symptom I was seeing is that the tableView's reordering gestureRecognizers were disappearing. Turned out that the tableView itself was getting replaced, but with no calls to viewDidLoad/Unload, so the logic for installing our gestureRecognizers failed. I tracked it down, finally, to the assertion.

Commenting out the assertion fixed the problem. If it's really necessary, I suppose it could be safely moved to viewDidLoad.

---

Reply to this email directly or view it on GitHub:
#5