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...
--
Regards, Scott Barnes - http://www.mossyblog.com http://www.bestrates.com.au
Lindsay Evans wrote:
Hi Scott,
When you're calling this.init() from the UIObject constructor, it's always going to call the InputField::init() method, 'cos it's overriding Label::init(), which is in turn overriding UIObject::init()
InputField::init() is then going to call Label::init() (via super.init()), which will call UIObject.init() in the same way.
The only way to achieve the result you want would be to give your init methods unique names.
I think I've worn out the bracket keys on my keyboard now, so I'll stfu & get back to messing with cellRenderer.
-- Lindsay Evans. Developer, Red Square Productions.
[p] 8596.4000 [f] 8596.4001 [w] www.redsquare.com.au
--- 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
