The better approach is to use bindings so the target is updated whenever the source (height) changes, regardless of why it changed.
Moving from AS2 to AS3 is sometimes harder than learning AS3 from scratch--don't think about how you did things before but learn how Flex does things. In general the more you leverage the framework and language the better off you and your apps will be. MXML and Bindings are good examples of this. HTH, Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building Flex based products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Winter Sent: Tuesday, November 27, 2007 12:28 PM To: [email protected] Subject: [flexcoders] Re: This has to be a bug right? If not, please explain... Is there a better, more appropriate way to validate certain properties, like "height", after adding children to a UIComponent or subclass of UIComponent? Coming from AS2 I find it confusing that there isn't an easy way to access the height of a container after adding children. If later during runtime I need to access the height of dynamically created child container, what is the appropriate approach?
