Delegates & Protocols iOS

A complex subject to wrap your head around, i agree!  But its pretty cool once you get a working example going.

Let’s think of a game where a lander comes down from the sky (presumably on Mars – since Mars is a hot topic lately) and deploys a  rover.  In Cocos2d, you put all your objects on a Layer object.  This means the layer class is the main class (analogous to a viewcontroller class contains buttons, views, labels, cells etc).

You create a Lander object class because you want to re-use it everywhere in the game.  With every new level, you must create a new layer class but you can reuse your Lander Class.  So you wan’t your Lander to be able to deploy these rovers so that each time you reuse the lander, it can deploy rovers on any given layer.

Let’s look at this image:

Marcio Valenzuela at Santiapps.com
Marcio Valenzuela at Santiapps.com

The Lander object declares a GameplayLayerDelegate property.  This means any lander object will be a delegate to the GameplayLayer.  This means the Lander can call the mystery protocol method in order to create the Rover object by saying:

[delegate mysteryMethod];

And the GameplayLayer only has to adopt the GameplayLayerDelegate.

In the case of an iOS app, a typical scenario might be a To Do List where you have a list of items and you wish to add a new item.  You have 2 view controllers: one lists the existing items and the other is called when the user taps on the “Add” button and wants to add a new item.  You might have something that looks like this:

Delegates & Protocols: Santiapps.com by Marcio Valenzuela
Delegates & Protocols: Santiapps.com by Marcio Valenzuela

In this scenario the AddItemViewController on the right will want to take the user input and report it back to the ViewController on the left labeled To Do List.  The steps are:

1)  The ViewController on the left will conform to or adopt the AddItemViewControllerDelegate.

2) The AddItemViewController class declares its protocol like so:

@protocol AddItemViewControllerDelegate <NSObject>

– (void)addItemViewControllerDidCancel:(AddItemViewController *)controller;

– (void)addItemViewController:(AddItemViewController *)controller didFinishAddingItem:(ToDoItem *)item;

– (void)addItemViewController:(AddItemViewController *)controller didFinishEditingItem:(ToDoItem *)item;

@end

3) And it declares the property:

@property (nonatomic, weak) id <AddItemViewControllerDelegate> delegate;

4) Finally the AddItemViewController calls those mystery methods by saying:

– (IBAction)cancel{

[self.delegate addItemViewControllerDidCancel:self];

}

– (IBAction)done{

// Do whatever in order to capture user data

//Now send that info back to the delegate

[self.delegate addItemViewController:self didFinishAddingItem:item];

}

Advertisements

3 thoughts on “Delegates & Protocols iOS

  1. I ‘m trying to access a single method at three times in a row. Each time i will be passing different parameter (parameters are the url which has to get connected to some webservice and retrieve the data) to the method so that i thought i can get three response for each calling. But for the sake of multithreading my second message get passed to the class before first one goes off , the same happening on third call. can gimme a quick guidance…
    Thanks in advance

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s