tableView didSelectRow not properly functioning - iphone

Question

My other question was ambiguous so I will make this one clearer. I have a table view on one viewController and when a cell is selected, it saves a number to NSUserDefaults. On my main viewController, I retrieve this number and want to update a label with it. I did some debugging and found that when I go back to my main viewController from the tableView one, this is the order at what happens:
1) main view loads
2) tableView cell tap recognized
3) number saved to NSUserDefaults
How would I change the order so that the main view loads last so that when I click a cell, it changes the label in my main viewController?
Here is the code from my didSelectRow method
- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath
{
NSString *pointsPath = [[NSString alloc] initWithFormat:#"totalPoints"];
NSString *numberFirst = [[NSString alloc] initWithFormat:#"numberFirst"];
int totalPoints = [[NSUserDefaults standardUserDefaults] integerForKey: pointsPath];
int number = [[NSUserDefaults standardUserDefaults] integerForKey:numberFirst];
if([indexPath row] == 1)
{
NSLog(#"Selected First row");
if(totalPoints < 10)
{
if (number != 0)
{
NSLog(#"Did not add a point, but saved");
[[NSUserDefaults standardUserDefaults] setInteger:1 forKey:numberFirst];
[[NSUserDefaults standardUserDefaults] synchronize];
}
else if (number == 0)
{
NSLog(#"Added a Point");
int newPoints = totalPoints + 1;
[[NSUserDefaults standardUserDefaults] setInteger:newPoints forKey: pointsPath];
[[NSUserDefaults standardUserDefaults] setInteger:1 forKey:numberFirst];
[[NSUserDefaults standardUserDefaults] synchronize];
int logPoints = [[NSUserDefaults standardUserDefaults]integerForKey:pointsPath];
NSLog(#"Point Count:%i", logPoints);
}
}

Answer 1

A controller's view is loaded on demand. So the thing that triggers viewDidLoad is somebody else performing controller.view. If you've already pushed the view controller into a container view or otherwise started to present it then that'll be the agent responsible.
viewDidLoad, and under iOS 5 and below viewDidUnload, are intended to give you the hooks you need if you want to create some part of the view programmatically.
If what you're doing is trying to account for a setting that may have been changed while the controller wasn't visible, you should probably use viewWillAppear:. That's the intended way to determine when you're about to transition from invisible to visible.
If you wanted a completely active link between the two things then you would set up the view controller that displays the number to listen for NSUserDefaultsDidChangeNotification and to update views as necessary when that occurs.

Answer 2

Guys i finally found the problem if anyone has this problem... You need to make sure that when the user selects a cell, it is a push segue not a modal... This is so frustrating that is was so simple!!