Re: Using Protocols (complete message this time...)

• Subject: Re: Using Protocols (complete message this time...)
• From: crucial felix <email@hidden>
• Date: Mon, 30 Dec 2002 11:37:15 -0500

@interface NPRolloverButton : NSImageView {
NSImage *normalState;
NSImage *overState;
NSImage *downState;
id <NPRolloverProtocol> controller;
SEL downEvent;
}
The controller is not in the nib file at
all. All of the initialization of the custom button is done in its
-awakeFromNib method, which means that the controller object won't be
created yet (since non-nib objects are created after nib-based objects are).
So I want to call alloc and init on 'controller'. This is the first problem.
How the heck do I allocate and initialize a dynamically typed object? I have
no idea what the class is,

and I have tried using things like [controller
class] in the alloc-init statement (formed like [[[controller class] alloc]
init];), but that doesn't work at all. The program still compiles, but I get
a warning that says that -class isn't implemented by the protocol, and then
when that line is executed... nothing happens.

A second problem is that whenever I call ANY method on the controller (other
than a method that is part of the protocol, such as -performSelector), the
compiler issues a warning that says that -performSelector isn't part of the
protocol. But since -performSelector is a function of NSObject, it is a
given that all classes will be able to perform -performSelector.

• Prev by Date: Re: multithreading limits?
• Next by Date: How to do the opposite of global floating window
• Previous by thread: Using Protocols (complete message this time...)
• Next by thread: CVS versus OSX cvswrappers
• Index(es):
  • Date
  • Thread