iOS Subclassing a Custom Class

Question

I'm having trouble wrapping my thoughts about class inheritance. I'm suppsed to create a dashboard like interface in a app, and I'll have maybe 10 widgets/dashlets on that dashboard view. All those dashlets/widgets will have basically same look, with a title on the top, borders, row of buttons on the top and a graph. Let's say I create a subclass of UI View called 'Dashlet' with properties and outlets, and create XIB file with proper layout and connected outlets etc.

Now I want to create several subclasses of that 'Dashlet' view that will only process data differently, and draw different graphs. My current code looks something like this:

Dashlet.h

@interface Dashlet : UIView{
@private
    UILabel *title;
    UIView *controls;
    UIView *graph;    
}
@property (weak, nonatomic) IBOutlet UILabel *title;
@property (weak, nonatomic) IBOutlet UIView *controls;
@property (weak, nonatomic) IBOutlet UIView *graph;

-(Dashlet*)initWithParams:(NSMutableDictionary *)params;
-(void)someDummyMethod;
@end

And in Dashlet.m

- (id) init {
    self = [super init];
    //Basic empty init...
    return self;
}

- (id)initWithFrame:(CGRect)frame
{
    self = [super initWithFrame:frame];
    if (self) {

    }
    return self;
}

-(id)initWithParams:(NSMutableDictionary *)params
{
    self = [super init];
    if (self) {
        self = [[[NSBundle mainBundle] loadNibNamed:@"Dashlet" owner:nil options:nil] lastObject];
        //some init code
    }
    return self;
}

Now let's say that I create a subclass called CustomDashlet.h:

@interface CustomDashlet : Dashlet
@property (nonatomic, strong) NSString* test;
-(void)testMethod;
-(void)someDummyMethod;
@end

and CustomDashlet.m

-(id)init{
    return self;
}

- (id)initWithFrame:(CGRect)frame
{
    self = [super initWithFrame:frame];
    if (self) {

    }
    return self;
}

-(id)initWithParams:(NSMutableDictionary *)parameters
{
   self = [super initWithParams:parameters];
   if (self) {
      //do some stuff 
   }
   return self;
}

This, kind of works, but I need to override some of the methods declared in the superclass or even add some of my own. Whenever i try to do something like this in CustomDashlet.m

[self someDummyMethod] or even [self testMethod] I get an exception error like this:

NSInvalidArgumentException', reason: '-[Dashlet testMethod]: unrecognized selector sent to instance

Am I even doing this right? Did I miss something? Am I supposed to make this work in some other way? If anyone has suggestions, please feel free to share your thoughts, thank you for all the help.

Do you have concrete implementations of someDummyMethod and testMethod? — jszumski
Where is implementation of [self someDummyMethod] and [self testMethod] methods? — Tirth
Not a duplicate, but your question is answered here: stackoverflow.com/questions/19451744/… — nhgrif
@jszumski Well, the someDummyMehod is implemented in superclass, and it looks as even though I override it in subclass, a superclass implementation code gets called. Test method is a method I don't have in superclass, only in subclass, and whenever it gets called, i get exception that no 'testMethod' method found in superclass. — Slavenko Miljic
@SlavenkoMiljic: The exception method -[Dashlet testMethod]: unrecognized selector clearly indicates that self in [self testMethod] is a Dashlet, and not a * CustomDashlet* as you expect. You should provide a small self-contained example demonstrating the problem, in particular show how the object is created. — Martin R

Martin R Martin R · Accepted Answer · 2013-11-11T21:19:23

The problem is that

SalesDashlet *sales = [[SalesDashlet alloc] initWithParams:nil];

does not return a SalesDashlet instance, as expected, but a Dashlet instance. Here is what happens:

[SalesDashlet alloc] allocates an instance of SalesDashlet.
The subclass implementation of initWithParams: is called with this instance, and calls self = [super initWithParams:parameters].
The superclass implementation of initWithParams discards self and overwrites it with a new instance loaded from the Nib file. This is an instance of Dashlet.
This new instance is returned.

Therefore SalesDashlet *sales is "only" a Dashlet, and calling any subclass method on it throws an "unknown selector" exception.

You cannot change the type of objects loaded in the Nib file. You could create a second Nib file containing a SalesDashlet object. If the main purpose of the subclass is to add additional methods, then the easiest solution would be to add these methods in a Category of the Dashlet class.

iOS Subclassing a Custom Class

4 Answers