global bool variable. Is it the best practice on iPhone?

Question

I want to keep track of when I move from one view to another.

So I created a global bool to keep track of this.

This works, but is it the best practice? Should I make it a property?

Thanks!

bool didNavigateToFullWebView; 

    viewDidAppear: (BOOL) animated {
     if(didNavigateToFullWebView) {
          //Load differently depending on the last view visited.
      } 
    }

    - (void) tableView: (UITableView*) tableView didSelectRowAtIndexPath: (NSIndexPath*) indexPath {  
     didNavigateToFullWebView = YES; 
 }

if you're using a navigation controller, you'll have a "stack" of previous view controllers (in a `viewControllers` array property) to fall back upon. — Michael Dautermann, Apr 22 '12 at 01:26

score 1 · Accepted Answer · edited May 23 '17 at 10:24

A common practice is to put all your state in your model class (as in "model - view - controller" pattern), and make your model a singleton. Then all globals go into the model class as properties, or become hidden behind publicly available methods. This is better than scattered globals, because the readers of your code will need to look in a single place for all the state information of your application. Here is a stack overflow question with a relevant discussion.

global bool variable. Is it the best practice on iPhone?

1 Answers1