using a delegate in a class method

Question

I want to invoke a delegate in class method.

The example below obviously does not work, since the delegate is an instance variable that is accessed within a class method. (Error: instance variable 'delegate' accessed in class method)

Is there an alertnative?

My header file:

//  MyClass.h

#import <Foundation/Foundation.h>

@protocol MyDelegate <NSObject>

-(void)update;

@end

@interface MyClass : NSObject
{
    id<MyDelegate> delegate;
}
@property (nonatomic, retain) id delegate;

+(void)methodThatInvokesDelegate;
@end

My implementation file:

//  MyClass.m
#import "MyClass.h"

 @implementation MyClass
 @synthesize delegate;

+(void)methodThatInvokesDelegate{
[delegate update];
 }

 @end

you're missing the "@" in front of protocol. what exactly is the problem you're seeing? — Mike M
– Mike M, Commented May 29, 2013 at 11:34
@MikeM the above was just an example. Not code that I am actually using. But just to illustrate the problem. I edited my post and added the '@'. The error i': "instance variable 'delegate' accessed in class method — steak2002
– steak2002, Commented May 29, 2013 at 11:38
Why do you want to do this? Maybe you're better off using a singleton pattern? — Marcel
– Marcel, Commented May 29, 2013 at 11:39
if you want to send a simple "update" to a class, it's maybe enought to use the NSNotificationCenter stackoverflow.com/questions/16409448/… . Else I would recommand to set the methode non-static or use a singleton like @Marcel said — geo
– geo, Commented May 29, 2013 at 11:49
I want to an event to be triggered within a class method. This event is then subscribed to by another class. — steak2002
– steak2002, Commented May 29, 2013 at 11:53

Stephen Darlington · Accepted Answer · 2013-05-29 11:50:26Z

3

Three obvious options:

Singleton
Static variable (i.e., class variable) pointing to the delegate
Use NSNotification's rather than delegates

Since a singleton (and a static variable) can't keep track of the lifecycle of delegates, I think option three would be the cleanest.

answered May 29, 2013 at 11:50

Stephen Darlington

52.8k12 gold badges110 silver badges153 bronze badges

Sign up to request clarification or add additional context in comments.

9 Comments

Amin Negm-Awad Over a year ago

I would not take option 3, because notifications are "untargeted", while delegating is "targeted". With targeted I want to say, that delegating points to a specific object.

Stephen Darlington Over a year ago

@AminNegm-Awad I take your point but we're trying to do something a bit odd here so there's bound to be some breakage. I would consider notifications to be the lesser of evils in this case.

Amin Negm-Awad Over a year ago

This is a subject of taste for sure. But I think, that a static variable is nothing evil. And with notifications, for example, you will never have a return value.

Stephen Darlington Over a year ago

Prior to zeroing weak references, a static delegate would be a crash waiting to happen. Static variables in general are fine but I think delegates are a special case -- because they're dependent on but not in control of another object -- even though, technically, they're just a variable like any other. Also, notifications have the user dictionary, so can pass values back.

Amin Negm-Awad Over a year ago

How to pass a value back? And whose value? You can have a mass of notification observers.

|

Amin Negm-Awad · Accepted Answer · 2013-05-29 11:51:02Z

I want to know the context, which let you run in that situation. ;-) Anyway:

First: Delegates are set for a specific instance object. Because of this, you can have different delegates for different instances of the same (delegating) class.

Second: A class method runs inside a class object of that class. This is an object that is different from every instance object of that class. So there is nothing that can be called "the delegate". You can have 100s of delegates.

Third: Your class object needs a delegate at its own. So you have to add a property delegate to the class object and then use this. (Yes, it is possible to have properties an a class object. I did not write declared property.) If you need further information on how to do this, just comment it. I will add code.

Mike M · Accepted Answer · 2013-05-29 11:52:03Z

I'm not sure if this will help you, but I have a similar situation where I have a class method used for data loads. In this case, the class instantiates itself (so that the caller doesn't need to) until it is done. (this code was edited somewhat to make it work here)

header file:

    @protocol DataLoaderDelegate2 <NSObject>
    - (void) dataLoaderSuccess:(NSData *)data loader:(id)theloader;
    - (void) dataLoaderFailed:(NSString *)error loader:(id)theloader;
    @end

    @interface DataLoader2 : NSObject {
            NSURLConnection *conn;
            NSMutableData   *receivedData;
            NSFileHandle    *fileHandle;
            id <DataLoaderDelegate2>    delegate;
    }
    @property (nonatomic, assign) id<DataLoaderDelegate2>delegate;

Call to start the process - the call to initWithRequest passes "self" along.

    + (DataLoader2 *)loadWithURLRequest:(NSURLRequest *)req delegate:(id)_delegate
    {
        DataLoader2 *dl = [[DataLoader2 alloc] init];
        [dl setDelegate:_delegate];
        conn = [[NSURLConnection alloc] initWithRequest:req delegate:self];
        return dl;
    }

When the data is done loading, it cleans up with something like

    - (void)connectionDidFinishLoading:(NSURLConnection *)connection
    {

            if ([delegate respondsToSelector:@selector(dataLoaderSuccess:loader:)])
                    [delegate dataLoaderSuccess:(fileHandle)?(id)fileHandle:(id)receivedData loader:self];
            [self autorelease];
    }

Collectives™ on Stack Overflow

using a delegate in a class method

3 Answers 3

9 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

9 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related