Title: Message
This is actually a bug in DateChooser's createChildren(). A createChildren() routine should not recreate children than already exist.
 
It isn't possible to use super.super but you could probably play games like UIComponent.prototype.createChildren.call().
 
- Gordon
-----Original Message-----
From: Simon Fifield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 30, 2005 2:52 AM
To: [email protected]
Subject: RE: [flexcoders] super.super?

I have extended the DateChooser component to allow user to click through Years and Months rather than just Months.
 
I have overridden the createChildren() method. DateChooser calls super.createChildren(). If I call super.createChildren() in my subclass at the end of my method it redefines the objects that I have overridden, if I call it at the beginning of my method before I create the objects, it does most of the work twice.
 
It works if I don't call super.createChildren() at all, but there are side effects that I have to fix after anyway.
 
If the superClass creates and lays-out objects that I do not want in my subClass I would like to be able to call the superClass' super methods to by-pass the instantiation and layout of the objects that I don't want.
 
But I presume its not possible?
 
-----Original Message-----
From: Chris Velevitch [mailto:[EMAIL PROTECTED]
Sent: 30 March 2005 03:15
To: [email protected]
Subject: Re: [flexcoders] super.super?

If you are in a method of say class C which extends class B, then
calling super.someMethodName works. If class B extends class A and B
doesn't redefine a method of A, say, called methodOfA, then in class C
you can call super.methodOfA. This is because, through inheritance,
all unredefined methods of A are automatically available to B. Super
only works one level up.



Yahoo! Groups Sponsor
ADVERTISEMENT
click here


Yahoo! Groups Links

Reply via email to