Re: UITableView -reloadData woes

2016-02-12 Thread diederik
Have you tested the sequence in which these events occur? Does the reallocate method return before the data model has been updated (or its updating has completed?). Just log when the reloadData method starts and log when updating the data model finishes. Maybe the latter happens later than the

Re: UITableView -reloadData woes

2016-02-12 Thread Quincey Morris
On Feb 12, 2016, at 12:37 , Carl Hoefs wrote: > > Wouldn't that necessitate the invocation of the delegate callback method > -tableView:cellForRowAtIndexPath:? FWIW, the next time the app is run, the > additional data does appear in the table. Yes. In fact, the

UITableView -reloadData woes

2016-02-12 Thread Carl Hoefs
iOS 9.2 Is there a trick to using UITableView -reloadData? I can't get it to do anything. My view controller has a UITableView instance (VC is both UITableView delegate and dataSource), and I populate it with cells from my data source via the delegate callback method

Re: UITableView -reloadData woes

2016-02-12 Thread Carl Hoefs
On Feb 12, 2016, at 4:28 PM, Quincey Morris wrote: > > On Feb 12, 2016, at 16:23 , Carl Hoefs > wrote: >> >> When I issue the -reloadData, the -tableView:numberOfRowsInSection:

Re: UITableView -reloadData woes

2016-02-12 Thread Quincey Morris
On Feb 12, 2016, at 16:23 , Carl Hoefs wrote: > > When I issue the -reloadData, the -tableView:numberOfRowsInSection: callback > gets invoked. But, it returns the number of rows _before_ the addition. Whoa. *You* return the number of rows from *your* data model,

Re: UITableView -reloadData woes

2016-02-12 Thread Carl Hoefs
> On Feb 12, 2016, at 1:39 PM, Quincey Morris > wrote: > > I think the one thing you can count on is that the ‘reloadData’ API isn’t > broken. But it's very tempting to think so... ;-) When I issue the -reloadData, the -tableView:numberOfRowsInSection: