Read that link Michael provided, but in short, step 9 says the following, which indicates that when the initialize event is fired, the components inside the Panel have been initialized, but they have not been sized or laid out.
9) Dispatches the initialize event on the component. At this time, all of the component's children are initialized, but the component has not been sized or processed for layout. You can use this event to perform additional processing of the component before it is laid out.
That explains it. There IS a 'preinitialization' event which is essentially what I thought the 'initialize' event was.
Sorry I didn't find it myself in the documentation, but it's SO massive!
Remember the days of C, when you read a short little book like K&R, and you knew essentially everything you needed to use the language? :-)
You're welcome, yes the documentation is massive, but there you find most of the times the info you need.
Tell me about it, it's so hard to keep up these days, learning new technologies, mastering the actual ones, but is a fun ride.
Happy flex coding
The proper comparison is C to ActionScript, not C to Flex. C and ActionScript are languages while the Flex runtime is an application framework written in ActionScript. I don't think learning ActionScript is any harder than learning C, but learning any application framework tends to be time-consuming.
Adobe Flex SDK Team