base question
-
I have a control C that extends control B that extends control A. In control C's OnXYZEvent method, I occassionaly need to call control A's OnXYZEvent rather than control B's (as control B's does something I may not want it to do) - ie:
OnXYZ() { // do some stuff if (_) { //B.OnXYZ() base.OnXYZ(); } else { //A.OnXYZ() ??? } }Is this at all possible? "I think I speak on behalf of everyone here when I say huh?" - Buffy -
I have a control C that extends control B that extends control A. In control C's OnXYZEvent method, I occassionaly need to call control A's OnXYZEvent rather than control B's (as control B's does something I may not want it to do) - ie:
OnXYZ() { // do some stuff if (_) { //B.OnXYZ() base.OnXYZ(); } else { //A.OnXYZ() ??? } }Is this at all possible? "I think I speak on behalf of everyone here when I say huh?" - BuffyYou make another derived class! :) top secret xacc-ide 0.0.1
-
You make another derived class! :) top secret xacc-ide 0.0.1
Thats what I thought, and its so not what I wanted to do :( "I think I speak on behalf of everyone here when I say huh?" - Buffy
-
Thats what I thought, and its so not what I wanted to do :( "I think I speak on behalf of everyone here when I say huh?" - Buffy
But in the long run it will prove better, now it mite just be one method, but later it could be several, and then the seperation of logic makes alot more sense, especially if you have to debug the app several months later. top secret xacc-ide 0.0.1