當兩個類別需要互相溝通時,協議(Protocol)是最乾淨的做法。它不像繼承那樣綁死實作,而是把「應該提供哪些方法」這份契約獨立出來,讓任何類別都能自行決定要不要簽。
兩個關鍵的修飾字:@optional 表示該方法可以選擇性實作,@required 則表示必須強制實作(若省略不寫,預設就是 required)。
標頭檔:
@protocol ContactCtrlDelegate
-(void)DismissContactsCtrl;
@end
@interface ContactsCtrl : UIViewController {
id <ContactCtrlDelegate> delegate;
}
@property (nonatomic, assign) id <ContactCtrlDelegate> delegate;
@end
實作檔:
@synthesize delegate;
UITextViewDelegate 就是標準寫法,可以參考它如何區分必要與選填:
@protocol UITextViewDelegate <NSObject> @optional - (BOOL)textViewShouldBeginEditing:(UITextView *)textView; - (BOOL)textViewShouldEndEditing:(UITextView *)textView; - (void)textViewDidBeginEditing:(UITextView *)textView; - (void)textViewDidEndEditing:(UITextView *)textView; - (BOOL)textView:(UITextView *)textView shouldChangeTextInRange:(NSRange)range replacementText:(NSString *)text; - (void)textViewDidChange:(UITextView *)textView; - (void)textViewDidChangeSelection:(UITextView *)textView; @end
想要接到這些回呼,必須先設定委派對象:textView.delegate = self;
ContactsCtrl.h:
#import <UIKit/UIKit.h>
// 定義協議
@protocol ContactCtrlDelegate
-(void)DismissContactsCtrl;
@end
@interface ContactsCtrl : UIViewController {
IBOutlet UINavigationBar *ContactNavBar;
id <ContactCtrlDelegate> delegate;
}
@property (nonatomic, assign) id <ContactCtrlDelegate> delegate;
-(IBAction)canCelBtn:(id)sender;
@end
ContactsCtrl.m:
@implementation ContactsCtrl
@synthesize delegate;
- (void)viewDidLoad {
[super viewDidLoad];
ContactNavBar.topItem.prompt = @"選取聯繫人發送短信";
}
// 呼叫協議中的方法
-(IBAction)canCelBtn:(id)sender {
[delegate DismissContactsCtrl];
}
@end
ProtocolDemoCtrl.h:
#import <UIKit/UIKit.h>
#import "ContactsCtrl.h"
@interface ProtocolDemoCtrl : UIViewController <ContactCtrlDelegate> {
ContactsCtrl *contactsView;
}
@end
ProtocolDemoCtrl.m:
#import "ProtocolDemoCtrl.h"
#define BARBUTTONADD(SELECTOR) [[[UIBarButtonItem alloc] initWithBarButtonSystemItem:UIBarButtonSystemItemAdd target:self action:SELECTOR] autorelease];
@implementation ProtocolDemoCtrl
@synthesize contactsView;
- (void)viewDidLoad {
[super viewDidLoad];
self.navigationItem.rightBarButtonItem = BARBUTTONADD(@selector(addContactAction:));
}
- (void)addContactAction:(id)sender {
ContactsCtrl *contactView = [[ContactsCtrl alloc] initWithNibName:@"ContactsCtrl" bundle:nil];
self.contactsView = contactView;
contactsView.delegate = self; // 設定委派
[self presentModalViewController:contactsView animated:YES];
[contactView release];
}
// 實作 ContactCtrlDelegate 協議中的方法
-(void)DismissContactsCtrl {
[contactsView dismissModalViewControllerAnimated:YES];
}
@end
如果 A 類別在標頭檔定義了一個協議,同時也宣告了一個 delegate 屬性;協議裡有一個必須實作的 methodA(由遵循協議的類別負責實作),而 A 類別在實作檔中透過委派去呼叫它:
[delegate DismissContactsCtrl];
那麼 B 類別只要遵循該協議、在實作檔寫好 methodA,並且把 delegate 指向自己:
a.delegate = self; // 設定委派
雙向通道就建立起來了。若 methodA 的傳回值是 B 類別的物件,A 類別便能取得 B 的屬性與方法,反之亦然——這正是委派模式能做到「父子頁面互傳資料」的原因。