Maybe those components never finish initializing? You can override measure() and updateDisplayList() and commitProperties() on the custom components and see if they get called over and over again.
well I've tried with something much simpler and it still doesn't work. So I removed all scripts and all components and just added an mx:Button.
The button is initialised but it's creationComplete event does not get fired.
So I'm not exactly sure what's wrong.
I have a mx:Module (DashboardModule) which is loaded using Cairngorm's ModuleViewLoader and that includes the following:
DashboardView is the code I've shown you above.
But as I said, even If I remove all scripts and components from DashboardView.mxml and just leave an mx:Button with a creationComplete handler and an initialize handler, the creationComplete handlernever gets invoked.
Could this be something with mx:Module and Cairngorm's ModuleViewLoader?
I should say that the Module's creationComplete handler gets invoked and so does the DashboardView's creationComplete handler gets invoked but not DashboardView's children.
Try a simpler new project that doesn’t use Cairngorm.
I think changing the DashboardView's VBox to VGroup helped. So this might be an SDK bug.