I personally tend to call super after all my code not before, but that could
change if apple actually does anything with these methods later on. And I
would implement the tableView reloadData in viewWillAppear, since it gets
called before it actually appears. If there's any slow downs on the phone
Depends on what you want for your app. If you want the user to see the
table data change then keep it the way it is. If you'd rather the
change occur out of view use viewWillAppear:
Luke
Sent from my iPhone.
On Dec 26, 2009, at 8:31 PM, Brian Bruinewoud
wrote:
Hi all,
I have a naviga
Hi all,
I have a navigation controller based app consisting mostly of table views.
Table View 1 moves you to Table View 2 when you select a row.
When you return from Table View 2, Table View 1 needs to be updated to show the
changes made.
There is no fetchedResultsController for Table View 1.
I k
