heh you're a mad man :D
Hmm, gotta be a better way then unique Init methods.. oh well i'll figure it out, that or lit it ping around the shop until the dust settles...
Ie it kinda of balances out in the end... but it just seems like a damn ugly way of doing it...
I don't understand the issue with calling the parent's init() function?
You are basically saying, you've got an object (TextField) that is like an Label, it has the same properties, methods, behaviours and it also has these other properties, methods and behaviours. So you are defining a new type of object (InputField) that extends the Label type with these additional properties, methods and behaviours and you are saying when you init() an object of this type, it has the same init() behaviour as Label plus, potentially, a couple of other things need to be done on initialisation.
This is bascially the way inheritance works, reusing Label to get an InputField.
--- You are currently subscribed to fugli as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
