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 <br...@darknova.com>
wrote:
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 know that Table View 1 will need to be update 90% of the time.
I've done the following in Table View 1's controller:
- (void)viewDidAppear:(BOOL)animated
{
[super viewDidAppear:animated];
if( self.beenHereBefore )
[self.tableView reloadData];
self.beenHereBefore = YES;
}
This solution seems to work.
My question is, is this the best way to do this and is this the best
method to do it in?
Perhaps viewWillAppear is better?
Perhaps reloadData before calling super?
Thanks.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/luketheh%40apple.com
This email sent to luket...@apple.com
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
