Re: Simple but fundamental question
Re: Simple but fundamental question
- Subject: Re: Simple but fundamental question
- From: Guy Umbright <email@hidden>
- Date: Wed, 1 Feb 2006 12:33:19 -0600
You have to remember that by calling the super method, that does not
put you into a 'super mode' where
the class of the object is now considered to be the super class. It
is still the same object and any
invocation will to the the 'outermost' class.
Guy
On Feb 1, 2006, at 7:06 AM, email@hidden wrote:
Hi,
I have a simple question, but means a lot to me.
That is, if I call a method of super, like [super goAway] and -
goAway calls a method on self, like [self blowUp],
and - blowUp is subclassed in the same class that called the
original method, super's call would call my subclassed method?
Is supers' self actually the same as my "self?"
So If I could have a call stack like this :
...
4 NSObject : CleanUp
3 MyObject : BlowUp //Calls super CleanUP
2 NSObject : CleanUp //Calls Self BlowUP (I would think the
super's implementation but calls subclassed one?)
1 MyObject : BlowUp //Calls super CleanUP
Is it true? That is what I'm seeing.
NSController calls - setSelectionIndexPath when setting -
setSelectionIndexPaths apparently, and instead of calling super's
version of - setSelectionIndexPath it calls my subclasses' one....
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40kickstandsoft.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden