Mornin' Devs,
Is there a recommended pattern for passing events up the responder chain
without subclassing a class and overriding the methods I'm interested in?
Here is an explanation of what I'm trying to do:
I have a subclass of UIButton, call it MyButton, that I would like to
function as a vanilla UIButton but also pass touch events to the next
responder (I'm interested in eventually getting the events in
UIViewController). I can do something like this in MyButton:
-(void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event
{
[[self nextResponder] touchesBegan:touches withEvent:event];
}
But then I lose the touch handling that makes a UIButton different from just
a plain old UIView (e.g. highlight states). I could use [self
setHighlighted:YES], for example, to fix that problem. What I really want
to do, though, is something like this:
-(void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event
{
[self originalTouchesBegan:touches withEvent:event];
[[self nextResponder] touchesBegan:touches withEvent:event];
}
Something analogous to ruby's alias. I haven't found anything built in for
method aliasing, which leads me to believe there is another way to approach
this. Does anyone have a good approach?
Thanks,
Lou
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
